[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GNU Coding Standards for progname:file:line. (Was: Font path issue)
From: |
Ralph Corderoy |
Subject: |
GNU Coding Standards for progname:file:line. (Was: Font path issue) |
Date: |
Mon, 22 Aug 2022 09:04:46 +0100 |
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
$
--
Cheers, Ralph.
- Font path issue, Peter Schaffter, 2022/08/19
- Re: Font path issue, Deri, 2022/08/20
- Re: Font path issue, Robert Goulding, 2022/08/21
- Re: Font path issue, G. Branden Robinson, 2022/08/21
- Re: Font path issue, Ralph Corderoy, 2022/08/21
- Re: Font path issue, G. Branden Robinson, 2022/08/21
- GNU Coding Standards for progname:file:line. (Was: Font path issue),
Ralph Corderoy <=
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue), Alejandro Colomar, 2022/08/22
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue), G. Branden Robinson, 2022/08/22
- Re: GNU Coding Standards for progname:file:line. (Was: Font path issue), Alejandro Colomar, 2022/08/22
- Re: Font path issue, Deri, 2022/08/22