rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Alan Watson <alan@oldp.astro.wisc.edu>
To: "jeff (j.d.) sparkes" <jsparkes@bnr.ca>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: want code for b_access
Date: Tue, 22 Mar 1994 10:37:47 -0500	[thread overview]
Message-ID: <9403221537.AA11048@oldp.astro.wisc.edu> (raw)

For path building, it is probably easiest to use the hack in the rc FAQ
list -- attempt to cd to each directory.  It's not perfect, but it
works for me.  See question 5.7.

Alan.


             reply	other threads:[~1994-03-22 15:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-03-22 15:37 Alan Watson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1994-03-22 10:04 jeff (j.d.) sparkes

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=9403221537.AA11048@oldp.astro.wisc.edu \
    --to=alan@oldp.astro.wisc.edu \
    --cc=jsparkes@bnr.ca \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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 NNTP newsgroup(s).