From: P.Stephenson@swansea.ac.uk
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: Compctl fixes & a query
Date: Mon, 17 Jul 95 11:08:18 +0100 [thread overview]
Message-ID: <1813.9507171008@pyro.swan.ac.uk> (raw)
In-Reply-To: "A.Main@dcs.warwick.ac.uk"'s message of "Sun, 16 Jul 95 15:33:59 BST." <14608.199507161434@stone.dcs.warwick.ac.uk>
A.Main@dcs.warwick.ac.uk wrote:
> On a separate matter, does anyone ever use the numerical equals
> expansion?
Yes, but tildes would be more in keeping with other syntax for
directories (~+ and ~- being sort of tied to the directory stack
anyway): also, there's no good reason for associating this behaviour
with the noequals option as is currently the case. If implemented
properly it would even allow trailing characters after a number to be
a separate directory name, since only a / or end of word would be a
separator, unlike the present case with =<num>. At the moment, it
doesn't look like ~<num> works at all, i.e. even with `hash -d 1 dir',
so there aren't compatibility problems there (in fact there's a bug,
since the directory will appear as ~1 in the stack).
We could possibly kludge =<num> followed by a slash or space where
<num> is not a command for the time being, but maybe going straight to
tildes is the right thing.
Now I've got my working directory called ~1, which I can't alter...
--
Peter Stephenson <P.Stephenson@swansea.ac.uk> Tel: +44 1792 205678 extn. 4461
WWW: http://python.swan.ac.uk/~pypeters/ Fax: +44 1792 295324
Department of Physics, University of Wales, Swansea,
Singleton Park, Swansea, SA2 8PP, U.K.
next prev parent reply other threads:[~1995-07-17 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-07-16 14:33 Zefram
1995-07-17 10:08 ` P.Stephenson [this message]
1995-07-17 17:17 ` Zefram
1995-07-17 18:17 ` Vinnie Shelton
1995-07-17 19:12 ` Zefram
1995-07-18 10:27 ` P.Stephenson
1995-07-18 14:29 ` Mark Borges
1995-07-18 21:31 ` Zefram
1995-07-17 13:15 ` Vinnie Shelton
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=1813.9507171008@pyro.swan.ac.uk \
--to=p.stephenson@swansea.ac.uk \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).