From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: "Peter Slížik" <peter.slizik@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: How to avoid infinite recursion in ZLE widgets
Date: Sat, 26 Sep 2020 09:27:00 +0000 [thread overview]
Message-ID: <20200926092700.01784063@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <322971271.67362.1601044983375@mail2.virginmedia.com>
Peter Stephenson wrote on Fri, 25 Sep 2020 15:43 +0100:
> > On 25 September 2020 at 15:19 Peter Slížik <peter.slizik@gmail.com> wrote:
> > By the way, the documentation says that zle -R should be called after
> > changing the command line from within a ZLE widget.
> >
> > However, when playing with LBUFFER and RBUFFER I realized that zle -R is
> > not needed and the changes are visible immediately.
> >
> > Why is it so?
>
> You only need to call zle -R either if you are passing it an argument
> to show, or if you are bypassing the editor interface somehow so it
> doesn't know the display has changed. If you use any of the special
> variables or a zle command to update the command line then ZLE's
> internals are all consistent and you don't need any special action.
diff --git a/Doc/Zsh/zle.yo b/Doc/Zsh/zle.yo
index 84be010e1..885366c8c 100644
--- a/Doc/Zsh/zle.yo
+++ b/Doc/Zsh/zle.yo
@@ -502,7 +502,8 @@ ifnzman(noderef(Completion Widgets))\
)
item(tt(-R) [ tt(-c) ] [ var(display-string) ] [ var(string) ... ])(
Redisplay the command line; this is to be called from within a user-defined
-widget to allow changes to become visible. If a var(display-string) is
+widget to allow changes made directly to the terminal (bypassing ZLE) to become
+visible. If a var(display-string) is
given and not empty, this is shown in the status line (immediately
below the line being edited).
next prev parent reply other threads:[~2020-09-26 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 8:34 Peter Slížik
2020-09-23 11:21 ` Peter Stephenson
2020-09-23 11:24 ` Peter Slížik
2020-09-23 11:29 ` Daniel Shahaf
2020-09-23 11:32 ` Peter Slížik
2020-09-23 18:25 ` zsugabubus
2020-09-24 9:55 ` Peter Slížik
2020-09-25 14:19 ` Peter Slížik
2020-09-25 14:43 ` Peter Stephenson
2020-09-26 9:27 ` Daniel Shahaf [this message]
2020-09-26 9:40 ` Roman Perepelitsa
2020-09-26 10:24 ` Daniel Shahaf
2020-09-26 10:31 ` Roman Perepelitsa
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=20200926092700.01784063@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=peter.slizik@gmail.com \
--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).