public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ian Roxborough <irox@redhat.com>
To: Bill Munday <bmunday@3glab.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Using Nedit, gvim, etc Editors with Snav 4.x
Date: Thu, 26 Apr 2001 16:08:00 -0000	[thread overview]
Message-ID: <3AE8AA23.40DD6178@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104261308090.1322-100000@bmunday>

Bill Munday wrote:
> 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.

SN doesn't know anything about sam files (I don't either for that matter).
However, if you can produce a short reproducible test case for the
highlighting problem, then it's a step closer to being fixed.

> How do I use another editor and still maintain the jumping to errors
> during the build step?

Emacs is meant to have that level of integration, however it's
possible that the Emacs integration is broken.  Current, I don't
think there are any other editors that could work like that.
 
> As changing the Preferences - EDIT = external editor does not give a clean
> integration.

Yeah, that level of integration would require adding an editor interface
layer that can control either an existing SN editor or be ported to
control 3rd party editors.

> PS How comes no one aswered my previous emails?

I didn't have a good answer.

Ian.

  reply	other threads:[~2001-04-26 16:08 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 [this message]
2001-04-26 18:36     ` Mo DeJong

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=3AE8AA23.40DD6178@redhat.com \
    --to=irox@redhat.com \
    --cc=bmunday@3glab.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).