Re: Is this a bug?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: Is this a bug?
Date	2020-08-19 08:57 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.339.1597841888.2469.bug-bash@gnu.org> (permalink)
References	(2 earlier) <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu> <1312274972.4025864.1597785278610@mail.yahoo.com> <6575997b-0217-046a-8ef1-0437571475ca@case.edu> <1699062943.4171052.1597809756404@mail.yahoo.com> <16e6944b-9707-a80c-3602-e76edcca64ec@case.edu>

Show all headers | View raw

On 8/19/20 12:02 AM, George R Goffe wrote:
> Chet,
> 
> I've been thinking about what you've said below... that bash is waiting for input. If this were the case, ctrl-c would return to the bash prompt immediately. Yes? What I'm seeing is that with a partial filename entered followed by the tab key is hit which results in nothing due to an uninterriputible sleep. Ctrl-c does not stop the filename completion process.
> 
> Does this make any sense?

If that were the case, and it might be, the pselect is a red herring.
The filename completion process doesn't use pselect.

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: Is this a bug? Chet Ramey <chet.ramey@case.edu> - 2020-08-19 08:57 -0400

csiph-web