zsh-workers
 help / color / mirror / code / Atom feed
From: Vinnie Shelton  <shelton@spacely.icd.teradyne.com>
To: Zefram <A.Main@dcs.warwick.ac.uk>
Cc: zsh-workers@math.gatech.edu (Z Shell workers mailing list)
Subject: Re: Compctl fixes & a query
Date: Mon, 17 Jul 1995 14:17:54 -0400	[thread overview]
Message-ID: <9507171817.AA01709@spacely.afive> (raw)
In-Reply-To: A.Main's message of Mon, 17 Jul 1995 18:17:51 +0100. <27816.199507171717@stone.dcs.warwick.ac.uk>

In message <27816.199507171717@stone.dcs.warwick.ac.uk>, Zefram wrote:
>I think that, in the interests of consistency and name space
>preservation, it would be a good idea to use ~+n rather than ~n, as
>this reduces the number of characters that are treated specially.  ~+n
>and ~-n can then be interpreted however pushd interprets +n and -n,
>depending on whether PUSHD_MINUS is set or not.  What do people think
>of this?

I think that =1 is easy to type (no shift key).  I think that ~1 is a little more annoying (1 shift).  But I think that ~+1 is too cumbersome, IMHO.

Consider this:
=n is an absolute directory reference which corresponds directly to the directory stack, ie:

src/gnu Mon 17 13:59 % dirs -v
0       /pd/src/gnu
1       ~csim
2       ~
src/gnu Mon 17 13:59 % echo =1
/vobs/devel/shared/hsd100/sim

~+1 and ~-1 would refer to relative entries on the directory stack.  I prefer the absolute naming scheme, personally.

--Vin


  reply	other threads:[~1995-07-17 18:21 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
1995-07-17 17:17   ` Zefram
1995-07-17 18:17     ` Vinnie Shelton [this message]
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=9507171817.AA01709@spacely.afive \
    --to=shelton@spacely.icd.teradyne.com \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=acs@world.std.com \
    --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).