rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks>
To: rc
Subject: Re: are there any patches which add ~ expansion to rc
Date: Thu, 18 Sep 1997 19:26:21 -0400	[thread overview]
Message-ID: <97Sep18.202144edt.24666@hawkwind.utcs.utoronto.ca> (raw)
In-Reply-To: tgoodwin's message of Thu, 18 Sep 1997 06:14:43 -0400. <8ncAABP/IDSuhgUA@nan.cygnus.co.uk>

 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.

 I've repeatedly found it very handy to have a short name for home
directories that works in every program and situation. And better
yet there's no need to clog up umpteen programs with code to do ~

	- cks
[*: yes, I know I was giving in to the evil empire, but I decided I
    needed a decently fast program for the system with circa 10,000
    passwd entries.]

  reply	other threads:[~1997-09-19  0:21 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 [this message]
1997-09-19 17:21     ` Jeremy Fitzhardinge
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=97Sep18.202144edt.24666@hawkwind.utcs.utoronto.ca \
    --to=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).