From: Ray Andrews <rayandrews@eastlink.ca>
To: "Lawrence Velázquez" <vq@larryv.me>
Cc: zsh-users@zsh.org
Subject: Re: symlink chain.
Date: Fri, 02 Jan 2015 13:19:59 -0800 [thread overview]
Message-ID: <54A70B7F.70203@eastlink.ca> (raw)
In-Reply-To: <74193E12-E858-4733-B713-3548A9C69393@larryv.me>
On 01/02/2015 12:27 PM, Lawrence Velázquez wrote:
> On Jan 2, 2015, at 1:42 PM, Ray Andrews <rayandrews@eastlink.ca> wrote:
>
>> Do you think 'whence' would benefit from showing the chain if '-s' is specified? Maybe it's just me, but I want no surprises when I use whence, I want complete information about what any typed command it actually going to end up executing and a roadmap of any and all links as to how it got there.
> I would consider this undesirable noise, and I think most users would agree. The point of `whence` is to "indicate how [the argument] would be interpreted if used as a command name". I don't care about the chain of links, I just want to know what ends up being run.
Yup, at the end of the day it's what people find useful. I myself have
had so much grief for not realizing that the way whence 'jumps' like
that is infact a jump, that I'm biased against it. I dunno, maybe '-S'
could mean 'show the entire chain', but it looks like I'm the only guy
who's worried about it and the devs have better things to think about.
But I would change the symbol where this jumping happens "->>" or
something like that, just so you know.
next prev parent reply other threads:[~2015-01-02 21:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 4:50 Ray Andrews
2014-12-27 23:38 ` Ray Andrews
2015-01-02 17:03 ` Peter Stephenson
2015-01-02 18:42 ` Ray Andrews
2015-01-02 20:27 ` Lawrence Velázquez
2015-01-02 21:19 ` Ray Andrews [this message]
2015-01-02 21:24 ` Peter Stephenson
2015-01-02 21:36 ` Ray Andrews
2015-01-02 21:53 ` Ray Andrews
2015-01-02 22:21 ` Peter Stephenson
2015-01-02 23:42 ` Ray Andrews
2015-01-03 1:08 ` Ray Andrews
2015-01-03 5:03 ` Bart Schaefer
2015-01-03 5:53 ` Ray Andrews
2015-01-03 7:17 ` Bart Schaefer
2015-01-03 17:14 ` Ray Andrews
2015-01-03 20:02 ` Bart Schaefer
2015-01-03 21:13 ` Ray Andrews
2015-01-03 21:42 ` Peter Stephenson
2015-01-03 22:42 ` Ray Andrews
2015-01-04 0:41 ` Bart Schaefer
2015-01-04 3:45 ` Ray Andrews
2015-01-04 0:40 ` Bart Schaefer
2015-01-04 3:35 ` Ray Andrews
2015-01-04 8:31 ` Bart Schaefer
2015-01-04 20:49 ` Ray Andrews
2015-01-05 1:34 ` Bart Schaefer
2015-01-05 2:28 ` Lawrence Velázquez
2015-01-05 4:24 ` Ray Andrews
2015-01-02 22:22 ` Bart Schaefer
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=54A70B7F.70203@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=vq@larryv.me \
--cc=zsh-users@zsh.org \
/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).