rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: "Jeremy Fitzhardinge" <jeremy@softway.com.au>
To: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: are there any patches which add ~ expansion to rc
Date: Fri, 19 Sep 1997 13:21:13 -0400	[thread overview]
Message-ID: <9709191221.ZM19970@suede.sw.oz.au> (raw)
In-Reply-To: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu> "Re: are there any patches which add ~ expansion to rc" (Sep 18,  7:26pm)

On Sep 18,  7:26pm, Chris Siebenmann wrote:
>  Our local solution is a /u directory (automatically) populated with
> symlinks that point to the appropriate places. We've been running it
> for years without problems; I can mail people copies of either a sh
> or a perl version[*] of the script that maintains /u if desired.

While I agree that /u is an elegant approach to dealing with the ~user
problem, the most common use of ~ is when referring to one's own
home directory, which /u doesn't help with.  I once implemented /u
as a user-space filesystem under Linux which generated its contents
on demand from /etc/passwd. It also had a /u/me which always referred
to the caller's home direcory, which is hard to do with a conventional
symlink /u.

The $H solution is OK for rc, but it has the same problems as ~, in that
not everything will understand it.


  reply	other threads:[~1997-09-19  6:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-17 15:56 Joseph Skinner
1997-09-17 21:56 ` Scott Schwartz
1997-09-17 22:08 ` Mark K. Gardner
1997-09-18 10:14 ` Tim Goodwin
1997-09-18 23:26   ` Chris Siebenmann
1997-09-19 17:21     ` Jeremy Fitzhardinge [this message]
1997-09-18  2:27 arnold
1997-09-19  7:51 Steve_Kilbane

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 \
    --in-reply-to=9709191221.ZM19970@suede.sw.oz.au \
    --to=jeremy@softway.com.au \
    --cc=cks@hawkwind.utcs.toronto.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


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