Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16818
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Is this a bug? |
| Date | 2020-08-26 09:11 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.1333.1598447471.2469.bug-bash@gnu.org> (permalink) |
| References | (12 earlier) <b095f41a-da61-375c-945e-422ab06b4156@case.edu> <1955786957.6888236.1598300159108@mail.yahoo.com> <32267efb-4c8b-3a38-10a4-eb620e6c3ffd@case.edu> <1658471205.7502354.1598384875406@mail.yahoo.com> <5edfa1ed-2165-fc27-fa97-719ee35bec21@case.edu> |
On 8/25/20 3:47 PM, George R Goffe wrote: > Chet, > > I appreciate your help with this. > > Do "we" know that bash IS trying to generate an alarm? Yes, we are fairly sure that bash is trying to `ring' the bell. When I run bind 'set bell-style audible' and type the common prefix of a set of filenames in the current directory, then hit TAB, bash rings the bell. -- ``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
Re: Is this a bug? Chet Ramey <chet.ramey@case.edu> - 2020-08-26 09:11 -0400
csiph-web