Subject: Re: are there any patches which add ~ expansion to rc
Date: Fri, 19 Sep 1997 03:51:22 -0400 [thread overview]
Message-ID: <199709190751.IAA09932@vampire.cegelecproj.co.uk> (raw)
> 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.
True, but then, the problem lies in the ~ semantics, which aren't
great. Just as /u/foo can point to user foo's directory, /me (or /m)
can point to the current user's. Naturally, this needs special
handling in UNIX (as in /proc, /fd), and can be put in $home/lib/profile
in Plan 9.
What's really annoying is that this is one of the few things that
DOS can handle, and plain ol' UNIX can't.
next reply other threads:[~1997-09-19 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-19 7:51 Steve_Kilbane [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-09-18 2:27 arnold
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
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 NNTP newsgroup(s).