Re: auto_resume takes effect too early in command substitution
On 8/17/20 12:15 AM, Oğuz wrote: > See: > > $ sleep 20 > ^Z > [1]+ Stopped sleep 20 > $ > $ auto_resume= sleep > sleep: missing operand > Try 'sleep --help' for more information. > $ > $ echo $(auto_resume= sleep) > bash: fg: no current jobs Thanks for the report. I'll take a look. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: Is this a bug?
On 8/18/20 5:14 PM, George R Goffe wrote: > Chet, > > > Please accept my apology for not responding to your email sooner. > > I have the bash source from the(?) repository. I followed Dimitris suggestion > and found bash hung in a system call named "pselect". I did a grep on the > source and found the only two ".c" files using "pselect": If it's in pselect, it's waiting for input. It's probably not performing completion at all. It may have read the directory, found no common prefix for the files it found, `rang' the visible bell, and gone back to waiting to read the next input character. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
Re: Is this a bug?
On Tue, Aug 18, 2020 at 7:57 PM George R Goffe wrote: > > Chet, > > Thanks for your response. > > I'm running konsoles (KDE). I have tried complettion but don't see any > evidence of bell ringing. Not even a flash. > > Do you think that bash have a problem with konsole? Maybe it's a konsole bug? > > > I'll look at konsole docs for anything that speaks of "alarm bells", visual > or otherwise and report back here. Ok? You can use pstack to see the call stack. regards, Dmitry
