Re: public inbox for groff

[CC trimmed; keep just groff@] Hi, On Mon, Mar 31, 2025 at 09:55:20AM -0400, Frank Ch. Eigler wrote: > Hi - > > > Many GNU projects have a public inbox at . > > That's significantly more comfortable to follow threads than archives > > like

public inbox for groff

Hi! Many GNU projects have a public inbox at . That's significantly more comfortable to follow threads than archives like , so it would be interesting to have a public inbox for groff too. Would you mind adding it? Thanks!

Re: public inbox for groff

On Tue, Apr 01, 2025 at 12:18:35PM +0200, Alejandro Colomar wrote: > Hi Mark, > > On Tue, Apr 01, 2025 at 12:11:53PM +0200, Mark Wielaard wrote: > > Hi Alex, > > > > On Mon, Mar 31, 2025 at 05:35:40PM +0200, Alejandro Colomar via Overseers > > wrote: >

Re: public inbox for groff

Hi Mark, On Tue, Apr 01, 2025 at 12:11:53PM +0200, Mark Wielaard wrote: > Hi Alex, > > On Mon, Mar 31, 2025 at 05:35:40PM +0200, Alejandro Colomar via Overseers > wrote: > > The public inbox of gcc@ doesn't replace the archive, but rather > > complement it. That is

Re: public inbox for groff

Hi, Many GNU projects have a public inbox at . That's significantly more comfortable to follow threads than archives like , so it would be interesting to have a public inbox for groff too. Would you mind adding it? Thanks!

Re: public inbox for groff

Hi Marc, On Mon, Mar 31, 2025 at 05:25:55PM +0200, Marc Chantreux wrote: > I really like the GNU mailing list archives because they are available > in mbox format: > > https://lists.gnu.org/archive/mbox/groff/ > > so I can have local copies, find stuff with mutt search patterns, index > with mai

Re: Report a Plan9 bug

Hi onf, On Sun, Feb 09, 2025 at 09:17:56PM +0100, onf wrote: > Hi Alex, > > On Sun Feb 9, 2025 at 8:11 PM CET, Alejandro Colomar wrote: > > This is off-topic, but I don't know where to ask. > > > > Thing is, I found a bug in a Plan9 string API: seprintf(2). > &

Report a Plan9 bug

Hi, This is off-topic, but I don't know where to ask. Thing is, I found a bug in a Plan9 string API: seprintf(2). I discussed the bug with Doug some time ago, and ISTR that we agreed that the API has a design bug. And we might be able to fix it. But I don't know who maintains that code. I thin

Re: [PATCH v1] CONTRIBUTING.d/style/c: Add coding style for the example programs

[CC += Ingo] Hi Branden, On Sat, Feb 08, 2025 at 06:45:31PM -0600, G. Branden Robinson wrote: > https://git.savannah.gnu.org/cgit/groff.git/tree/tmac/an.tmac?h=1.23.0#n162 Hmmm. What would be affected by changing that default? Does it affect anything other than a literal tab in source code? I

Re: [PATCH v1] CONTRIBUTING.d/style/c: Add coding style for the example programs

Hi Branden, On Sat, Feb 08, 2025 at 05:46:19PM -0600, G. Branden Robinson wrote: > _If_ you advise the use of tab characters _only_ when filling is > disabled, as, apropos of the Subject line, is the case in (displayed) > code examples, you should be fine. Yes, I'm proposing using tabs exclusivel

Re: duffman(1) (was: diffman(1))

Hi onf, On Fri, Jan 10, 2025 at 05:30:59AM +0100, onf wrote: > Hi Alex, > > On Thu Jan 9, 2025 at 2:59 PM CET, Alejandro Colomar wrote: > > I have added a duffman(1) program (script) to the Linux man-pages repo. > > It is similar to diffman(1), but it diffs the git workin

Re: SY $3

[CC += Michael Kerrisk] Hi Ingo, On Thu, Jan 09, 2025 at 08:07:34PM +0100, Ingo Schwarze wrote: > Hi, > > Alejandro Colomar wrote on Wed, Jan 08, 2025 at 09:32:25PM +0100: > > > So, let's break the line before the first parameter if it would overrun > > the

duffman(1) (was: diffman(1))

n:~/src/linux/man-pages/man-pages/contrib$ git show 437e4afec6ca commit 437e4afec6cae16ba75587f835acee1e251f2e75 Author: Alejandro Colomar Date: Sun Jan 5 13:44:32 2025 +0100 man/man3/sem_open.3: SYNOPSIS: This is a variadic function Specify

Re: SY $3

Hi Ingo, On Wed, Jan 08, 2025 at 08:57:04PM +0100, Ingo Schwarze wrote: > > alx@devuan:~/tmp/groff$ cat sy.man > > .TH a s d f > > .SH g > > .SY 123456789_123456789_123456789 > > 123456789_123456789_123456789_123456789_123456789_123456789 > > So you are talking about a combin

SY $3

Hi Branden, I have a proposal for SY: a third parameter, optional (of course), allowing me to specify the width at which to wrap: alx@devuan:~/tmp/groff$ cat sy.man .TH a s d f .SH g .SY 123456789_123456789_123456789 123456789_123456789_123456789_123456789

Re: Proposed: QS/QE macros for quotation in man(7)

Hi Branden, On Fri, Dec 20, 2024 at 11:42:38AM GMT, G. Branden Robinson wrote: > > As GNU make(1) maintainer says (IIRC), don't write portable Makefiles, > > write GNU Makefiles, and port GNU make(1). > > These days the maintainer is Paul Smith. I don't know if he said that > originally, Here's

Re: Proposed: QS/QE macros for quotation in man(7)

Hi Branden, On Thu, Dec 19, 2024 at 09:31:49PM -0600, G. Branden Robinson wrote: > > I prefer \[lq] and \[rq] over .QS and .QE. > > If everybody just used groff (please feel free to start!), I wouldn't > bother with this proposal, for that precise reason. My proposal is > stimulated in part by e

Re: Proposed: QS/QE macros for quotation in man(7)

Hi onf, On Fri, Dec 20, 2024 at 02:21:00AM +0100, onf wrote: > Hi Alejandro, > > On Fri Dec 20, 2024 at 12:39 AM CET, Alejandro Colomar wrote: > > I prefer \[lq] and \[rq] over .QS and .QE. BTW, that's that '*' mean? > > That's string interpolat

Re: Proposed: QS/QE macros for quotation in man(7)

ndard roff since forever. Plus \% is a generic tool vs the boolean which a specific tool, and I tend to favour generic ones. For the same reason, I'm a defendant of cat(1) as a starter of a pipeline, at least when typing interactively, even if it may be considered a useless use of cat(1)

Re: Proposed: QS/QE macros for quotation in man(7)

Hi Dave, On Wed, Dec 18, 2024 at 02:48:35PM -0600, Dave Kemper wrote: > One final point unrelated to the macro names: > > > B2. It would be trivial to support the British, who use the wrong > > quotation marks^W^W^W^W^Wdrive on the wrong side of the > > road^W^W^W^W^W^W^W^Whave a differen

Re: Build error in Devuan stable

Hi Branden, On Mon, Dec 16, 2024 at 08:43:18AM GMT, G. Branden Robinson wrote: > At 2024-12-16T15:24:25+0100, Alejandro Colomar wrote: > > I see on the archives that you replied, but I didn't get a copy. You > > probably dropped me from CC. :-( > > Sure. I'm af

Re: Build error in Devuan stable

Hi Branden, On Sun, Dec 01, 2024 at 03:03:15PM GMT, Alejandro Colomar wrote: > Hi Branden, > > Do you intend to fix this? Should I report a bug in Savannah? I see on the archives that you replied, but I didn't get a copy. You probably dropped me from CC. :-( Would you mind

Re: on the need for better quotation in man(7) (was: names of ISO 8859 encodings)

Hi Branden, Dave, On Sun, Dec 15, 2024 at 11:30:27PM -0600, Dave Kemper wrote: > On Sat, Dec 14, 2024 at 12:02 PM G. Branden Robinson > wrote: > > This is likely due for a cleaned up re-proposal under the new names > > `QS`/`QE` as suggested by Doug McIlroy. I still don't know what to ex

Nested SY/YS

Hi Branden, I was wondering if it would be good to nest SY/YS. What do you think of this?: .SY void\~*bsearch ( .BI const\~void\~ key [. size ], .BI const\~void\~ base [. size \~*\~. n ], .BI size_t\~ n , .BI size_t\~ size , .br -.BI int\~(* compar )(const\~void\~[. size ], +.SY int\~(*\f[

Re: Build error in Devuan stable

Hi Branden, Do you intend to fix this? Should I report a bug in Savannah? Cheers, Alex On Mon, Nov 25, 2024 at 12:36:49AM +0100, Alejandro Colomar wrote: > On Sun, Nov 24, 2024 at 11:43:57PM +0100, onf wrote: > > On Sun Nov 24, 2024 at 10:52 PM CET, Alejandro Colomar wrote: > >

Re: diffman(1)

Hi onf, On Mon, Nov 25, 2024 at 05:08:48PM +0100, onf wrote: > Hi Alejandro, > > On Mon Nov 25, 2024 at 1:44 PM CET, Alejandro Colomar wrote: > > You may find it useful for development of manual pages. If so, please > > let me know any feedback you have for it. I was

Re: diffman(1)

On Mon, Nov 25, 2024 at 01:44:07PM +0100, Alejandro Colomar wrote: > Hi! > > I've developed a new program (actually, a bash script) that diffs manual > pages. I find it quite useful for quickly seeing differences between a > page as installed in the system, and the file

diffman(1)

Hi! I've developed a new program (actually, a bash script) that diffs manual pages. I find it quite useful for quickly seeing differences between a page as installed in the system, and the file I'm working on. The output is diff -u of formatted manual pages (suitable for less -R). You can find

Re: Build error in Devuan stable

Hi onf, Branden, On Sun, Nov 24, 2024 at 11:43:57PM +0100, onf wrote: > On Sun Nov 24, 2024 at 10:52 PM CET, Alejandro Colomar wrote: > > I'm having a build error when trying to build groff HEAD in Devuan > > stable. ./bootstrap and ./configure succeed, and them make(1) fai

Build error in Devuan stable

Hi Branden, I'm having a build error when trying to build groff HEAD in Devuan stable. ./bootstrap and ./configure succeed, and them make(1) fails. Below is the failure. Let me know if you need more details. Have a lovely night! Alex --- GEN doc/groff.dvi This is pdfTeX, Version 3.1415

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

Hi Colin, On Sun, Nov 03, 2024 at 12:47:23AM +, Colin Watson wrote: > I'm not trying to stop you committing whatever you want to your > repository, of course, but I want to be clear that this doesn't actually > solve the right problem for manual page indexing. The point of the > parsing code

Re: [PATCH v2 1/3] scripts/bash_aliases: man_lsfunc(), man_lsvar(): Use mansect(1)

D'oh. Ignore this thread, please. I'm a bit rusty with git-send-email(1), it seems. On Sun, Nov 03, 2024 at 02:16:47AM +0100, Alejandro Colomar wrote: > Remove the man_section() function, and call the mansect(1) program > instead. > > Signed-off-by: Alejandro Col

[PATCH v2 4/4] src/bin/mansect: Preprocess with preconv(1)

This doesn't process the pages in a significant way, and has the benefit that it writes the name of the pages in the output. Signed-off-by: Alejandro Colomar --- src/bin/mansect | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/bin/mansect b/src/bin/mansect

[PATCH v2 2/3] scripts/bash_aliases: man_lsfunc(), man_lsvar(): Use pcre2grep(1) instead of pcregrep(1)

pcregrep(1) is obsolete. Signed-off-by: Alejandro Colomar --- scripts/bash_aliases | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/bash_aliases b/scripts/bash_aliases index 25425c389..98b466410 100644 --- a/scripts/bash_aliases +++ b/scripts/bash_aliases

[PATCH v2 3/4] scripts/bash_aliases: man_lsfunc(), man_lsvar(): Use pcre2grep(1) instead of pcregrep(1)

pcregrep(1) is obsolete. Signed-off-by: Alejandro Colomar --- scripts/bash_aliases | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/bash_aliases b/scripts/bash_aliases index 25425c389..98b466410 100644 --- a/scripts/bash_aliases +++ b/scripts/bash_aliases

[PATCH v2 1/3] scripts/bash_aliases: man_lsfunc(), man_lsvar(): Use mansect(1)

Remove the man_section() function, and call the mansect(1) program instead. Signed-off-by: Alejandro Colomar --- scripts/bash_aliases | 45 ++-- 1 file changed, 6 insertions(+), 39 deletions(-) diff --git a/scripts/bash_aliases b/scripts/bash_aliases

[PATCH v2 3/3] src/bin/mansect: Preprocess with preconv(1)

This doesn't process the pages in a significant way, and has the benefit that it writes the name of the pages in the output. Signed-off-by: Alejandro Colomar --- src/bin/mansect | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/bin/mansect b/src/bin/mansect

[PATCH v2 2/4] scripts/bash_aliases: man_lsfunc(), man_lsvar(): Use mansect(1)

Remove the man_section() function, and call the mansect(1) program instead. Signed-off-by: Alejandro Colomar --- scripts/bash_aliases | 45 ++-- 1 file changed, 6 insertions(+), 39 deletions(-) diff --git a/scripts/bash_aliases b/scripts/bash_aliases

[PATCH v2 1/4] src/bin/mansect, mansect.1: Add program and its manual page

Cc: "G. Branden Robinson" Cc: Colin Watson Cc: Signed-off-by: Alejandro Colomar --- man/man1/mansect.1 | 61 ++ src/bin/mansect| 26 2 files changed, 87 insertions(+) create mode 100644 man/man1/mansect.1 c

[PATCH v2 0/4] Add mansect(1)

Hi Colin, Branden, I've further optimized the script to be 3x faster, simpler and more robust. It now also prints the filename in the output, by calling preconv(1), which is necessary for doing the job that mandb(8) does (see patch 4/4). Cheers, Alex Alejandro Colomar (4): src/bin/ma

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

[CC trimmed] Hi Colin, On Sun, Nov 03, 2024 at 12:24:54AM +, Colin Watson wrote: > On Sun, Nov 03, 2024 at 01:05:34AM +0100, Alejandro Colomar wrote: > > Are you sure? With a small tweak, I get the following comparison: > > > > alx@devuan:~/src/linux/man-pages

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

On Sun, Nov 03, 2024 at 01:05:42AM +0100, Alejandro Colomar wrote: > Hi Colin, > > On Sat, Nov 02, 2024 at 11:47:14PM +, Colin Watson wrote: > > On Sat, Nov 02, 2024 at 10:36:20PM +0100, Alejandro Colomar wrote: > > > This is quite naive, and will not work with pag

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

Hi Colin, On Sat, Nov 02, 2024 at 11:47:14PM +, Colin Watson wrote: > On Sat, Nov 02, 2024 at 10:36:20PM +0100, Alejandro Colomar wrote: > > This is quite naive, and will not work with pages that define their own > > stuff, since this script is not groff(1). But it shoul

Re: [PATCH] CONTRIBUTING.d/patches: Document new features alongside the features

Oops, this was sent by accident. :) On Sun, Nov 03, 2024 at 12:10:18AM +0100, Alejandro Colomar wrote: > Link: <https://lwn.net/Articles/989380/> > Cc: Jiri Olsa > Cc: Günther Noack > Signed-off-by: Alejandro Colomar > --- > > [offlist] > > Hi Günther, Ji

Re: [PATCH 1/3] signal.7: Better description for SIGFPE

Oops, this was sent by accident. On Sun, Nov 03, 2024 at 12:10:27AM +0100, Alejandro Colomar wrote: > From: Vincent Lefevre > > SIGFPE has comment "Floating-point exception", which corresponds to > the FPE acronym. But this is misleading as this signal may also be >

[PATCH 2/3] src/bin/mansect, mansect.1: Add program and its manual page

Cc: "G. Branden Robinson" Cc: Colin Watson Cc: Signed-off-by: Alejandro Colomar --- man/man1/mansect.1 | 61 ++ src/bin/mansect| 33 + 2 files changed, 94 insertions(+) create mode 100644 man/man1/mansect.1 c

[PATCH 3/3] scripts/bash_aliases: man_section(), man_lsfunc(), man_lsvar(): Use mansect(1)

Signed-off-by: Alejandro Colomar --- scripts/bash_aliases | 38 ++ 1 file changed, 6 insertions(+), 32 deletions(-) diff --git a/scripts/bash_aliases b/scripts/bash_aliases index e461707c8..0b0b5e08a 100644 --- a/scripts/bash_aliases +++ b/scripts

[PATCH 1/3] signal.7: Better description for SIGFPE

Library manual says "fatal arithmetic error". Link: <https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/signal.h.html> Link: <https://www.gnu.org/software/libc/manual/html_node/Program-Error-Signals.html> Signed-off-by: Vincent Lefevre Signed-off-by: Alejandro Colo

[PATCH 0/3] Add mansect(1) program and manual page

Linux man‐pages (unrelea... (date) mansect(1) What do you think of it? Have a lovely night! Alex Alejandro Colomar (2): src/bin/mansect, mansect.1: Add program and its manual page scripts/bash_aliases: man_section(), man_lsfunc(), man_lsvar(): Use mansect(1) V

[PATCH] CONTRIBUTING.d/patches: Document new features alongside the features

Link: <https://lwn.net/Articles/989380/> Cc: Jiri Olsa Cc: Günther Noack Signed-off-by: Alejandro Colomar --- [offlist] Hi Günther, Jiri, I've prepared a draft of this contributing process that we talked about. I won't officially post it until the other situation (sponsor

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

Hi Branden, Colin, On Sat, Nov 02, 2024 at 11:40:13AM +0100, Alejandro Colomar wrote: > > I also of course have ideas for generalizing the feature, so that you > > can request any (sub)section by name, and, with a bit more ambition,[4] > > paragraph tags (`TP`) too. > &

Re: [PATCH v2 1/3] proc_pid_fdinfo.5: Reduce indent for most of the page

Hi Branden, On Sat, Nov 02, 2024 at 05:08:37AM -0500, G. Branden Robinson wrote: > [adding Colin Watson to CC; and the groff list because I started musing] > > Hi Alex, > > At 2024-11-01T21:07:29+0100, Alejandro Colomar wrote: > > > > > -/proc/pid/fdinfo/ \- info

Re: C Strings and String Literals. (Was: Pascal rides again)

(2 years later...) Hi Doug! On 11/13/22 23:39, Douglas McIlroy wrote: > > Wouldn't it be nice to use -Wunterminated-strings and let the > > compiler yell at me if I write a string literal [that's too long]? > > A good idea. Assuming you use gcc, please propose it at > https://gcc.gnu.org/bugzilla

Re: YS .

On Sat, Jul 13, 2024 at 10:46:17AM GMT, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-07-13T17:38:17+0200, Alejandro Colomar wrote: > > > Try the attached patches. > > > > They don't seem to apply. > > Alas, that's life when you're

Re: YS .

Hi Branden, On Sat, Jul 13, 2024 at 10:12:32AM GMT, G. Branden Robinson wrote: > Hi Alex, > > At 2024-07-13T09:32:10-0500, G. Branden Robinson wrote: > > Yes, sort of--it seems I managed to screw it up. On top of that I > > wrote a particularly dumb test for it. :) > Try the attached patches.

YS .

Hi Branden, Was the trailing dummy string for YS to allow alignment finally merged? I built groff(1) from git HEAD and lost that functionality. Below is the head of a manual page for libs, a string library that I'm writing: $ cat stpeprintf.3 .\" Copyright 2024

Re: [PATCH v5 00/10] strtol(3)-related fixes

Hi Branden, On Fri, Jul 12, 2024 at 01:48:39PM GMT, G. Branden Robinson wrote: > Hi Alex, > > At 2024-07-10T11:41:15+0200, Alejandro Colomar wrote: > > How is that? I would expect git-am(1) to work. > [...] > > What I do is on neomutt(1), while reading the email --and

Re: [PATCH v5 00/10] strtol(3)-related fixes

If you supply directories, they will be treated as Maildirs. Please let me know if this doesn't work for you. Have a lovely day! Alex > > Regards, > Branden > > At 2024-03-16T13:34:28+0100, Alejandro Colomar wrote: > > This v5 further documents which commits i

Re: -Thtml double free in tcache 2; Abort

On Thu, Jun 20, 2024 at 01:54:57PM GMT, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-06-17T23:23:03+0200, Alejandro Colomar wrote: > > On Mon, Jun 17, 2024 at 01:43:38PM GMT, G. Branden Robinson wrote: > > > Until grohtml's putatively sloppy handli

Re: -Thtml double free in tcache 2; Abort

Hi Branden, On Mon, Jun 17, 2024 at 01:43:38PM GMT, G. Branden Robinson wrote: > Me neither. > > I bisected it down to this. > > 0951ff53e47cfc8dda792e23f2111268bd3dd81b is the first bad commit > commit 0951ff53e47cfc8dda792e23f2111268bd3dd81b > Author: G. Branden Robinson > Date: Thu Aug 10

Re: man: EX/EE nested within nf/fi

On Sun, Jun 16, 2024 at 05:16:25PM GMT, G. Branden Robinson wrote: > Hi Alex, > > At 2024-06-16T23:14:56+0200, Alejandro Colomar wrote: > > Branden, how about using some register in EX/EE so that it can nest > > within nf/fi? > > In your scenario I would advise the

Re: man: EX/EE nested within nf/fi

On Sun, Jun 16, 2024 at 05:16:25PM GMT, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-06-16T23:14:56+0200, Alejandro Colomar wrote: > > Branden, how about using some register in EX/EE so that it can nest > > within nf/fi? > > In your scenario I would advi

Re: man: EX/EE nested within nf/fi

Hi Doug, Branden, On Tue, Jun 11, 2024 at 07:58:51PM GMT, Douglas McIlroy wrote: > > I'd structure what you have like this: > > > > .nf > > .EX > > ... > > .EE > > .fi > > .EX/.EE is too dumb for this. Anything between .EE and .fi will get > filled, which is almost certainly contrary to the purp

Re: -Thtml double free in tcache 2; Abort

On Sun, Jun 16, 2024 at 10:10:38PM GMT, Alejandro Colomar wrote: > Hi Branden, > > In the git HEAD of the man pages repository, I can reproduce a bug in > groff -Thtml: > > alx@debian:~/tmp/groff$ cat keyrings.7 > .TH a s d f > .SH foo > .TP > foobar > alx@debi

-Thtml double free in tcache 2; Abort

Hi Branden, In the git HEAD of the man pages repository, I can reproduce a bug in groff -Thtml: alx@debian:~/tmp/groff$ cat keyrings.7 .TH a s d f .SH foo .TP foobar alx@debian:~/tmp/groff$ troff -man -Thtml <./keyrings.7 >/dev/null free(): double free detected in tcache 2 Aborted alx@debian:~/

Re: prepare.pl looping forever

On Thu, Jun 13, 2024 at 05:11:15PM GMT, Alejandro Colomar wrote: > Hi Deri! > > I've triggered a forever loop in the scripts that produce the Linux > man-pages PDF book. Whoops! I created a page which is a .so to itself, accidentally. Never mind. Cheers, Alex -- <h

prepare.pl looping forever

Hi Deri! I've triggered a forever loop in the scripts that produce the Linux man-pages PDF book. I think the problem is in prepare.pl, since top(1) shows it stuck at around 100% CPU. It doesn't call anything groff internally, so it's just an issue in the perl code. However, it might be interest

Re: man: EX/EE nested within nf/fi

On Tue, Jun 11, 2024 at 07:52:30AM GMT, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-06-10T21:24:54+0200, Alejandro Colomar wrote: > > Hi Branden, > > > > Is it correct to nest EX/EE within nf/fi? > > It's harmless. "Correct" is a qu

man: EX/EE nested within nf/fi

Hi Branden, Is it correct to nest EX/EE within nf/fi? $ cat nfi.man .TH EXE 7 2024-06-10 alx .SH Name nf \- EX .SH SYNOPSIS .nf .B #include .P .EX struct { int a; int b; };

Re: Proposed v2: revised man(7) synopsis macros

Hi Branden, On Sun, May 05, 2024 at 04:11:21PM +0200, Alejandro Colomar wrote: > On Sun, May 05, 2024 at 08:54:53AM -0500, G. Branden Robinson wrote: > > Hi Alex, > > Hi Branden, > > > At 2024-05-05T14:41:44+0200, Alejandro Colomar wrote: > > > Thanks! >

Re: Proposed v2: revised man(7) synopsis macros

You did s/vger/lore/ and now the mail is bouncing. :-) -- signature.asc Description: PGP signature

Re: Proposed v2: revised man(7) synopsis macros

On Sun, May 05, 2024 at 08:54:53AM -0500, G. Branden Robinson wrote: > Hi Alex, Hi Branden, > At 2024-05-05T14:41:44+0200, Alejandro Colomar wrote: > > Thanks! > > > > I'm trying it already in liba2i, since it's a project that I don't > > expec

Re: Proposed v2: revised man(7) synopsis macros

On Sun, May 05, 2024 at 02:41:44PM +0200, Alejandro Colomar wrote: > Hi Branden, > > On Fri, May 03, 2024 at 03:31:26PM -0500, G. Branden Robinson wrote: > > At 2024-04-26T11:32:06+0200, Alejandro Colomar wrote: > > > > My questions: > > > > > > >

Re: Proposed v2: revised man(7) synopsis macros

Hi Branden, On Fri, May 03, 2024 at 03:31:26PM -0500, G. Branden Robinson wrote: > At 2024-04-26T11:32:06+0200, Alejandro Colomar wrote: > > > My questions: > > > > > > A. Does anyone object to me committing this change to groff's > > > master br

Re: man(7) <-> mdoc(7) (approximate) correspondence table?

Hi Alexis, On Sat, Apr 27, 2024 at 04:17:28PM +1000, Alexis wrote: > [ Not subscribed to the linux-man list, so please cc me if replying there. ] > > Hi all, > > As someone who's much more familiar with mdoc(7) than man(7), is there an > approximate 'correspondence table' somewhere that gives at

Re: Proposed v2: revised man(7) synopsis macros

t; `in` and `ti` requests. > * An example document, renderable with groff Git HEAD, 1.23.0, 1.22.4, > and 1.22.3 (at least), illustrating use of these macros. View it with > "nroff -man". > > My questions: > > A. Does anyone object to me committing this change to

Re: Proposed: revised man(7) synopsis macros

On Tue, Apr 23, 2024 at 08:19:55PM -0500, G. Branden Robinson wrote: > Hi folks, Hi folk, > I have been dissatisfied with groff man(7)'s SY and YS macros for a long > time. My primary grievance is one that has frustrated its uptake by > documenters of libraries: the macros are designed for synop

Re: Problems building the unifont PFA and DIT files for the PDF book

Hi Dave, On Sat, Apr 20, 2024 at 11:19:24PM -0500, Dave Kemper wrote: > Would you be willing to open a savannah request for this feature? > > https://savannah.gnu.org/bugs/?group=groff&func=additem > > afmtodit falls under category "Utilities." Thanks! Done.

Re: Problems building the unifont PFA and DIT files for the PDF book

Hi Brian, On Sat, Apr 20, 2024 at 02:11:55PM -0600, Brian Inglis wrote: > On 2024-04-20 09:52, G. Branden Robinson wrote: > > At 2024-04-20T14:26:17+0200, Alejandro Colomar wrote: > > > First problem: > > > > > > In the Unifont, I don't see a "Reg

Re: Problems building the unifont PFA and DIT files for the PDF book

Hi Branden, On Sat, Apr 20, 2024 at 10:52:31AM -0500, G. Branden Robinson wrote: > Since (I believe I saw you say that) you're using GNU Unifont only to > patch up missing code point coverage from other fonts, in your > application it probably makes sense to specify it as a "special" font. > > af

Problems building the unifont PFA and DIT files for the PDF book

Hi, I've tried groff-ifying the Unifont, in the same way I do it with the Tinos font. However, I've had a few problems. Here's the Tinos font that's packaged with Debian: $ apt-file find tinos | grep ttf texlive-fonts-extra-links: /usr/share/texlive/texmf-dist/fonts/truetype/go

Re: A primer on font installation for groff (was: gropdf(1)'s 'Font installation' section is opaque to me)

On Fri, Apr 19, 2024 at 12:36:39PM -0500, G. Branden Robinson wrote: > At 2024-04-19T19:34:19+0200, Alejandro Colomar wrote: > > On Thu, Apr 18, 2024 at 08:33:39PM -0500, G. Branden Robinson wrote: > > > B. afmtodit(1) must be run to produce a groff font description file >

Re: A primer on font installation for groff (was: gropdf(1)'s 'Font installation' section is opaque to me)

Hi Branden, On Thu, Apr 18, 2024 at 08:33:39PM -0500, G. Branden Robinson wrote: > B. afmtodit(1) must be run to produce a groff font description file > from the AFM file. BTW, what does 'dit' mean in afmtodit(1)? It seems like a very weird way to spell fdf. :) Cheers, Alex > > C. The

Re: A primer on font installation for groff (was: gropdf(1)'s 'Font installation' section is opaque to me)

> On Fri, Apr 19, 2024 at 04:43:49AM +0200, Jan Eden wrote: > > The process is explained in detail by Walter Alejandro Iglesias on the > > blog I referenced earlier[1], > > and he also provides a shell script > > (similar to Peter's explanation and script[2]). > > > > [1] https://technicallywewri

Re: A primer on font installation for groff (was: gropdf(1)'s 'Font installation' section is opaque to me)

On Fri, Apr 19, 2024 at 04:43:49AM +0200, Jan Eden wrote: > Hi Alejandro, Hi Jan, > On 2024-04-18 20:33, G. Branden Robinson wrote: [...] > > The process is explained in detail by Walter Alejandro Iglesias on the > blog I referenced earlier[1], I must have missed it. I don't find any mails fr

Re: A primer on font installation for groff (was: gropdf(1)'s 'Font installation' section is opaque to me)

Hi Branden, On Thu, Apr 18, 2024 at 08:33:39PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-04-19T00:29:37+0200, Alejandro Colomar wrote: > > While the above is interesting, I've already read similar explanations > > from you in related threads. However, I

Re: gropdf(1)'s 'Font installation' section is opaque to me

Hi Branden, On Thu, Apr 18, 2024 at 02:03:50PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-04-18T18:00:09+0200, Alejandro Colomar wrote: > > Hi, > > > > I find the following section very opaque. > > > > Font installation > >

gropdf(1)'s 'Font installation' section is opaque to me

Hi, I find the following section very opaque. Font installation The following is a step‐by‐step font installation guide for gropdf. • Convert your font to something groff understands. This is a PostScript Type 1 font in PFA or PFB format, together with an

Re: [PATCH v2] tzfile.5: Fix indentation

gt; when filling is disabled. (This would be kin to TeX's notoriously > discouraging "overfull hbox" warnings, but if I can't write a diagnostic > message more intelligible than that, I'll put in for retirement.) Since manual pages often have a few levels of indent

Re: [PATCH v2] tzfile.5: Fix indentation

Hi Paul, Branden, On Sun, Apr 07, 2024 at 11:33:38PM -0700, Paul Eggert wrote: > On 2024-03-18 01:35, Alejandro Colomar wrote: > > > Hmm, while Ossana's indents might be a bit excessive, TZDB's might be > > too short. Maybe I would RS 4 spaces instead of 2 before

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 05:45:14PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-22T21:24:10+0100, Alejandro Colomar wrote: > > Heh, we're comparing different things. I'm comparing `eqn -Tps` to > > nothing at all, while you're compa

Re: Running the grohtml pipeline as a pipeline

On Fri, Mar 22, 2024 at 03:15:11PM -0500, G. Branden Robinson wrote: > At 2024-03-22T20:56:28+0100, Alejandro Colomar wrote: > > I'm quite surprised that you aren't even getting the warning due to > > `eqn -Thtml`. > > I did. I elided it. I also elided nearly all

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 02:44:26PM -0500, G. Branden Robinson wrote: > At 2024-03-22T20:10:51+0100, Alejandro Colomar wrote: > > It reduces the base paragraph inset (did I use the right term? :) to > > almost nothing. > > I have to say I regard this as a pretty m

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 01:53:51PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-18T12:38:30+0100, Alejandro Colomar wrote: > > I'm considering using grohtml(1) in the Linux man-pages, to replace > > man2html(1), which crashes on tzfile(5)

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

On Fri, Mar 22, 2024 at 05:56:58PM +, Deri wrote: > On Friday, 22 March 2024 16:59:14 GMT Alejandro Colomar wrote: > > ow, how am I supposed to > > get that patch without anyone tampering it during its trip to my > > computer? :( > > derij@ws:~$ md5sum

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

Hi Branden! On Fri, Mar 22, 2024 at 11:30:11AM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-17T23:44:07+0100, Alejandro Colomar wrote: > > On Sun, Mar 17, 2024 at 05:23:20PM -0500, G. Branden Robinson wrote: > > > Following up my earlier announcement r

Running the grohtml pipeline as a pipeline

Hi Branden, I'm considering using grohtml(1) in the Linux man-pages, to replace man2html(1), which crashes on tzfile(5) --which has correct man(7)--. Currently, I'm running groff(1) as its separate constituents: $ make build-ps -Wman2/membarrier.2 PRECONV .tmp/man/man2/me

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

Hi Branden! On Sun, Mar 17, 2024 at 05:23:20PM -0500, G. Branden Robinson wrote: > Hi folks, > > Following up my earlier announcement regarding man(7),[1], I'm pleased > to report that we have a functioning PDF hyperlink story for the mdoc > package. > > * The Mt macro hyperlinks email addresses

Re: [PATCH v2] tzfile.5: Fix indentation

On Sun, Mar 17, 2024 at 08:53:22PM +0100, Alejandro Colomar wrote: > Hi Branden, > > On Sun, Mar 17, 2024 at 08:31:55PM +0100, Alejandro Colomar wrote: > > Hmmm, I was about to say inset, but double-checked groff_man(7) to be > > sure of the exact term, and then I g

Re: [PATCH v2] tzfile.5: Fix indentation

Hi Branden, On Sun, Mar 17, 2024 at 08:31:55PM +0100, Alejandro Colomar wrote: > Hmmm, I was about to say inset, but double-checked groff_man(7) to be > sure of the exact term, and then I got confused even more: > > $ man groff_man | grep ' \.\(IP\|RS\) \[' > .RS

  1   2   3   4   5   6   7   >