zsh-users
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: zsh-users@zsh.org
Subject: Re: prevent some lines directly coming from the history from being executed
Date: Thu, 26 May 2022 15:53:29 +0000	[thread overview]
Message-ID: <20220526155329.GF19001@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <20220526143602.GA1236826@zira.vinc17.org>

Vincent Lefevre wrote on Thu, May 26, 2022 at 16:36:02 +0200:
> On 2022-05-25 18:25:40 -0700, Bart Schaefer wrote:
> > On Wed, May 25, 2022 at 1:49 AM Vincent Lefevre <vincent@vinc17.net> wrote:
> > > zle -A accept-line real-accept-line
> > 
> > There's the built-in ".accept-line" widget for this sort of thing, so
> > you don't have to create a new alias.
> 
> Is this documented?
> 
> When searching the man pages, I could find only one place where
> such a built-in is used: in the example for recursive-edit.

There's this in compsys.yo:

> Should you need to use the original completion commands, you can still
> bind keys to the old widgets by putting a `tt(.)' in front of the
> widget name, e.g. `tt(.expand-or-complete)'.

And this in mod_complist.yo:

> All movement functions wrap around at the edges; any other zle function not
> listed leaves menu selection and executes that function.  It is possible to
> make widgets in the above list do the same by using the form of the widget
> with a `tt(.)' in front.  For example, the widget `tt(.accept-line)' has
> the effect of leaving menu selection and accepting the entire command line.

but, yes, it should be mentioned in the zle documentation too, not only
in the compsys documentation.

Anyone volunteering to write the patch?

Cheers,

Daniel


  reply	other threads:[~2022-05-26 15:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 15:47 Vincent Lefevre
2022-05-24 18:58 ` Bart Schaefer
2022-05-25  2:54   ` Vincent Lefevre
2022-05-25  3:59     ` Bart Schaefer
2022-05-25  8:49       ` Vincent Lefevre
2022-05-26  1:25         ` Bart Schaefer
2022-05-26 14:36           ` Vincent Lefevre
2022-05-26 15:53             ` Daniel Shahaf [this message]
2022-05-26 16:13               ` Peter Stephenson
2022-05-27 12:40                 ` Daniel Shahaf
2022-05-28  0:07                   ` Vincent Lefevre
2022-05-28 10:06                     ` Daniel Shahaf
2022-05-28 18:43                       ` Bart Schaefer
2022-05-29 22:55                         ` Daniel Shahaf
2022-05-30  4:04                           ` Bart Schaefer
2022-05-30  9:07                             ` Peter Stephenson
2022-06-02  9:59                               ` Daniel Shahaf
2022-06-02 10:19                               ` Daniel Shahaf
2022-06-02  9:59                             ` Daniel Shahaf
2022-05-30  9:02                       ` Vincent Lefevre
2022-06-02 10:17                         ` Daniel Shahaf
2022-06-02 13:54                           ` Vincent Lefevre
2022-05-26 16:37             ` 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=20220526155329.GF19001@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=vincent@vinc17.net \
    --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).