From: Eric Freese <ericdfreese@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: [PATCH] Include number of chars in zle unget mechanism in $PENDING calculation
Date: Wed, 1 Mar 2017 07:41:07 -0700 [thread overview]
Message-ID: <CAAikoALbx5dP3Rn+tr_V+qSg7sijP57_a+k2YoBG1Np5ezz4mw@mail.gmail.com> (raw)
In-Reply-To: <170228185233.ZM9032@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Ok. How about a separate parameter that just returns kungetct?
My use case is disabling zsh-autosuggestions (https://github.com/zsh-
users/zsh-autosuggestions)
while bracketed-paste-magic and other
widgets using zle -U are running. Ideally, I could just avoid fetching
a suggestion until $PENDING and this new param are zero.
On Tue, Feb 28, 2017 at 7:52 PM Bart Schaefer <schaefer@brasslantern.com>
wrote:
> Yeah, this was discussed (with identical patch) back in May 2016 in
> workers/38522. It turned out not to have the desired effect so we
> didn't do anything with it.
>
> The question is whether it's useful to be able to tell that TTY read
> will not block, separately from whether ZLE has available input.
> There are cases where one might be invoking a tty read in the middle
> of a widget, before any of the "zle -U" pushback would be consumed.
>
> We'd also have to change the doc that says "where the shell is not able
> to get this information, this parameter will always have a value of zero."
>
--
Sent from my iPhone
next prev parent reply other threads:[~2017-03-01 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 1:25 Eric Freese
2017-03-01 2:52 ` Bart Schaefer
2017-03-01 3:51 ` Eric Freese
2017-03-02 14:31 ` Peter Stephenson
2017-03-01 14:41 ` Eric Freese [this message]
2017-03-03 23:54 Eric Freese
2017-03-04 14:53 ` Daniel Shahaf
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=CAAikoALbx5dP3Rn+tr_V+qSg7sijP57_a+k2YoBG1Np5ezz4mw@mail.gmail.com \
--to=ericdfreese@gmail.com \
--cc=schaefer@brasslantern.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).