[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cannot validate read -e entry when bound to TAB

From: Koichi Murase
Subject: Re: cannot validate read -e entry when bound to TAB
Date: Fri, 11 Nov 2022 08:48:38 +0900

2022年11月11日(金) 7:58 of1 <of1@disroot.org>:
> [...]
>          read -set .001 -d '' DISCARD
>          before the actual read -e
>          Alas, this does not work anymore with 5.2 (-e and -t
> combination triggers shell exit or, when used in a script, prevents
> further use of read -e).

Thanks for the report. I confirmed this.

bash-5.2$ read -et 0.5 hello

This is a regression introduced by the following commit

commit 2fe2e8197eb8f05c22a23b9d1e115d74febc8325 (HEAD)
Author: Chet Ramey <chet.ramey@case.edu>
Date:   Thu Mar 11 18:41:17 2021 -0500

    application-settable readline timeouts

This was introduced after the following discussion:


I checked the final version of the patch I submitted then, but my
patch doesn't seem to have this problem. I guess some difference
between my patch and the change actually applied would be causing the

Note: I submitted the final version of the patch in private
communications, so it is not found in the mailing-list archive. For
reproducibility, I attach to this email my final version of the patch
set I sent to Chet: r0021-patches.tar.gz. The patch set applies to
commit 26db5626.

I'll later check the details.

Attachment: r0021-patches.tar.gz
Description: application/gzip

reply via email to

[Prev in Thread] Current Thread [Next in Thread]