On 8/22/20 5:25 PM, George R Goffe wrote: > > Chet, > > I'm really perplexed with this situation. I type in "ls -al 123456<tab>" with > only 1 tab key. NO indication of what's happening. I hit enter and get a > message that "ls: cannot access '123456': No such file or directory" I try > the same command but with 2 tab keys... hit enter and get the same msg.
Readline defaults to a visual bell, using the terminal's `vb' capability. You can set the readline `bell-style' variable to `audible' to change that. If you do, make sure your terminal emulator does something reasonable with the ^G character. > I tried the same with a partial filename that DOES exist in the directory. I > can't seem to get the filename completion to ctrl-c out. gdb sees the ctrl-c > but bash stays in the attempted filename completion. Enter doesn't work. > Ctrl-c doesn't work. Ctrl-z doesn't work. I just can't reproduce this. (Though there's no reason to expect ^Z to have any effect, since we're not running a separate job here.) > > Shouldn't there be a message about no file found presented by bash? There > appears to be NO indication that filename completion has failed to find a > file. Why would a message be appropriate here? It seems to me that the visible or audible bell is the right indicator. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/