From: dana <dana@dana.is>
To: "Jun T" <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: ksh compatibility: initial value of $_
Date: Wed, 05 Apr 2023 03:14:06 -0500 [thread overview]
Message-ID: <838816ad-0337-452b-94d1-e18a17c33c78@app.fastmail.com> (raw)
In-Reply-To: <2A0716F2-F80B-4357-87AA-0A9881A52CEC@kba.biglobe.ne.jp>
On Tue 4 Apr 2023, at 11:24, Jun. T wrote:
> The following is my revised path.
> # Since $_ is almost always set in environment (though sometimes
> # not useful), this may be going too far (or to excess, don't know
> # the correct words).
I had written a patch very very similar to this in 2018 because of
workers/42193 (as well as users/22875, users/18199, &c.). I wasn't thinking
about $_ at the time; instead, i had created a ZSH_EXECUTABLE_PATH parameter
that resolved the path the first time it was referenced, because i was worried
that it was too niche to waste I/O on it for every invocation of the shell. In
the end i didn't submit the patch because it still felt too elaborate...
Anyway, would it make sense to revive the idea of having a dedicated variable
for it, so you can get the absolute path to the shell regardless of the
environment or what commands might have run before you could capture $_? That
would somewhat address your fear that it's too excessive for how rarely it'd
be used, at least
PS: bash has a similar dedicated parameter, just called BASH... but it doesn't
try to be this accurate about it. If it's a log-in shell, it will use $SHELL,
otherwise it basically does the 'guess the absolute pathname' part of your
getmypath()
dana
next prev parent reply other threads:[~2023-04-05 8:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 1:52 Bart Schaefer
2023-03-23 10:40 ` Jun T
2023-03-31 8:18 ` Jun T
2023-03-31 14:31 ` Jun. T
2023-03-31 17:45 ` Bart Schaefer
2023-04-03 11:16 ` Jun. T
2023-04-03 16:48 ` Bart Schaefer
2023-03-31 19:02 ` Bart Schaefer
2023-03-31 19:03 ` Bart Schaefer
2023-04-03 12:13 ` Jun. T
2023-04-03 16:50 ` Bart Schaefer
2023-04-04 16:24 ` Jun. T
2023-04-05 1:03 ` Oliver Kiddle
2023-04-05 8:15 ` zeurkous
2023-04-05 9:00 ` Oliver Kiddle
2023-04-05 16:24 ` Jun. T
2023-04-05 8:14 ` dana [this message]
2023-04-05 18:16 ` Jun. T
2023-04-08 4:03 ` dana
2023-04-08 16:22 ` Oliver Kiddle
2023-04-09 13:30 ` Jun. T
2023-04-10 0:51 ` Jun T
2023-04-15 5:02 ` Felipe Contreras
2023-04-15 22:24 ` 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=838816ad-0337-452b-94d1-e18a17c33c78@app.fastmail.com \
--to=dana@dana.is \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@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).