From: Bart Schaefer <schaefer@brasslantern.com>
To: Eric Freese <ericdfreese@gmail.com>, zsh-workers@zsh.org
Subject: Re: [PATCH] Include number of chars in zle unget mechanism in $PENDING calculation
Date: Tue, 28 Feb 2017 18:52:33 -0800 [thread overview]
Message-ID: <170228185233.ZM9032@torch.brasslantern.com> (raw)
In-Reply-To: <20170301012534.67145-1-ericdfreese@gmail.com>
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."
next prev parent reply other threads:[~2017-03-01 2:52 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 [this message]
2017-03-01 3:51 ` Eric Freese
2017-03-02 14:31 ` Peter Stephenson
2017-03-01 14:41 ` Eric Freese
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=170228185233.ZM9032@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=ericdfreese@gmail.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).