GNU bug report logs - #39017
Mention more about uniq failure exit status

Previous Next

Package: coreutils;

Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>

Date: Tue, 7 Jan 2020 17:16:01 UTC

Severity: normal

To reply to this bug, email your comments to 39017 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-coreutils <at> gnu.org:
bug#39017; Package coreutils. (Tue, 07 Jan 2020 17:16:02 GMT) Full text and rfc822 format available.
Acknowledgement sent to 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Tue, 07 Jan 2020 17:16:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-coreutils <at> gnu.org
Subject: Mention more about uniq failure exit status
Date: Wed, 08 Jan 2020 01:02:47 +0800

(info "(coreutils) uniq invocation") says
   An exit status of zero indicates success, and a nonzero value
   indicates failure.

The user wonders:
"Failure to make a file unique because it was already unique?"
Be more explicit.
This bug report was last modified 4 years and 322 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.