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: 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

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 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

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: 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: 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

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 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: [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: [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

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: 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 > >

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: 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)

> 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)

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 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 >

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: 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

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 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: 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: 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: 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

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: 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

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

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

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! >

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: 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

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: 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

-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: -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

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: 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

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: -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: -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: [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: [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

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: 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.

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: 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: Escaping hyphens ("real" minus signs in groff)

h. > > Regards, > Branden > > [1] especially in light of the \[mi] special character escape and the > existence of U+2212 :-/ > I just found another good reason to use '\-'. I was searching for an option of curl in their man page, and I used '/-s'

[PATCH] *.man: Break URIs at points specified by the Chicago Style

xargs sed -i '/^\.UR/s,\([^/]\)/\\:,\1\\:/,g'; $ find * -type f \ | xargs grep -l 'UR.*[^/]/\\e:' \ | xargs sed -i '/UR/s,\([^/]\)/\\e:,\1\\e:/,g'; These scripts miss 2 cases, which I fixed manually (URIs that used 2 source lines). Signed-off-by: Alejandro

[BUG] -T html: \- rendered as something different than ASCII 45

mp;pasted to a terminal is different from ASCII 45, and is longer than the proper minus sign. Should I report a bug to firefox? Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

[BUG] .MR: hyperlink only on html, but not on pdf or terminal

? Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

[GUB] -T html: .EX/.EE is not monospaced

Best regards, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

[BUG] -T html: .RS/.RE incorrectly indented

ull source code at <http://www.alejandro-colomar.es/src/alx/alx/games/chessutils.git/tree/share/man/man6/chess-init.6> and the html page at <http://www.alejandro-colomar.es/man/man6/chess-init.6.html> Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

[Wishlist] .MT/.ME: The mailto link doesn't contain the name

Hi Branden, Some wish. For the following code: [ .MT alx.manpa...@gmail.com Alejandro Colomar .ME . ] The produced html output is mailto:alx.manpa...@gmail.com";>Alejandro Colomar The visual output shows the full name, but when you want to send an email, that is discarded. It

[Wishlist] Don't discard groff comments on HTML output

Hi Branden, I'd like to see groff comments preserved in the HTML output (as HTML comments). So, for `groff -T html ...`, .\" hello world would be transformed to Sounds good? Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-p

groff_man_style(7): wfix needed

these for paired directional single quotes, ‘like this’. ] What did you mean by 'a right single quotation mark'? s/right/correct/? Or maybe s/right/closing/? Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http:

How to print a literal '.' as the first character in a line?

ple: [ .EX $ echo '.' . .EE ] You get the idea, I guess. Ho do I do that? Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: How to print a literal '.' as the first character in a line?

ure, > CSTR 54 §4.1, https://troff.org/54.pdf, and > > info groff Requests | less -j12 +/precede Thank you too. Branden, any chance you may add that to any groff manual page? Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: How to print a literal '.' as the first character in a line?

Hi, Branden! On 5/2/22 00:52, G. Branden Robinson wrote: Hi, Alex-- At 2022-05-01T22:24:04+0200, Alejandro Colomar wrote: On 5/1/22 13:00, Ralph Corderoy wrote: Hi Alejandro, https://man.openbsd.org/mandoc_char#Accents https://man.openbsd.org/mandoc_char#Periods Or, more generally, which

Represent several consecutive newlines

sent precisely in EXAMPLES, but groff(1) doesn't like things like: [[ .EX .RB $ " echo -e \"\n\nHere's some text.\n\n\nAnd here's some more.\"" Here's some text. And here's some more. .EE ]] Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: Represent several consecutive newlines

Hi! On 5/9/22 18:27, G. Branden Robinson wrote: Hi, Alex! At 2022-05-09T17:44:01+0200, Alejandro Colomar wrote: Is it possible to represent the following precisely in a manual page?: Yes. It's the output of a program that I'd like to represent precisely in EXAMPLES, but groff(

Re: Represent several consecutive newlines

foo bar That was an example. groff test suite 2022‐05‐09 foo(1) ]] :( -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: Represent several consecutive newlines

Hi Branden, On 5/9/22 22:36, G. Branden Robinson wrote: Hi Alex, At 2022-05-09T18:36:44+0200, Alejandro Colomar wrote: It's not working for me. I have GNU groff version 1.23.0.rc1.2366-0328. I think our messages crossed in the ether. I suspect you're seeing man-db man(1)'s

.TQ to replace .PD 0

t -rCHECKSTYLE=3 -ww -z ./tq.7 $ mandoc -man -Tlint ./tq.7 $ Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: .TQ to replace .PD 0

On 5/21/22 16:46, Alejandro Colomar wrote: I (succesfully) tried the following: [ .TP tag1 Some text here. .TQ I missed here "tag2" Some more text. ] -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: .TQ to replace .PD 0

after we get groff 1.23.0 out. Do you have an idea of when that can be (1.23.0)? Regards, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: groff 1.23.0.rc2 readiness

Hi Branden, On 5/26/22 17:23, G. Branden Robinson wrote: [...] So, here's Mean Mr. Mustard. Anybody who's read the previous discussion(s) we've had on this list about it, or the current version of the groff_char(7) man page, will be aware of my objections (the latter because I think those objec

Re: Zero Width Space

you: How about "non-breaking escape" or "non-printing escape" (not necessarily in that order of preference)? Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/>

Re: Zero Width Space

On 6/5/22 17:07, Alejandro Colomar wrote: How about "non-breaking escape" or "non-printing escape" (not necessarily in that order of preference)? Or (I was going to suggest this one, but didn't because it is too long, but neither of those fully convinces me as

Re: Zero Width Space

ior would be as [.BR foo bar], and reported it to the mailing list a few months ago. Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

Warn on semantic newlines

something equivalent to -Wno-switch (or -Wno-error=switch), which could be nice to silence (or make non-fatal) some warnings on purpose. Do you think that could be implemented in groff(1) or mandoc(1)? Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; http://www.kerne

Re: Warn on semantic newlines

ade and refusal to countenance "$<" in target rules throw caltrops in our path again here, and will force a policy of enabling or disabling this warning for all documents in our tree using a certain macro package. I'd enable it for everyone. Why not? BTW, I guess the "no-op

Re: Warn on semantic newlines

in a specific place (because it's not a sentence ending; but just a dot), they should use \&. But if it's really a sentence ending, it should use a newline (if the warning is enabled, which means that the code base follows the semantic newlines rules); otherwise, don't enable the warning (or don't enable absolutely all warnings, which may add new warnings as this one). Regards, Alex -- Alejandro Colomar Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/ OpenPGP_signature Description: OpenPGP digital signature

Optimize string literals

applies, but I would guess that it does. Please check your source code, and see if that optimizes something in your case. Cheers, Alex [1]: <https://unit.nginx.org/> [2]: <https://www.akkadia.org/drepper/dsohowto.pdf> -- Alejandro Colomar <http://www.alejandro-colom

Re: Optimize string literals

On 6/12/22 23:35, Alejandro Colomar wrote:> I'm reporting this because I found groff's source code to be full of `const char *`, which may be open to the optimization. I forgot to show the places that use it (some of them are not optimizable (variable pointers), but most see

Re: Optimize string literals

Hi Ralph, On 6/13/22 10:51, Ralph Corderoy wrote: I think section 2.4 starting on page 26 is the relevant part, if anyone else wants to read it. Yes it is; sorry for not mentioning it. Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/>

Re: Warn on semantic newlines

on of false positives. But i'm not sure yet what to change following your present request. No problem, I'll keep suggesting stuff. >> The tool could have a secondary warning, not so important, >> for "foo, bar". > > Absolutely not. Makes sense. Cheers,

Re: man(7) .TH font change, was: groff man(7) `B` macro...

in the long term, or we will be stuck with each vendor having their own attributes syntax. The same applies to man(7) .MR, I think. Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

Re: man(7) .TH font change, was: groff man(7) `B` macro...

o happen around 2023 or 2025, depending on if groff releases before the freeze or after it. oldstable and oldoldstable can apply some .tmac fix as you suggested, if they need it to backport the Linux man-pages. I guess that by 2030 or 2040 many pages will be using .MR. Cheers, Alex -- Aleja

Re: man(7) .TH font change, was: groff man(7) `B` macro...

;s just a matter of time, I think. When .MR has been in the game for at least 15 years, we can consider that absolutely no user will have a system that lacks it. It's all a balance about how many years to wait. Regards, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

[BUG] italics run past where they should

it's a problem in groff(1). $ man -w clone | xargs mandoc | less /flags I'm running: $ groff --version GNU groff version 1.23.0.rc1.2366-0328 Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

Re: [BUG] italics run past where they should

On 7/21/22 11:25, G. Branden Robinson wrote: Hi Alex, At 2022-07-20T16:58:34+0200, Alejandro Colomar wrote: I'm not sure if this is a groff(1) bug, or less(1), or who knows... From your description I suspect a bug either in less(1) or your terminal emulator. Yup, I also had that fe

Re: [BUG] italics run past where they should

On 7/21/22 12:46, Alejandro Colomar wrote: On 7/21/22 11:25, G. Branden Robinson wrote: Hi Alex, At 2022-07-20T16:58:34+0200, Alejandro Colomar wrote: I'm not sure if this is a groff(1) bug, or less(1), or who knows...  From your description I suspect a bug either in less(1) or

Re: [BUG] italics run past where they should

Hi Branden, On 7/21/22 12:49, Alejandro Colomar wrote: On 7/21/22 12:46, Alejandro Colomar wrote: On 7/21/22 11:25, G. Branden Robinson wrote: Hi Alex, At 2022-07-20T16:58:34+0200, Alejandro Colomar wrote: I'm not sure if this is a groff(1) bug, or less(1), or who knows...  From

Re: All caps .TH page title

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, Ing

Re: All caps .TH page title

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 th

[PATCH] NULL.3def: Add documentation for NULL

Reported-by: "G. Branden Robinson" Signed-off-by: Alejandro Colomar --- Hi all! As hinted in recent mails to groff@ and linux-man@, I'm going to inaugurate a new [sub]section for constants. I think it should contain constants, normally represented by object-like macros in C.

Re: All caps .TH page title

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

learn(1) (was: a new intro(1) (was: All caps .TH page title))

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

Re: All caps .TH page title

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 diff

tbl(1) minor issues

Some of these options require a parenthesized argument; those that do, permit spaces and tabs between the option’s name and the opening parenthesis. Options accumulate and cannot be ] Expect to see more reports about that page soon :) Cheers, Alex -- Alejandro Colomar

Re: man(7) DS and DE macros (was: [PATCH 4/5] tm.3type: describe tm_zone, tm_gmtoff)

Hi Branden, On 7/23/22 00:20, G. Branden Robinson wrote: [dropped наб from CC list; added groff@] At 2022-07-22T12:57:53+0200, Alejandro Colomar (man-pages) wrote: You answered all that I thought you would, and even more. As always, you surprise me with great knowledge that I didn't

man -M tcl (was: All caps .TH page title)

't recall even one single complaint from a user who wanted the feature back or explained what they were using it for. Not one person needing it in over half a decade since it was deleted... Okay. Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

FHS and packaging (was: All caps .TH page title)

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),

[PATCH] NULL.3const: Add documentation for NULL

Reported-by: "G. Branden Robinson" Cc: Ralph Corderoy Cc: Ingo Schwarze Signed-off-by: Alejandro Colomar --- v2: - Move to man3const [Ralph, Branden] - Added LIBRARY section - Added #include [Ralph] - Note that it can also be used as a function pointer [Ralph] - Document that 0

[PATCH v3] NULL.3const: Add documentation for NULL

Reported-by: "G. Branden Robinson" Cc: Ralph Corderoy Cc: Ingo Schwarze Signed-off-by: Alejandro Colomar --- v2: - Move to man3const [Ralph, Branden] - Added LIBRARY section - Added #include [Ralph] - Note that it can also be used as a function pointer [Ralph] - Document that 0

Re: [PATCH v3] NULL.3const: Add documentation for NULL

Hi Ingo, On 7/25/22 20:49, Ingo Schwarze wrote: Hi Alejandro, Alejandro Colomar wrote on Sun, Jul 24, 2022 at 09:19:32PM +0200: - Move to man3const [Ralph, Branden] - Added LIBRARY section - Added #include [Ralph] - Note that it can also be used as a function pointer [Ralph] - Document that

Re: [PATCH v3] NULL.3const: Add documentation for NULL

Hi Jakub, On 7/25/22 20:57, Jakub Wilk wrote: * Alejandro Colomar , 2022-07-24, 21:19: +.B "#define NULL  ((void *) 0)" +.fi +.SH DESCRIPTION +.B NULL +represents a null pointer constant. +.PP +According to POSIX, +it shall expand to an integer constant expression with the value +.B

[PATCH v4] NULL.3const: Add documentation for NULL

Reported-by: "G. Branden Robinson" Cc: Ralph Corderoy Cc: Ingo Schwarze Cc: Jakub Wilk Signed-off-by: Alejandro Colomar --- v2: - Move to man3const [Ralph, Branden] - Added LIBRARY section - Added #include [Ralph] - Note that it can also be used as a function pointer [Ralph] - Doc

Re: [PATCH v4] NULL.3const: Add documentation for NULL

his difficulty, and will have one definition site only for their constants with external linkage. Oh, no. Check ssize_t(3type)! Cheers, Alex -- Alejandro Colomar <http://www.alejandro-colomar.es/> OpenPGP_signature Description: OpenPGP digital signature

<    1   2   3   4   5   6   7   >