GNU bug report logs - #70873
join --return-error-if-any-unmatched-lines

Previous Next

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

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

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: join --return-error-if-any-unmatched-lines
Date: Sat, 11 May 2024 17:14:58 +0800

join should have an option to return an error value in the shell's $?
if any lines are not matched.

Currently the man page doesn't even mention a return value. So it is not
set in stone yet.

Currently one must save -v output in a file then use test -s do detect
if there were any non-matched lines. And then exit one script with
non-zero. Big hassle.

join (GNU coreutils) 9.4

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

From: Pádraig Brady <P <at> draigBrady.com>
To: Dan Jacobson <jidanni <at> jidanni.org>, 70873 <at> debbugs.gnu.org
Subject: Re: bug#70873: join --return-error-if-any-unmatched-lines
Date: Sat, 11 May 2024 11:43:21 +0100

On 11/05/2024 10:14, Dan Jacobson wrote:
> join should have an option to return an error value in the shell's $?
> if any lines are not matched.
> 
> Currently the man page doesn't even mention a return value. So it is not
> set in stone yet.
> 
> Currently one must save -v output in a file then use test -s do detect
> if there were any non-matched lines. And then exit one script with
> non-zero. Big hassle.
> 
> join (GNU coreutils) 9.4

This does seem to have some merit.
Perhaps --check-pairable similar to the existing --check-order option.

cheers,
Pádraig

Previous Next

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