public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Warrick Lacey <wlacey@ikadega.com>
To: sourcenav@sources.redhat.com
Subject: Kudos and more...
Date: Sat, 21 Jul 2001 14:44:00 -0000	[thread overview]
Message-ID: <3B59F82A.832875EA@ikadega.com> (raw)

Hi Source Navigator Team...

My name is Warrick Lacey, I am an experienced developer and died in the
wool Linux/Unix/FreeBSD/xxx fan.
For sometime I have looked w/distain on most Microsoft developers,
working for the embodiment of evil himself but I have lusted after some
of the neat development tools which were available on the windows
platform (e.g. CodeWrite).

A friend of mine shot me a copy of Source Navigator and I initially
installed it and played w/it and found it useful. I love tools if they
are good, useful and not propietary, Source Navigator fit the bill. I
have since become more knowledgable and am now taking the time to make
it an integral part of my development tool kit (I consider this high
praise, my toolkit heretofore consisted only of emacs, make and gcc, a
small but mighty trio if ever there were) and in the course of
playing/tailoring it I wanted to share a few points.

Could never get Source Navigator (snag) to exhibit the proper behavior
of using the existing emacs window. Additionally, if you specify
emacsclient in the external editor, snag hangs... I was just trying to
get the thing to work I am using emacs-20.7.1 (maybe the problem is due
to my newer release of emacs, your online documentation mentions emacs
19.X)

THANKS for making a good useful tool, 
W

                 reply	other threads:[~2001-07-21 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B59F82A.832875EA@ikadega.com \
    --to=wlacey@ikadega.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).