Hi,
On 8/2/22 22:10, DJ Chase wrote:
Would this work:
OUTPUT="$(mandoc -Tlint || true)"
OUTPUT="$(printf %s\\n "$OUTPUT" | sed '/reg/ex/d')"
if [ "$OUTPUT" ]; then
printf %s\\n "$OUTPUT"
exit 1
fi
Yes, something like that is wh
On Tue Aug 2, 2022 at 12:19 PM EDT, Alejandro Colomar wrote:
> On 8/2/22 17:51, DJ Chase wrote:
> > You could swap mandoc’s stderr and stdout, then filter it with sed and
> > redirect sed to stderr:
> >
> > mandoc -W 3>&2 2>&1 1>&3 | sed '/reg/ex/d' >&2
> >
> > Of course if mandoc also norma
Hi DJ Chase,
On 8/2/22 17:51, DJ Chase wrote:
On Tue Aug 2, 2022 at 5:55 AM EDT, Alejandro Colomar wrote:
The thing is that I'm running mandoc(1) from a Makefile, which means
that not only stdout/stderr is important, but also the exit status.
There's no trivial way to ignore mandoc(1)'s error c
Hi Ingo,
On 8/2/22 14:55, Ingo Schwarze wrote:
Hi Alejandro,
Alejandro Colomar wrote on Tue, Aug 02, 2022 at 12:58:41AM +0200:
Would you mind disabling the following warning?:
mandoc: man3type/regex_t.3type:7:5: STYLE: lower case character
in document title: TH regex_t
Yes.
[...]
Good.
On Tue Aug 2, 2022 at 5:55 AM EDT, Alejandro Colomar wrote:
> The thing is that I'm running mandoc(1) from a Makefile, which means
> that not only stdout/stderr is important, but also the exit status.
> There's no trivial way to ignore mandoc(1)'s error code for certain
> warnings. Also, I run
Hi Alejandro,
Alejandro Colomar wrote on Tue, Aug 02, 2022 at 12:58:41AM +0200:
> Would you mind disabling the following warning?:
>
> mandoc: man3type/regex_t.3type:7:5: STYLE: lower case character
> in document title: TH regex_t
Yes. Deleting that style recommendation is definitely one of th
Hi Bjarni,
On 8/2/22 02:13, Bjarni Ingi Gislason wrote:
It is simpler to use a filter, like
#!/bin/dash
mandoc -T lint $* | sed -e '/cannot parse date, using it verbatim:/d' \
-e '/empty block: UR$/d' \
-e '/: \.so is fragile, better use ln/,+3 d' \
-e '/: ignoring macro in table: /d' \
-e
On Tue, Aug 02, 2022 at 12:58:41AM +0200, Alejandro Colomar wrote:
>[...]
> Would you mind disabling the following warning?:
>
> mandoc: man3type/regex_t.3type:7:5: STYLE: lower case character in document
> title: TH regex_t
>
> :)
>
> Also, may I make you reconsider allowing one to disable spe
Hi Ingo,
On 7/23/22 20:37, Ingo Schwarze wrote:
Hi Doug,
G. Branden Robinson wrote on Fri, Jul 22, 2022 at 07:48:21AM -0500:
At 2022-07-22T07:36:03-0400, Douglas McIlroy wrote:
Changing the .TH case convention throughout the Unix world is about
as futile an effort as English spelling reform
On 7/29/22 15:22, Ingo Schwarze wrote:
What are your thoughts?
Yes, even though /usr/local/share/doc/pkgname/man/man* is a bit long,
it makes more sense than paths like
/usr/local/cyrus/man/
/usr/local/heirloom-doctools/man/
/usr/local/lib/erlang21/man/
/usr/local/lib/node_modules/
Hi Alejandro,
Alejandro Colomar wrote on Fri, Jul 29, 2022 at 02:03:51PM +0200:
> BTW, I guess you also have the POSIX man pages in BSDs. Do they come
> from the kernel repo that I maintain, or do you have your own separate
> repos?
$ less /usr/ports/books/man-pages-posix/Makefile
[...]
C
Hi Ingo,
On 7/27/22 17:32, Ingo Schwarze wrote:
Hi Alejandro,
Alejandro Colomar wrote on Sun, Jul 24, 2022 at 06:17:40PM +0200:
On 7/24/22 16:57, Ingo Schwarze wrote:
I even considered supporting aliases for manpath directories
in man.conf(5), something like being able to say
alias tcl
Hi Ingo and Branden,
On 7/27/22 18:05, Ingo Schwarze wrote:
[...]
Under this umbrella, the Linux kernel is effectively under the BSD
license.
Except that free software projects cannot copy from it - that's
quite a big BUT since allowing *everybody* to copy the code for
any purpose is the cent
Hi Branden,
G. Branden Robinson wrote on Sun, Jul 24, 2022 at 10:44:47AM -0500:
> At 2022-07-24T16:57:19+0200, Ingo Schwarze wrote:
>> But dismissing decade-old *BSD standards like the use of /usr/ for the
>> base system and /usr/local/ for packages as a standard violation, and
>> promoting /opt/
Hi Alejandro,
Alejandro Colomar wrote on Sun, Jul 24, 2022 at 06:17:40PM +0200:
> On 7/24/22 16:57, Ingo Schwarze wrote:
>> I even considered supporting aliases for manpath directories
>> in man.conf(5), something like being able to say
>>
>>alias tcl /usr/local/lib/tcl/tcl8.5/man/
>>
>> in
Hi Ingo and Branden!
On 7/24/22 16:57, Ingo Schwarze wrote:
> P.S.
> I moved this to the bottom because it is off-topic:
>
> Alejandro Colomar wrote on Sun, Jul 24, 2022 at 01:20:46PM +0200:
>> BTW, that's a thing I don't like at all from BSDs; IMO (and FHS's),
>
> Years ago, i tried to engage wi
Hi Ingo,
On 7/24/22 16:57, Ingo Schwarze wrote:
[...]
I'm not happy with this approach. I don't want to be typing paths for
system stuff (your /usr/local is /usr in GNU/Linux systems;
Then use an alias like
alias tclman='man -M /usr/local/lib/tcl/tcl8.5/man/'
It's not like users are norm
At 2022-07-24T16:57:19+0200, Ingo Schwarze wrote:
> But dismissing decade-old *BSD standards like the use of /usr/ for the
> base system and /usr/local/ for packages as a standard violation, and
> promoting /opt/ which is firmly a Linux-only invention,
Oh, no it's not. I remember that thing from
Hi Alex,
> > $ grep -m1 ^ `find -type f | sort -f | uniq -Di`
>
> I'm a big fan of pipes and xargs(1). I only use `` or $() when I
> _really_ need to. I'd use:
>
> $ find -type f | sort -f | uniq -Di | xargs grep -m1 ^
I too use xargs(1). But beware its defaults. Unless I know the nature
Hi Alejandro,
Alejandro Colomar wrote on Sun, Jul 24, 2022 at 01:20:46PM +0200:
> On 7/23/22 21:29, Ingo Schwarze wrote:
>> On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
>>> BTW, I think I didn't reply (or if I did was very short) to your comment
>>> that other languages may find it diff
Hi Ralph,
On 7/23/22 12:36, Ralph Corderoy wrote:
Hi Alejandro,
Wandering off-topic...
$ find man* -type f \
| tr '[:upper:]' '[:lower:]' \
| sort \
| uniq -d \
| while read f; do
find man* -type f \
| grep -i $f;
done;
man2/_Exit.2
man2/_exit.2
man3/nan.3
Hi Branden and Ralph,
On 7/24/22 12:25, Ralph Corderoy wrote:
Hi Branden,
Do you think I should go further and warn man page authors away from
attempting to redefine these macros in their pages?
No, I think you should go less and not change the headers and footers so
as to inspire the man-pa
Hi Branden,
On 7/23/22 21:30, G. Branden Robinson wrote:
If I were to rewrite the C library and kernel from scratch, without
backwards compatibility, I'd fix many many things. But that train
passed many years before I was born.
Lightning will not strike in the same way again. But we are engi
On 7/23/22 21:30, G. Branden Robinson wrote:
IMO system_data_types(7) bit off too much to chew. The Linux system
programming interface is a collection of independently developed
components, generally with loose coupling. At the risk of repeating
myself, I think the data types of these compon
Hi Ingo,
On 7/23/22 21:29, Ingo Schwarze wrote:
Hi Alejandro,
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
BTW, I think I didn't reply (or if I did was very short) to your comment
that other languages may find it difficult to mirror our use of
subsections, since their main section i
Hi Branden,
> Do you think I should go further and warn man page authors away from
> attempting to redefine these macros in their pages?
No, I think you should go less and not change the headers and footers so
as to inspire the man-page author to correct the deviancy. :-)
--
Cheers, Ralph.
Hi Alex,
[Dropping linux-man from the CC list as I am sure some of the kernel
hackers there, if they bother to read my remarks below, will take
offense. As they should.
By the way, I was able to follow up with a screenshot of the tm.3type
page rendered as PostScript, but it was rejected from the
Hi Alejandro,
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
> BTW, I think I didn't reply (or if I did was very short) to your comment
> that other languages may find it difficult to mirror our use of
> subsections, since their main section is already a subsection (e.g.,
> 3pl).
Othe
Hi Doug,
G. Branden Robinson wrote on Fri, Jul 22, 2022 at 07:48:21AM -0500:
> At 2022-07-22T07:36:03-0400, Douglas McIlroy wrote:
>> Changing the .TH case convention throughout the Unix world is about
>> as futile an effort as English spelling reform.
> I love a challenge.
In addition to that,
At 2022-07-23T11:51:04+0100, Ralph Corderoy wrote:
> > And, as I shall never cease to remind people, the man(7) `PT` and
> > `BT` traps are replaceable, thanks to the efforts of Larry Kollar
> > around 20 years ago.
>
> Are you saying a man-page author should work around groff's increasing
> devia
At 2022-07-23T11:51:04+0100, Ralph Corderoy wrote:
> Doug wrote:
> > > Doing it for groff-related man pages only would simply brand groff
> > > as quirky.
> ...
> > And, as I shall never cease to remind people, the man(7) `PT` and
> > `BT` traps are replaceable, thanks to the efforts of Larry Kolla
Hi Branden,
Doug wrote:
> > Doing it for groff-related man pages only would simply brand groff
> > as quirky.
...
> And, as I shall never cease to remind people, the man(7) `PT` and `BT`
> traps are replaceable, thanks to the efforts of Larry Kollar around 20
> years ago.
Are you saying a man-pag
Hi Alejandro,
Wandering off-topic...
> $ find man* -type f \
>| tr '[:upper:]' '[:lower:]' \
>| sort \
>| uniq -d \
>| while read f; do
> find man* -type f \
> | grep -i $f;
>done;
> man2/_Exit.2
> man2/_exit.2
> man3/nan.3
> man3/NAN.3
You may like to know GNU's
That tarball is not how it should be done, it unpacks in . Should
unpack in learn/
Just a FYI.
On Fri, Jul 22, 2022 at 11:43:37PM +0200, Alejandro Colomar wrote:
> Hi Branden,
>
> On 7/22/22 23:04, G. Branden Robinson wrote:
> >At 2022-07-22T20:31:08+0200, Alejandro Colomar wrote:
> >>Also, now
Hi Branden,
On 7/22/22 21:03, G. Branden Robinson wrote:
Hi Alex,
At 2022-07-22T13:46:37+0200, Alejandro Colomar wrote:
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
BTW, I think I didn't reply (or if I did was very short) to your
comment that other languages may find it difficult to
Hi Branden,
On 7/22/22 23:04, G. Branden Robinson wrote:
At 2022-07-22T20:31:08+0200, Alejandro Colomar wrote:
Also, now that we speak about these things... I've always wondered
what happened to learn(1). It's a program mentioned[1] in UNIX for
Beginners [2nd ed.; K.], that doesn't seem to ex
Hi Alex,
At 2022-07-22T20:31:08+0200, Alejandro Colomar wrote:
> On 7/22/22 14:48, G. Branden Robinson wrote:
> > intro(x) pages are sorely neglected these days, a sad situation.
> >
> > A couple of years ago someone on this list proposed a revised
> > intro(1), which people on this list found to
Hi Alex,
At 2022-07-22T13:46:37+0200, Alejandro Colomar wrote:
> On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
> > BTW, I think I didn't reply (or if I did was very short) to your
> > comment that other languages may find it difficult to mirror our use
> > of subsections, since their main
Hi Branden, Doug,
On 7/22/22 14:48, G. Branden Robinson wrote:
Hi Doug,
At 2022-07-22T07:36:03-0400, Douglas McIlroy wrote:
Changing the .TH case convention throughout the Unix world is about as
futile an effort as English spelling reform.
I love a challenge.
Doing it for groff-related man
Hi,
Colin Watson wrote on Fri, Jul 22, 2022 at 01:22:57AM +0100:
> man-db doesn't index on the .TH section at all, and I don't believe
> I've encountered the practice of doing so in other indexers
> (I could be wrong, but I think that's something I would have
> remembered if I'd noticed it).
FWI
Hi Doug,
At 2022-07-22T07:36:03-0400, Douglas McIlroy wrote:
> Changing the .TH case convention throughout the Unix world is about as
> futile an effort as English spelling reform.
I love a challenge.
> Doing it for groff-related man pages only would simply brand groff as
> quirky.
True, but on
Hi,
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
BTW, I think I didn't reply (or if I did was very short) to your comment
that other languages may find it difficult to mirror our use of
subsections, since their main section is already a subsection (e.g.,
3pl). I'd say that since C i
Changing the .TH case convention throughout the Unix world is about as
futile an effort as English spelling reform. Doing it for
groff-related man pages only would simply brand groff as quirky.
At least the current convention has the virtue of simplicity. A
convention of matching the case of comma
On 7/22/22 04:14, G. Branden Robinson wrote:
At least, _Exit(2) and _exit(2) point to the same page. nan(3) and
NAN(3) don't, though!
Pretty gross. A useful counterexample of good practice, though.
We can't blame the writers, since the identifiers have those names in
C. Luckily, man(1)
At 2022-07-21T20:34:39-0500, G. Branden Robinson wrote:
> Ah, thanks, Colin. A quick consultation of ncurses man pages reveals
> that mandb(8)'s idea of the manual section comes from its place in the
> directory hierarchy, not from parsing the arguments to the `TH` call.
> My error!
Sorry, no, I
[Colin and Ingo dropped from CC since I know they read the groff list]
Hi Alex,
At 2022-07-22T01:16:49+0200, Alejandro Colomar wrote:
> On 7/21/22 20:36, G. Branden Robinson wrote:
> > At 2022-07-21T16:29:21+0200, Alejandro Colomar wrote:
> > > I've never been convinced about the page title being
At 2022-07-22T01:22:57+0100, Colin Watson wrote:
> On Fri, Jul 22, 2022 at 01:16:49AM +0200, Alejandro Colomar wrote:
> > On 7/21/22 20:36, G. Branden Robinson wrote:
> > > At 2022-07-21T16:29:21+0200, Alejandro Colomar wrote:
> > > > Also, does it have any functional implications? I'm especially
On Fri, Jul 22, 2022 at 01:16:49AM +0200, Alejandro Colomar wrote:
> On 7/21/22 20:36, G. Branden Robinson wrote:
> > At 2022-07-21T16:29:21+0200, Alejandro Colomar wrote:
> > > Also, does it have any functional implications? I'm especially
> > > interested in knowing if that may affect in any way
Hi Branden,
On 7/21/22 20:36, G. Branden Robinson wrote:
Hi Alex,
At 2022-07-21T16:29:21+0200, Alejandro Colomar wrote:
I've never been convinced about the page title being in all caps in
the .TH line. From recent groff@ discussions, I guess that neither of
you are either.
Well, Ingo was mo
49 matches
Mail list logo
