Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16396
| From | Lawrence Velázquez <vq@larryv.me> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: hash -l with empty hash table prints to stdout |
| Date | 2020-06-17 00:27 -0400 |
| Message-ID | <mailman.2037.1592368082.2541.bug-bash@gnu.org> (permalink) |
| References | (2 earlier) <447bbb87-ce9a-e038-5a00-68646f9771c4@archlinux.org> <067bf5a9-72ba-f6f6-a170-d1ebaa54919b@case.edu> <69a0b336-4f2e-3c9f-cacf-79358ed33bf4@archlinux.org> <083a2961-fd80-fbc8-4cf6-7ea30cf0c8e7@case.edu> <6BEEDF71-B645-4ED3-96DF-D97B9BDE3759@larryv.me> |
> On Jun 16, 2020, at 10:51 AM, Chet Ramey <chet.ramey@case.edu> > wrote: > >> On 6/16/20 10:26 AM, Eli Schwartz wrote: >> >>> On 6/16/20 9:56 AM, Chet Ramey wrote: >>> >>> It's not a warning; there's nothing to warn about. An empty hash >>> table is not an exceptional condition. It's simply informational. >> >> Then would you say it is debug info? > > No, not at all. What are you trying to debug? > > Maybe it would be better to remove the message entirely and only > display it in compatibility mode. The user-friendly way to view the table is by running `hash` without arguments. It prints "hash table empty" as well, which makes sense in that context. Given that, it makes sense to me to change `hash -l`, which is expressly intended for scripting use, to output nothing when the table is empty. vq
Back to gnu.bash.bug | Previous | Next | Find similar
Re: hash -l with empty hash table prints to stdout Lawrence Velázquez <vq@larryv.me> - 2020-06-17 00:27 -0400
csiph-web