Hi all!
On 02/08/2022 12:29, Alejandro Colomar wrote:
[...]
Actually, I'm appending the COLOPHON right now in a very simple way (no
need for perl(1) if sh(1) can do it):
Cool - but actually sed does it;-)
find man?/ -not -type d \
|xargs sed -i "\$a \\
.SH COLOPHON\\
This page is part of rele
Hi all!
On 31/07/2022 14:38, Alejandro Colomar (man-pages) wrote:
[...]
I think I'll remove the COLOPHON. One less problem.
Or add another preprocessing step which resolves another type
of include for such cases.
Idk if resolving the /^\.so / with a simple perl/whatever script
seems useful s
Hi Bernd,
On 8/2/22 12:24, Bernd Petrovitsch wrote:
Hi all!
On 31/07/2022 14:38, Alejandro Colomar (man-pages) wrote:
[...]
I think I'll remove the COLOPHON. One less problem.
Or add another preprocessing step which resolves another type
of include for such cases.
Idk if resolving the /^\.
Hi Ingo,
On 7/31/22 14:20, Ingo Schwarze wrote:
Hi Alejandro,
Alejandro Colomar wrote on Sat, Jul 30, 2022 at 10:45:42PM +0200:
I'm wondering if it wouldn't be easier to have a constant '.so
man-pages-colophon.man' line at the end of all of the Linux man-pages,
instead of appending a COLOPHON
Hi Alejandro,
Alejandro Colomar wrote on Sat, Jul 30, 2022 at 10:45:42PM +0200:
> I'm wondering if it wouldn't be easier to have a constant '.so
> man-pages-colophon.man' line at the end of all of the Linux man-pages,
> instead of appending a COLOPHON at every release. The
> man-pages-colopho
Hi Branden,
I'm wondering if it wouldn't be easier to have a constant '.so
man-pages-colophon.man' line at the end of all of the Linux man-pages,
instead of appending a COLOPHON at every release. The
man-pages-colophon.man file would be shiped together with the pages, and
it would be created
