Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16385
| From | Eli Schwartz <eschwartz@archlinux.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: hash -l with empty hash table prints to stdout |
| Date | 2020-06-16 09:46 -0400 |
| Message-ID | <mailman.1977.1592315194.2541.bug-bash@gnu.org> (permalink) |
| References | <20200615204717.GB28118@jar> <bd77214b-2690-f5de-a814-108e5be8b6f1@case.edu> <447bbb87-ce9a-e038-5a00-68646f9771c4@archlinux.org> |
[Multipart message — attachments visible in raw view] - view raw
On 6/16/20 9:30 AM, Chet Ramey wrote: > On 6/15/20 4:47 PM, beluro@web.de wrote: > >> Bash Version: 5.0 >> Patch Level: 3 >> Release Status: release >> >> Description: > >> `hash -l' is supposed to generate output that is reusable as input >> (`help hash' says so, at least). In case the hash table is empty, a >> string not re-usable as input is output to stdout. The exit code >> indicates success in this case. The string being output is locale- >> dependant (and therefore is hard to filter out in a work-around). > > It's an interesting question. An empty hash table is not an error > condition, and doesn't result in a non-zero exit status, so output to > stderr is not appropriate. You might want to temporarily enable posix mode, > which suppresses the message. stderr is also a reasonably appropriate place to emit debug info or warnings. I would consider this a warning condition... -- Eli Schwartz Arch Linux Bug Wrangler and Trusted User
Back to gnu.bash.bug | Previous | Next | Find similar
Re: hash -l with empty hash table prints to stdout Eli Schwartz <eschwartz@archlinux.org> - 2020-06-16 09:46 -0400
csiph-web