public inbox for
 help / color / mirror / Atom feed
From: Mo DeJong <>
Subject: Re: Project files and other fun...
Date: Thu, 09 Aug 2001 16:35:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 9 Aug 2001, Doug Fraser wrote:

> Hello.

Hi Doug.
> I am a newbie to source navigator, with a couple of
> questions.
> 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.

No, all path names are fully qualified. Getting everything
working with relative paths is a big job and one that
really needs to be done.

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

If you want to learn some Tcl, one of the books is
a good place to start.

Mo DeJong
Red Hat Inc

      reply	other threads:[~2001-08-09 16:35 UTC|newest]

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

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