From: Marlon Richert <marlon.richert@gmail.com>
To: Paul <GammaFunction@vivaldi.net>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] Add execute-command() widget function (was Re: [RFC][PATCH] Add change-directory() widget function)
Date: Mon, 31 May 2021 20:55:32 +0300 [thread overview]
Message-ID: <CAHLkEDu0g43j_w-xPb6RRS103_zjW4-hi_dNnFn8o+uRTrM3YQ@mail.gmail.com> (raw)
In-Reply-To: <CAHLkEDuLk7C8iJa0zokmJGu_=cR4mPucoJz0q0xv5xPy7Gu_Bw@mail.gmail.com>
Paul, you wrote in workers/48408: "I can write a proper widget."
Any chance you might feel like continuing where I left off, below? :)
On Sat, May 1, 2021 at 4:30 PM Marlon Richert <marlon.richert@gmail.com> wrote:
>
> OK, I give up. Someone else can finish this.
>
> On Fri, Apr 30, 2021 at 11:25 PM Bart Schaefer
> <schaefer@brasslantern.com> wrote:
> >
> > I'm trying not to be a wet blanket here, but:
> >
> > You've accidentally included the doc for zrestart in the .yo patch.
> >
> > The -e option is never going to do anything useful, because send-break
> > will kill the buffer to which the command has just been written. (I
> > feel as though I've said this before about a different proposed
> > widget. Hm.) If you wrote to the buffer before calling print -z that
> > might make some sense, but more so at PS1 than PS2.
> >
> > Attempting to pass multiple commands, one per positional argument, and
> > then eval them all at once with newlines between, strikes me as
> > inviting all kinds of quoting problems, plus obscures the return
> > status if some command in the middle of the list fails.
> >
> > It's not safe to use eval that way to assign to $ops[-v], the argument
> > passed to -v might not be a simple variable name. E.g. if the user
> > forgets the variable name, the first command they intended to execute
> > will be stored there instead. Using a single well-known (documented)
> > name instead of passing an argument would avoid this, and it's not as
> > though you can have two execute-commands simultaneously that would
> > introduce a conflict.
> >
> > Other things that occurred to me not directly related to this patch:
> >
> > There's nothing preventing the user from passing more "zle" commands
> > to execute-commands which could arbitrarily mess up your print -z ...
> > heck, execute-commands could even be caused to call itself
> > recursively. This is not something you need to try to code around,
> > but it could be documented as a misuse.
> >
> > Instead of throwing an error when there are no commands provided,
> > execute-commands could invoke read-from-minibuffer to input a command
> > to run, much like the builtin execute-named-cmd does for widget names.
> > That could make execute-commands into a widget rather than just
> > something callable from widgets.
next prev parent reply other threads:[~2021-05-31 17:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 13:36 [RFC][PATCH] Add change-directory() widget function 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 [this message]
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
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=CAHLkEDu0g43j_w-xPb6RRS103_zjW4-hi_dNnFn8o+uRTrM3YQ@mail.gmail.com \
--to=marlon.richert@gmail.com \
--cc=GammaFunction@vivaldi.net \
--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).