GNU bug report logs - #7965
file util doesn't note CRLF in troff input

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 7965 in the body.
You can then email your comments to 7965 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: Doug McIlroy <doug <at> cs.dartmouth.edu>
To: bug-coreutils <at> gnu.org
Subject: file util doesn't note CRLF in troff input
Date: Wed, 02 Feb 2011 11:22:30 -0500

When file-5.03 and file-5.04 identify "troff or preprocessor
input" that contains CRLF line terminators, they fail to report 
the CRLF property.  While the distinction doesn't matter
to the groff suite, it does to other utilities.  It is wrong
to hide it.

Doug McIlroy

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

From: Eric Blake <eblake <at> redhat.com>
To: Doug McIlroy <doug <at> cs.dartmouth.edu>
Cc: 7965 <at> debbugs.gnu.org
Subject: Re: bug#7965: file util doesn't note CRLF in troff input
Date: Wed, 02 Feb 2011 12:00:16 -0700

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

On 02/02/2011 09:22 AM, Doug McIlroy wrote:
> When file-5.03 and file-5.04 identify "troff or preprocessor
> input" that contains CRLF line terminators, they fail to report 
> the CRLF property.  While the distinction doesn't matter
> to the groff suite, it does to other utilities.  It is wrong
> to hide it.

Thanks for the report.  However, you reached the wrong list.  Coreutils
does not maintain file.  And it's a shame that 'file --help' doesn't
list a correct bug-reporting address, either - you now have two bugs to
report once you figure out the correct reporting address (and
unfortunately, it's hard to google for a correct address for 'filing
file bug reports', so I don't have a quick answer for where to redirect
this report).

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

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

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

From: Eric Blake <eblake <at> redhat.com>
To: christos <at> astron.com
Cc: 7965 <at> debbugs.gnu.org, Doug McIlroy <doug <at> cs.dartmouth.edu>
Subject: Re: bug#7965: file util doesn't note CRLF in troff input
Date: Wed, 02 Feb 2011 13:37:59 -0700

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

On 02/02/2011 12:00 PM, Eric Blake wrote:
> On 02/02/2011 09:22 AM, Doug McIlroy wrote:
>> When file-5.03 and file-5.04 identify "troff or preprocessor
>> input" that contains CRLF line terminators, they fail to report 
>> the CRLF property.  While the distinction doesn't matter
>> to the groff suite, it does to other utilities.  It is wrong
>> to hide it.
> 
> Thanks for the report.  However, you reached the wrong list.  Coreutils
> does not maintain file.  And it's a shame that 'file --help' doesn't
> list a correct bug-reporting address, either - you now have two bugs to
> report once you figure out the correct reporting address (and
> unfortunately, it's hard to google for a correct address for 'filing
> file bug reports', so I don't have a quick answer for where to redirect
> this report).

Follow-up - I found a bug reporting address on
http://directory.fsf.org/project/file/, so I'm adding that in cc.

Christos, even though it appears that file is not a GNU project and is
therefore not bound by the GNU Coding Standards, you are doing your
users a disservice by having 'file --help' output to stderr and lacking
any bug reporting information, particularly since it is rather difficult
to google for file's bug reporting address.  Would you mind making the
next version of file conform a bit more to those particular points of
the GNU Coding Standards, by sending --help (and --version) to stdout,
and by adding a blurb about a bug reporting address in --help?

-- 
Eric Blake   eblake <at> redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

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

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

From: christos <at> zoulas.com (Christos Zoulas)
To: Eric Blake <eblake <at> redhat.com>
Cc: 7965 <at> debbugs.gnu.org, Doug McIlroy <doug <at> cs.dartmouth.edu>
Subject: Re: bug#7965: file util doesn't note CRLF in troff input
Date: Wed, 2 Feb 2011 20:55:57 -0500

On Feb 2,  1:37pm, eblake <at> redhat.com (Eric Blake) wrote:
-- Subject: Re: bug#7965: file util doesn't note CRLF in troff input

| Follow-up - I found a bug reporting address on
| http://directory.fsf.org/project/file/, so I'm adding that in cc.
| 
| Christos, even though it appears that file is not a GNU project and is
| therefore not bound by the GNU Coding Standards, you are doing your
| users a disservice by having 'file --help' output to stderr and lacking
| any bug reporting information, particularly since it is rather difficult
| to google for file's bug reporting address.  Would you mind making the
| next version of file conform a bit more to those particular points of
| the GNU Coding Standards, by sending --help (and --version) to stdout,
| and by adding a blurb about a bug reporting address in --help?

Sure, will do.

christos

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

From: Jim Meyering <jim <at> meyering.net>
To: 7965-done <at> debbugs.gnu.org
Subject: Re: bug#7965: file util doesn't note CRLF in troff input
Date: Sat, 23 Jul 2011 00:09:14 +0200

tags 7965 + notabug
close 7965
thanks

Doug McIlroy wrote:
> When file-5.03 and file-5.04 identify "troff or preprocessor
> input" that contains CRLF line terminators, they fail to report
> the CRLF property.  While the distinction doesn't matter
> to the groff suite, it does to other utilities.  It is wrong
> to hide it.

This is not a coreutils bug.

Previous Next

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