help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: whence output varies with dot vs. realpath in $PATH
Date: Mon, 31 Oct 2022 17:55:28 -0700	[thread overview]
Message-ID: <fd587a85-a78f-3118-29ee-afff2f91b763@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7bGBsYwAsESmZp0TzU-Khu7OtZV2sMewC+Kz69xdOz=KA@mail.gmail.com>

On 2022-10-31 17:31, Bart Schaefer wrote:
> No.  -m means to find all the names (in any hash table) that match a
> pattern.  -a means to show all the occurrences in $path of each name
> (either literally without -m, or found in the command hash table by
> -m).  -m happens first, and then -a searches the path.
That's a better explanation right there than in the docs.  I was only 
saying how I think it should work, how it *does* work is only now made 
> Whether a full path appears there depends on how the function was
> defined.  The only way you get the output with "... from ..." but
> without the full path is if you source the function from a file in the
> current directory (e.g., "source rap").

Ah!  so the full path information isn't even retained anywhere. Once 
it's in memory it doesn't matter.  But if I do this:

2 /aWorking/Zsh/Source/Wk 5 $ . $(realpath ./rap)

... whence shows me this:

rap is a shell function from /aWorking/Zsh/Source/Wk/rap

... because the full path is actually available at the time of 
sourcing.  There is always a way.

  reply	other threads:[~2022-11-01  0:56 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
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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd587a85-a78f-3118-29ee-afff2f91b763@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \


* 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


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).