zsh-users
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Ray Andrews" <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: whence output varies with dot vs. realpath in $PATH
Date: Mon, 31 Oct 2022 19:14:25 -0400	[thread overview]
Message-ID: <128a1ff4-1af4-4d5f-b2e9-754daa6d9016@app.fastmail.com> (raw)
In-Reply-To: <1f246a94-944c-cbc3-27af-43a34b90151d@eastlink.ca>

On Mon, Oct 31, 2022, at 6:59 PM, Ray Andrews wrote:
> On 2022-10-31 14:18, Bart Schaefer wrote:
>> The "zsh is zsh" output means you have an empty path element, e.g. two
>> consecutive colons in $PATH or $PATH begins or ends with colon, and an
>> executable or link named "zsh" in the current directory.
>>
>
>> 2 /aWorking/Zsh/Source/Wk 1 $ echo $PATH
>> /aWorking/Zsh/Source/Wk:/usr/local/bin:/usr/sbin:/usr/bin:
>>
> Thereyago, I'll kill that trailing colon.  Still, it seems like 
> something that should be ignored.

Why should whence ignore it?  An empty PATH element actually means
something to PATH searches; it is not cosmetic.

-- 
vq


  parent reply	other threads:[~2022-10-31 23:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 13:30 Ray Andrews
2022-10-31 13:43 ` Roman Perepelitsa
2022-10-31 14:06   ` Ray Andrews
2022-10-31 14:10     ` Roman Perepelitsa
2022-10-31 14:32       ` Ray Andrews
2022-10-31 14:36         ` Roman Perepelitsa
2022-10-31 14:57           ` Ray Andrews
2022-10-31 21:18             ` Bart Schaefer
2022-10-31 22:26               ` Bart Schaefer
2022-10-31 22:59               ` Ray Andrews
2022-10-31 23:03                 ` Bart Schaefer
2022-10-31 23:17                   ` Ray Andrews
2022-10-31 23:21                     ` Bart Schaefer
2022-10-31 23:14                 ` Lawrence Velázquez [this message]
2022-10-31 23:21                   ` Ray Andrews
2022-10-31 23:38                     ` Bart Schaefer
2022-11-01  0:03                       ` Ray Andrews
2022-11-01  0:31                         ` Bart Schaefer
2022-11-01  0:55                           ` Ray Andrews
2022-11-01  1:08                             ` 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=128a1ff4-1af4-4d5f-b2e9-754daa6d9016@app.fastmail.com \
    --to=larryv@zsh.org \
    --cc=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).