GNU bug report logs - #13453
comm

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13453 in the body.
You can then email your comments to 13453 AT debbugs.gnu.org in the normal way.

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

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

From: Dennis Miller <DMiller <at> gohealth.com>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: comm
Date: Tue, 15 Jan 2013 16:37:21 -0600

[Message part 1 (text/plain, inline)]

Hello there,

Not really a bug per se, but a nice feature would be if a check was done to just sort the given files before hand.  If you don't sort it, you will get undesired output, and this would be a good safety check.

Thanks.

________________________________
Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.

[Message part 2 (text/html, inline)]

Message #12 received at 13453-done <at> debbugs.gnu.org (full text, mbox):

From: Eric Blake <eblake <at> redhat.com>
To: Dennis Miller <DMiller <at> gohealth.com>
Cc: 13453-done <at> debbugs.gnu.org, control <at> debbugs.gnu.org
Subject: Re: bug#13453: comm
Date: Tue, 15 Jan 2013 17:07:01 -0700

[Message part 1 (text/plain, inline)]

tag 13453 notabug
thanks

On 01/15/2013 03:37 PM, Dennis Miller wrote:
> Hello there,
> 
> Not really a bug per se,

Still, by sending a message to bug-coreutils, you've opened a bug track
id.  That is okay for feature requests (a new feature request is
arguably a bug of a missing functionality); but if you don't need to
spawn a bug id, then sending mail to coreutils <at> gnu.org is better.

> but a nice feature would be if a check was done to just sort the given files before hand.

What version of coreutils are you using?  This functionality is already
present in modern coreutils - by default, comm warns you if it gets
confused because the file is not in sorted order; comm --check-order
warns you in even more situations; and comm --nocheck-order silences the
default check.

> Privileged/Confidential Information may be contained in this message.

Unfortunately, this mail is now publicly archived, rendering this
disclaimer unenforceable.  It is considered poor netiquette to tack on
your employer's disclaimers to public lists, and we recommend using
personal email accounts to avoid the problem.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

[signature.asc (application/pgp-signature, attachment)]

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

From: Bob Proulx <bob <at> proulx.com>
To: Dennis Miller <DMiller <at> gohealth.com>
Cc: 13453 <at> debbugs.gnu.org
Subject: Re: bug#13453: comm
Date: Wed, 16 Jan 2013 09:45:18 -0700

tags 13453 + moreinfo
thanks

Dennis Miller wrote:
> Not really a bug per se, but a nice feature would be if a check was
> done to just sort the given files before hand.  If you don't sort
> it, you will get undesired output, and this would be a good safety
> check.

Have you seen the GNU comm --check-order and --nocheck-order options?
These options do exactly what you are asking for it to do.  Here is
the documentation for them from the comm docs:

     If the `--check-order' option is given, unsorted inputs will cause a
  fatal error message.  If the option `--nocheck-order' is given,
  unsorted inputs will never cause an error message.  If neither of these
  options is given, wrongly sorted inputs are diagnosed only if an input
  file is found to contain unpairable lines.  If an input file is
  diagnosed as being unsorted, the `comm' command will exit with a
  nonzero status (and the output should not be used).

     Forcing `comm' to process wrongly sorted input files containing
  unpairable lines by specifying `--nocheck-order' is not guaranteed to
  produce any particular output.  The output will probably not correspond
  with whatever you hoped it would be.

  `--check-order'
       Fail with an error message if either input file is wrongly ordered.

  `--nocheck-order'
       Do not check that both input files are in sorted order.

Bob


> Privileged/Confidential Information may be contained in this
> message. If you are not the addressee indicated in this message (or
> responsible for delivery of the message to such person), you may not
> copy or deliver this message to anyone. In such case, you should
> destroy this message and kindly notify the sender by reply
> email. Please advise immediately if you or your employer does not
> consent to Internet email for messages of this kind. Opinions,
> conclusions and other information in this message that do not relate
> to the official business of my firm shall be understood as neither
> given nor endorsed by it.

READ CAREFULLY.  By reading this email, you agree, on behalf of your
employer, to release me from all obligations and waivers arising from
any and all NON-NEGOTIATED agreements, licences, terms-of-service,
shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure,
non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I
have entered into with your employer, its partners, licensors, agents
and assigns, in perpetuity, without prejudice to my ongoing rights and
privileges.  You further represent that you have the authority to
release me from any BOGUS AGREEMENTS on behalf of your employer.

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

From: Dennis Miller <DMiller <at> gohealth.com>
To: Bob Proulx <bob <at> proulx.com>
Cc: "13453 <at> debbugs.gnu.org" <13453 <at> debbugs.gnu.org>
Subject: RE: bug#13453: comm
Date: Wed, 16 Jan 2013 10:53:37 -0600

My version doesn't have those options.  I'm running GNU coreutils 5.97-34.el5_8.1.  What version has these options?

-----Original Message-----
From: Bob Proulx [mailto:bob <at> proulx.com]
Sent: Wednesday, January 16, 2013 10:45 AM
To: Dennis Miller
Cc: 13453 <at> debbugs.gnu.org
Subject: Re: bug#13453: comm

tags 13453 + moreinfo
thanks

Dennis Miller wrote:
> Not really a bug per se, but a nice feature would be if a check was
> done to just sort the given files before hand.  If you don't sort it,
> you will get undesired output, and this would be a good safety check.

Have you seen the GNU comm --check-order and --nocheck-order options?
These options do exactly what you are asking for it to do.  Here is the documentation for them from the comm docs:

     If the `--check-order' option is given, unsorted inputs will cause a
  fatal error message.  If the option `--nocheck-order' is given,
  unsorted inputs will never cause an error message.  If neither of these
  options is given, wrongly sorted inputs are diagnosed only if an input
  file is found to contain unpairable lines.  If an input file is
  diagnosed as being unsorted, the `comm' command will exit with a
  nonzero status (and the output should not be used).

     Forcing `comm' to process wrongly sorted input files containing
  unpairable lines by specifying `--nocheck-order' is not guaranteed to
  produce any particular output.  The output will probably not correspond
  with whatever you hoped it would be.

  `--check-order'
       Fail with an error message if either input file is wrongly ordered.

  `--nocheck-order'
       Do not check that both input files are in sorted order.

Bob


> Privileged/Confidential Information may be contained in this message.
> If you are not the addressee indicated in this message (or responsible
> for delivery of the message to such person), you may not copy or
> deliver this message to anyone. In such case, you should destroy this
> message and kindly notify the sender by reply email. Please advise
> immediately if you or your employer does not consent to Internet email
> for messages of this kind. Opinions, conclusions and other information
> in this message that do not relate to the official business of my firm
> shall be understood as neither given nor endorsed by it.

READ CAREFULLY.  By reading this email, you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licences, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies ("BOGUS AGREEMENTS") that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges.  You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.

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

From: Bernhard Voelker <mail <at> bernhard-voelker.de>
To: Dennis Miller <DMiller <at> gohealth.com>
Cc: Bob Proulx <bob <at> proulx.com>,
	"13453 <at> debbugs.gnu.org" <13453 <at> debbugs.gnu.org>
Subject: Re: bug#13453: comm
Date: Wed, 16 Jan 2013 18:04:29 +0100

On 01/16/2013 05:53 PM, Dennis Miller wrote:
> My version doesn't have those options.  I'm running
> GNU coreutils 5.97-34.el5_8.1.  What version has these options?

The option --check-order has been added in coreutils-7.0 back in 2008.

Have a nice day,
Berny

Previous Next

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