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:03:37 -0700 [thread overview]
Message-ID: <77e57f37-7d6c-5ed4-5745-c424886bf16e@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7Zq44y1eBda6xtLwinn_7+iMSj+3_sYjnuaFSK+LTnWuw@mail.gmail.com>
On 2022-10-31 16:38, Bart Schaefer wrote:
> It's an archaic synonym for ".", included for backward compatibility.
> See POSIX spec.
Not me! Nothing I need worry about. Strange tho, if you want dot on
your path then say so. I'm glad it's archaic, that's sloppy magic. BTW
as to '-a' and '-m' they sure don't get along. I have a few examples
where they seem to try to cancel each other. Seems to me that -m is an
expansion of -a: show all matches AND extend that to wildcards. So -m
subsumes -a.
> If you don't mind the overhead, you can muck around with $path in your
> chpwd function to force the full current directory to always be there.
>
Na I'm good. It's just that I want full path disclosure in my function
cuz I need the full path later on. My crude search (not prettied up
yet) seems about right:
Searching for aliases, reserved words and autoloads. Then searching the
path for regular functions, builtins (no path), and executable scripts
or binary commands ...
Found 9 match(es):
ACTIVE: RAP is an alias for echo howdy
RAP is /aWorking/Zsh/Source/Wk/RAP
ACTIVE: RAp is /aWorking/Zsh/Source/Wk/RAp
ACTIVE: RaP is /aWorking/Zsh/Source/Wk/RaP
ACTIVE: bwrap is /usr/bin/bwrap
ACTIVE: rAp is /aWorking/Zsh/Source/Wk/rAp
ACTIVE: rap is an alias for echo pard
rap is a shell function from rap
ACTIVE: select-default-iwrap is /usr/bin/select-default-iwrap
ACTIVE: _trap is an autoload shell function
ACTIVE: trap is a shell builtin
... it's all there and where we have a name conflict I know which twin
is active.
BTW, you know what would be sweet, is if: "rap is a shell function from
rap" ... if there was the option of having that displayed with full
path. Throw in a case-insensitive option and all the work I've done in
this function will be mostly obviated.
next prev parent reply other threads:[~2022-11-01 0:04 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 [this message]
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=77e57f37-7d6c-5ed4-5745-c424886bf16e@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).