rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Stefan Axelsson <d7stfax@dtek.chalmers.se>
To: rc@hawkwind.utcs.utoronto.ca (The rc mailing list)
Subject: ~ == $home
Date: Thu, 12 Nov 1992 18:25:23 -0500	[thread overview]
Message-ID: <9211122326.AA06156@dtek.chalmers.se> (raw)

Hmm, I missed the beginning of this thread, but I've avoided missing ~
== home by using cdpath, and the variable expansion feature of
editline.

1) Our usernames are very regular (d7stfax, aso) and thus are well suited
for inclusion in the cdpath variable. e.g:

cdpath=(. /users/dtek /users/dtek/d82 /users/dtek/d83 /users/dtek/d84 \
        /users/dtek/d85 /users/dtek/d86  /users/dtek/d87 /users/dtek/d88 \
        /users/dtek/d89 /users/dtek/d90 /users/dtek/d91
	/users/dtek/d92) 

Thus I can say cd d7stfax, and end up in: /users/dtek/d87/d7stfax.
Of course this solution doesn't cover all contingencies like ~d7stfax
would, but in practice I have had no problem with it.

2) Now there`s the annoying fact that you cannot use filename
completion to complete say; $h/bin/whateve. If you have editline
compiled in you can set '_H_' for instance to;
/users/dtek/d87/d7stfax/, and improve the situation.

Since I have a keyboard with a 'meta' shift key, I press M-Shift-h and
can use filename completion from there on.  OK, that's three
simultanous keys, but I have no problem with that.  Your command line
can get quite long though. As in 1) above this isn't perfect, but it
works like a charm for me.

These solutions may not, for various reasons, be right for you, but
then again everybodys mileage may vary.

Regards,
-- 
Stefan Axelsson,			Chalmers University of Technology,
d7stfax@dtek.chalmers.se		Sweden


             reply	other threads:[~1992-11-12 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-12 23:25 Stefan Axelsson [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-11-10 10:13 Brendan Kehoe

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=9211122326.AA06156@dtek.chalmers.se \
    --to=d7stfax@dtek.chalmers.se \
    --cc=rc@hawkwind.utcs.utoronto.ca \
    /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).