From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: Re: Using Nedit, gvim, etc Editors with Snav 4.x
Date: Thu, 26 Apr 2001 18:36:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010426183440.4240C-100000@cse.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104261308090.1322-100000@bmunday>
On Thu, 26 Apr 2001, Bill Munday wrote:
> Hi,
>
> Up till now I have been happy with SN Editor until recently where it has
> started to mess up syntax highlighting, an nor can it highlight sam files.
>
> How do I use another editor and still maintain the jumping to errors
> during the build step?
I think that is covered here:
http://sources.redhat.com/sourcenav/online-docs/userguide/editor.html#pgfId-1075901
> As changing the Preferences - EDIT = external editor does not give a clean
> integration.
Could you explain what you mean by that? An external editor is by
definition not integrated.
Mo
prev parent reply other threads:[~2001-04-26 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 3:04 Bugfix for sorting problem in the symbol browser Khamis Abuelkomboz (UUNET)
2001-04-23 3:06 ` Khamis Abuelkomboz (UUNET)
2001-04-26 5:24 ` Using Nedit, gvim, etc Editors with Snav 4.x Bill Munday
2001-04-26 16:08 ` Ian Roxborough
2001-04-26 18:36 ` Mo DeJong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SOL.3.91.1010426183440.4240C-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).