public inbox for
 help / color / mirror / Atom feed
From: Peter Milne <>
To: Doug Fraser <>
Subject: Re: SN 5.0 html docs
Date: Wed, 05 Sep 2001 13:31:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Doug Fraser wrote:

>Another thing, I have a method of collecting file
>path names into a text file, and a shell script that
>filters those relative path names into a temp file
>as full path names and starting source navigator
>using the created temp file as an import file.
>It works okay and lets us set up pseudo-projects
>that can be stored in CVS and shared between
>developers. If anyone is interested in the shell
>script I will attach it to the list. Sure, it could
>have been prettier in TCL, but I don't know TCL.....
Script sounds great. Please let us see it.
Having a project with full path names is no good when you want to use it 
from different


  reply	other threads:[~2001-09-05 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 12:59 Doug Fraser
2001-09-05 13:31 ` Peter Milne [this message]
2001-09-06  4:52 Doug Fraser

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