Re: GNU Coding Standards for progname:file:line. (Was: Font path issue)

[Alejandro Colomar]

Hi Ralph, Branden,

On 8/22/22 10:04, Ralph Corderoy wrote:
> Hi Branden,
>
> > (B) I see a deviation from the GNU Coding Standards for diagnostic
> >      messages; we don't need a space after "troff:" when it's followed
> >      by a file name.
>
> It seems much of the word doesn't comply
>
>      $ sed -f /etc/passwd
>      sed: file /etc/passwd line 3: extra characters after command
>      $
>      $ awk -f /etc/passwd |& 3q
>      awk: /etc/passwd:1: root:x:0:0:root:/root:/bin/bash
>      awk: /etc/passwd:1:     ^ syntax error
>      awk: /etc/passwd:2: bin:x:1:1:bin:/bin:/usr/bin/nologin
>      $ pacman -Qo /usr/bin/awk
>      /usr/bin/awk is owned by gawk 4.2.1-2
>      $
>      $ perl /etc/passwd |& 3q
>      syntax error at /etc/passwd line 1, near "0:"
>      Unknown regexp modifier "/b" at /etc/passwd line 1, at end of line
>      Unknown regexp modifier "/b" at /etc/passwd line 1, at end of line
>      $

Also, I'd keep the space, even if only for being able to use standard 
tools like perror(3), or common tools like the <err.h> functions.

Cheers,

Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>

OpenPGP_signature
Description: OpenPGP digital signature