public inbox for
 help / color / mirror / Atom feed
From: Doug Fraser <>
Subject: Project files and other fun...
Date: Thu, 09 Aug 2001 13:36:00 -0000	[thread overview]
Message-ID: <> (raw)


I am a newbie to source navigator, with a couple of

I am using SN5.

It seems that project '.proj' files have full path names
in them, and I was wondering if there is anyway to create
project files with relative paths that are prepended by
an environment variable so that they can be shared through CVS.

Also, for importing (snavigator -import /file/path) you
have to supply the full path to the file. It won't just pick
up the file from the current directory. Also, that file must
contain full paths. Is there some env value or flag that will
root it from the current working directory or from some
prenamed root path?

Other than these problems, it is a great tool.

BTW: I have zero TCL knowledge, a bit of Perl knowledge, a lot
	of C and ASM. I tried plowing around the tcl code, but could
	not figure out how .proj files are managed. I did note a
	number of env() variables (HOME, TMP, TEMP ...) but nothing
	that looked useful for my questions.

I probably need to learn some tcl in any case, just so that
I can hook VIM into the editor. I see the hooks for emacs but
cannot quite follow them. VIM has similar APIs for hooking to
other tools, and being an old (yeah, I am old...) vi hack,
moving to emacs is too painful. I tried once, and ended up
with tendonitis in my left pinky.

Thanks much.


> -----Original Message-----
> From: Mark Purtill [ ]
> Sent: Thursday, August 09, 2001 1:14 PM
> To:
> Subject: SourceNav with NTEmacs
> Dalton, Barnaby writes:
>  > Does anyone use sourcenav with ntemacs? I'm trying to get 
> it working with
>  > gnuclient. The first time I try to edit a file from 
> sourcenav a new emacs
>  > process is launched even if I have already started one via 
> other means. This
>  > second process starts with the *messages*
>  > 
>  > Server subprocess exited
>  > connection failed: connection refused,, sn
>  > 
>  > >From then on sourcenav always uses this second process. 
> Doesn anyone know
>  > what is going on?
>  > 
>  > Gnuclient/serv is defnitely working ok as I have used it 
> from windows
>  > explorer/msdev for years.
> 	I had a similar problem under Linux.  When you set the editor
> to gnuclient, SN recognizes that and does what it thinks is the right
> thing, which seems to be to start a new emacs for you.  (Subsequent
> calls would try to use gnuclient.)  In your case, it sounds like this
> doesn't work because the server that gnuclient talks to has already
> been started by your previous emacs.  Try writing a script with a name
> different from gnuclient; I have one that looks something like this:
> #! /bin/sh
> TMPDIR=/tmp
> export TMPDIR
> gnuclient $*
> You'll need the equivalent for NT, except probably not the TMPDIR
> stuff.  (There's an additional problem on Linux that SN sets TEMPDIR,
> which gnuclient uses to connect to the emacs; if the two processes
> have different TMPDIRs, they can't connect, so I reset it.)  You might
> try naming the progam both a name with "emacs" in the name and not and
> see which works better for you.  (The behavior is different because,
> again, SN is looking at the name and trying to be clever.)
> --
> ^.-.^ Mark Purtill
> (("))

             reply	other threads:[~2001-08-09 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 13:36 Doug Fraser [this message]
2001-08-09 16:35 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).