Re: Enabling the fix for echo_input_at_read in run_debug_trap?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Enabling the fix for echo_input_at_read in run_debug_trap?
Date	2020-05-04 08:47 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.2057.1588596476.3066.bug-bash@gnu.org> (permalink)
References	<CAB5Rqonp_tv50b7392SjxdjEffgCtQE_i2L1=AsUmnmLehQ3jA@mail.gmail.com> <489551d3-1975-9656-1797-6e0ceacfee75@case.edu>

Show all headers | View raw

On 5/2/20 3:05 AM, George Nachman wrote:
> One of my users complained that the debug trap was printing their command
> after edit-and-execute-command when using my script, which depends on debug
> traps. I noticed that bash 5.0 made this change to run_debug_trap() that
> would fix the problem:

There was a discussion about this in early April:

https://lists.gnu.org/archive/html/bug-bash/2020-04/msg00016.html

and I put a change in the devel branch in the bash-20200406 snapshot push.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Enabling the fix for echo_input_at_read in run_debug_trap? Chet Ramey <chet.ramey@case.edu> - 2020-05-04 08:47 -0400

csiph-web