From: "Peter Slížik" <peter.slizik@gmail.com>
To: zsugabubus <zsugabubus@national.shitposting.agency>
Cc: zsh-users@zsh.org
Subject: Re: How to avoid infinite recursion in ZLE widgets
Date: Fri, 25 Sep 2020 16:19:45 +0200 [thread overview]
Message-ID: <CAC-uhUC8UY=SJTqdcAZM1Ja3AWAecvy7gcV0RVtKephttQRfRA@mail.gmail.com> (raw)
In-Reply-To: <CAC-uhUAFiL=LfZZ+PcYRRHgZVTyYJ5rd4r6vFWQTfkHMFNc+gQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
By the way, the documentation says that zle -R should be called after
changing the command line from within a ZLE widget.
> Redisplay the command line; this is to be called from within a
user-defined widget to allow changes to become visible.
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?
Peter
чет, 24. сеп 2020. у 11:55 Peter Slížik <peter.slizik@gmail.com> је
написао/ла:
>
>> function insert-single-quotes() {
>> LBUFFER+="'"
>> RBUFFER="'$RBUFFER"
>> }
>>
>
> Yes, this would be the best way. I wonder why I overlooked this
> possibility.
> Thanks a lot,
> Peter
>
[-- Attachment #2: Type: text/html, Size: 1348 bytes --]
next prev parent reply other threads:[~2020-09-25 14:20 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 [this message]
2020-09-25 14:43 ` Peter Stephenson
2020-09-26 9:27 ` Daniel Shahaf
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='CAC-uhUC8UY=SJTqdcAZM1Ja3AWAecvy7gcV0RVtKephttQRfRA@mail.gmail.com' \
--to=peter.slizik@gmail.com \
--cc=zsh-users@zsh.org \
--cc=zsugabubus@national.shitposting.agency \
/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).