Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: =?utf-8?Q?Lawrence_Vel=C3=A1zquez?= <vq@larryv.me>
Newsgroups: gnu.bash.bug
Subject: Re: hash -l with empty hash table prints to stdout
Date: Wed, 17 Jun 2020 00:27:55 -0400
Lines: 24
Approved: bug-bash@gnu.org
Message-ID: <mailman.2037.1592368082.2541.bug-bash@gnu.org>
References: <20200615204717.GB28118@jar> <bd77214b-2690-f5de-a814-108e5be8b6f1@case.edu> <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>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: Eli Schwartz <eschwartz@archlinux.org>, bug-bash@gnu.org
To: chet.ramey@case.edu
Envelope-to: bug-bash@gnu.org
In-Reply-To: <083a2961-fd80-fbc8-4cf6-7ea30cf0c8e7@case.edu>
Received-SPF: pass client-ip=66.111.4.28; envelope-from=vq@larryv.me; helo=out4-smtp.messagingengine.com
X-Spam_score_int: -27
X-Spam_score: -2.8
X-Spam_bar: --
X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN
X-Spam_action: no action
X-Content-Filtered-By: Mailman/MimeDel 2.1.23
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <6BEEDF71-B645-4ED3-96DF-D97B9BDE3759@larryv.me>
X-Mailman-Original-References: <20200615204717.GB28118@jar> <bd77214b-2690-f5de-a814-108e5be8b6f1@case.edu> <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>
Xref: csiph.com gnu.bash.bug:16396

> 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