From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25936 invoked by alias); 1 Mar 2017 02:52:51 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 40677 Received: (qmail 3640 invoked from network); 1 Mar 2017 02:52:50 -0000 X-Qmail-Scanner-Diagnostics: from park01.gkg.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(205.235.26.22):SA:0(0.5/5.0):. Processed in 0.885897 secs); 01 Mar 2017 02:52:50 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.5 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.1 X-Envelope-From: SRS0=o+GU=2K=brasslantern.com=schaefer@bounces.park01.gkg.net X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at bounces.park01.gkg.net does not designate permitted sender hosts) X-Virus-Scanned: by amavisd-new at gkg.net Authentication-Results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=brasslantern-com.20150623.gappssmtp.com X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=rc+26jdUGlyGHRbGGmhRhhChA9igTSAqDDl+1uhdiOI=; b=cCj180dE+NEf/aQcB36ClU/IFDP43Ex3+YPbdyIJiSCvQjgaaoEjOUgUFVkapKlwCb QuB//ajdPofxy82Q0U5AIztj45wPw1v2u5VUIXZe20xD5BBwZe/g5+tTibXqLmxFjg0X FP+yQ0k2fMQLXmEMr/IsCMH9Rkjhg+V0e8cWnuDIG+gn0DGOC11izTDTbnWltm3nleGW JdR24H1odulqEUh9O/kx6QkwAkrOwu9fJBuQB09YSFKcjXD9yN+aSdthFGBQZEizEuRR yVFcA3qapXC0+m+Ae3aAJBIeCsThsNAZVqIu1sUmwBvdAki6FtM6q7HF9BUUOzX58dLi 61yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=rc+26jdUGlyGHRbGGmhRhhChA9igTSAqDDl+1uhdiOI=; b=PXI+7n/iEDo0RJmAk/sg6/yqqTrKGu/+71Q2NupHi/FesvOMVQkB5CFgQx0pZCPIsW HRl+t28IeNvdOkns26zCAwgiqXfKg8R8/5iCRzNuTcZRFAFf+leIcRPAA2y2KtT5WM+l CJG3V2I5QrdCUUd6HyDuXjVAR12dUBhe0UxjHN1nNhlE5KcE1AY17gNlHKTxT2AUvEtP 8qWlm0OLb6sxb4Qx1p97mUdDiNOvw3r8Qy8qRzPzyrgyQVE3PUmfU0EAcMp1rcv8vwJq tem/8ewq4/69Q5cvWyUNpNQhOhJiKAXsfxgekTjK1Z/IV4aGQbkcYrsnvVf3mPKze2rw sclg== X-Gm-Message-State: AMke39kNuZuqQKkVnnnDD7fUd92Fg5fgPQve9HecRXjIaEEolg/3hNa8OHsYXnQiGeErQw== X-Received: by 10.31.169.16 with SMTP id s16mr2141436vke.21.1488336739382; Tue, 28 Feb 2017 18:52:19 -0800 (PST) From: Bart Schaefer Message-Id: <170228185233.ZM9032@torch.brasslantern.com> Date: Tue, 28 Feb 2017 18:52:33 -0800 In-Reply-To: <20170301012534.67145-1-ericdfreese@gmail.com> Comments: In reply to Eric Freese "[PATCH] Include number of chars in zle unget mechanism in $PENDING calculation" (Feb 28, 6:25pm) References: <20170301012534.67145-1-ericdfreese@gmail.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Eric Freese , zsh-workers@zsh.org Subject: Re: [PATCH] Include number of chars in zle unget mechanism in $PENDING calculation MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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."