From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>,
Marlon Richert <marlon.richert@gmail.com>
Subject: Re: [RFC][PATCH] Add change-directory() widget function
Date: Wed, 21 Apr 2021 13:29:44 -0700 [thread overview]
Message-ID: <CAH+w=7ZuXWVbjrU3_qPSsd8qwhB-56uYhhqK7zYO3LiXbhzCUw@mail.gmail.com> (raw)
In-Reply-To: <20210421201139.GD21343@tarpaulin.shahaf.local2>
On Wed, Apr 21, 2021 at 1:12 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Bart Schaefer wrote on Tue, Apr 20, 2021 at 20:18:24 -0700:
> > On Tue, Apr 20, 2021 at 3:14 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > >
> > > Should any of the words be quoted to protect against global aliases?
> >
> > This is generally speaking a fruitless task.
>
> How so? «PM_UNALIASED» turns «noaliases» on for the duration of parsing
> the function itself, not for the duration of parsing the code which the
> function dumps into $BUFFER when executed.
Ah, I misunderstood the scope of "any of the words".
I'm of two minds on this one. Totally agree regarding e.g. "builtin
cd". OTOH if for some reason I have a global alias for "+1" or "-0" I
might actually want it expanded here (I'm having a hard time
visualizing a use case for such an alias in the first place).
Marlon's latest effort to generalize this as "execute-command" pushes
responsibility for all of the foregoing onto the caller.
prev parent reply other threads:[~2021-04-21 20:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 13:36 Marlon Richert
2021-04-20 19:43 ` Bart Schaefer
2021-04-20 20:13 ` Marlon Richert
2021-04-20 21:32 ` Bart Schaefer
2021-04-21 3:46 ` Bart Schaefer
2021-04-21 11:37 ` [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function) Marlon Richert
2021-04-21 20:40 ` Bart Schaefer
2021-04-21 21:27 ` Daniel Shahaf
2021-04-21 21:58 ` Bart Schaefer
2021-04-22 10:55 ` Marlon Richert
2021-04-22 20:25 ` Daniel Shahaf
2021-04-22 23:27 ` Bart Schaefer
2021-04-24 20:06 ` Marlon Richert
2021-04-24 21:49 ` Bart Schaefer
2021-04-24 21:58 ` Bart Schaefer
2021-04-26 18:08 ` Marlon Richert
2021-04-26 21:39 ` Bart Schaefer
2021-04-27 10:46 ` Marlon Richert
2021-04-27 19:27 ` Bart Schaefer
2021-04-30 19:16 ` Marlon Richert
2021-04-30 20:25 ` Bart Schaefer
2021-05-01 13:30 ` Marlon Richert
2021-05-31 17:55 ` Marlon Richert
2021-04-25 17:02 ` Hard-wrapping emails (Was: [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function)) Lawrence Velázquez
2021-04-20 21:57 ` [RFC][PATCH] Add change-directory() widget function Daniel Shahaf
2021-04-20 22:14 ` Daniel Shahaf
2021-04-21 0:09 ` Bart Schaefer
2021-04-21 3:18 ` Bart Schaefer
2021-04-21 20:11 ` Daniel Shahaf
2021-04-21 20:29 ` Bart Schaefer [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='CAH+w=7ZuXWVbjrU3_qPSsd8qwhB-56uYhhqK7zYO3LiXbhzCUw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=marlon.richert@gmail.com \
--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).