Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
[PATCH] Include number of chars in zle unget mechanism in $PENDING calculation
- X-seq: zsh-workers 40682
- From: Eric Freese <ericdfreese@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Subject: [PATCH] Include number of chars in zle unget mechanism in $PENDING calculation
- Date: Wed, 1 Mar 2017 07:41:07 -0700
- Authentication-results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=/IrkJIyi/+/WaQYSGwBzGPCTlIAE9sim1Jyayaqzjwc=; b=gbJu+5PF87+BRwaOr7i2A37wdBRMFG74v0unkY/28EeM/hhdO7d5sWSrzs+Z5cQt26 FJ+SmF4leVAsaBeUWIlUGyMYrod/WQmwiTxqJ8909LFo6XPZOZVrXDUyjAJfz9N0twPl E4XZO6y0iDJVfH0IvqUdgSgPh37MZWvMMiKTBaTCkHsBYdZcUp6+hVWK9i7VO7nfShDa dGTwPbwPcEwopERW7/PHowsFMSsfE5usVwHNgwp3DVy3mZpynKlDoLqoqxGPcBN2xpGZ ha9u2bgeDjKp/u5WQMFKA3VwTJiNLH0CgeoqXpzu5PDzIXY/hgKJZrBXBzBPBDFjLFYS bNVw==
- In-reply-to: <170228185233.ZM9032@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20170301012534.67145-1-ericdfreese@gmail.com> <170228185233.ZM9032@torch.brasslantern.com>
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@xxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author