zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: whence defect?
Date: Wed, 28 Mar 2018 09:41:07 -0700	[thread overview]
Message-ID: <329ec749-c78a-362e-b0e0-e5c8cdf7d000@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Zxb6PnDPq_+6uF4RD3ahnjceWffPT2LiN6=e_ysFXQ5A@mail.gmail.com>

On 28/03/18 08:53 AM, Bart Schaefer wrote:
> That'd get very strange to keep track of, given that "." could appear
> anywhere in the path, including at the end.  You did ask (-a) for ALL
> occurrences.
Sure, that's a legitimate way to look at it tho I'd be 60/40 the other 
way.  I want ALL occurrences but not necessarily two occurrences of 
exactly the same file viewed from two perspectives ... or, nuts, maybe 
the arbitrary location of 'dot' should be permitted to display the 
results of an overlap on the path -- that has to  be the simplest thing 
in either case.  And there is a simple fix anyway, no reason to whine 
for a change.
>
>> perhaps noted, but if it is to show up twice why would the 'dot' version not
>> show that it's a link as the explicit entry does?
> Hmm.  The code to print whether a command is a symbolic link is using
> zsh's internal symlink-chasing routine, but that method only works for
> file names starting with "/".
>
Well I'd still say that's a mistake.  '-S' says show me links and since 
the dot is a legitimate path, it should be handled, no? Following your 
logic above, if I see ALL occurrences, fine, but I should also see ALL 
data even on Tuesday.  The file IS a link and '-S' says show me that.  
Period.

... or remove the duplicate.


      reply	other threads:[~2018-03-28 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 13:06 Ray Andrews
2018-03-28 15:53 ` Bart Schaefer
2018-03-28 16:41   ` Ray Andrews [this message]

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=329ec749-c78a-362e-b0e0-e5c8cdf7d000@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).