Re: [PATCH v1 2/2] [troff]: Rewrite function in C.

On 2023-08-04 03:00, Alejandro Colomar wrote: > * src/roff/troff/env.cpp (is_family_valid): The old code was >eyeball-bleeding. This cuts 6 lines to 3, and each of them is >significantly simpler to read. Remove the comments of how it could >be improved using modern C++

Re: [PATCH v1 1/2] [troff]: Add lengthof() macro.

Hi Branden! On 2023-08-04 06:32, G. Branden Robinson wrote: > At 2023-08-04T03:00:10+0200, Alejandro Colomar wrote: >> * src/roff/troff/env.cpp (lengthof): Add macro to calculate the number >>of elements in an array. It's named after the proposal to ISO C, >>

Re: ⟨ vs < in hostname man page of hostname

Hi Jonny, On 2023-08-07 15:47, Jonny Grant wrote: > Hi Alejhandro > > Just looking at the COLOPHON > https://man7.org/linux/man-pages/man1/hostname.1.html ``` COLOPHON top This page is part of the net-tools (networking utilities) project. Information about the project can

Re: ⟨ vs < in hostname man page of hostname

Hi Jinny, On 2023-08-07 17:36, Jonny Grant wrote: >>> >>> Noticed that sometimes the '⟨' doesn't render, perhaps it is not in all >>> fonts, would it be possible to use consider using regular '<' and '>' >>> character in the man page? >> >> That is implemented using man(7)'s UR, which is for URI

Re: [PATCH v2] man*/: ffix (migrate to `MR`)

Hi Branden, Ingo, On 2023-08-01 16:12, G. Branden Robinson wrote: > At 2023-08-01T15:35:10+0200, Alejandro Colomar wrote: >> [CC += groff] >> >> Hi Jakub, Branden, >> >> On 2023-08-01 03:31, G. Branden Robinson wrote: >>> Hi Jakub, >>> >>

PDF book improvements

Hi Deri, My end goal is to be able to embed the creation of the PDF book in the Makefiles. To that end, as a first step, I'd like to reuse part of what we already have in the Makefile. Currently, we process all files with -Tpdf, which I guess we'll be able to reuse. $ make build-pdf -kij >

Re: PDF book improvements

On 2023-08-12 23:46, Alejandro Colomar wrote: > Hi Deri, > > My end goal is to be able to embed the creation of the PDF book in the > Makefiles. To that end, as a first step, I'd like to reuse part of > what we already have in the Makefile. Currently, we process all files &

Re: PDF book improvements

On 2023-08-12 23:46, Alejandro Colomar wrote: > Hi Deri, > > My end goal is to be able to embed the creation of the PDF book in the > Makefiles. To that end, as a first step, I'd like to reuse part of > what we already have in the Makefile. Currently, we process all files &

[linux-man book] Fonts from a library (was: PDF book improvements)

Hi Deri, Is there any chance we could use a font that is installed with the system (Debian would be good)? I'd also like to be able to remove the font from our source repository, if possible. Cheers, Alex -- GPG key fingerprint: A9348594CE31283A826FBDD8D5763

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

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

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

[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

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

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 >

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

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

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

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

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: [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: 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). > &

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

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

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

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

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

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

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: Plan 9 man added a new macro for man page references

rect practice, Version 7 Unix, is not as dispositive as it might be. Of the 641 cross-references I count in its corpus, only 345 (53.8%) set the page name in italics. The remainder simply use roman. The barbarism of setting the parenthetical section number in bold or italic

Re: Plan 9 man added a new macro for man page references

Hi, Branden! On 8/1/21 1:09 PM, G. Branden Robinson wrote: Hi, Alex! Welcome to the groff list! At 2021-07-31T16:54:43+0200, Alejandro Colomar (man-pages) wrote: Here's what I would have done differently or in addition. * Named the macro MR ("manual reference") to give it eve

Re: Plan 9 man added a new macro for man page references

quot; back (some of) those features back into man(7). Either we should move to use mdoc(7), or we don't at all. (And for the moment, I think I'll keep with the man(7) simpler macros.) What are your thoughts? Regards, Alex -- Alejandro Colomar Linux man-pages comaintaine

Re: Plan 9 man added a new macro for man page references

Hi, Ingo! On 8/3/21 4:30 PM, Ingo Schwarze wrote: Hello Alejandro, Alejandro Colomar (man-pages) wrote on Tue, Aug 03, 2021 at 09:29:14AM +0200: Thinking about it twice... Given mdoc(7) already implemented that, and that the basic difference between mdoc(7) and man(7) is basically that man

Re: Plan 9 man added a new macro for man page references

thing I'll ask, if I may: If you port it with the same exact features, could it come with the same exact name? Well, .BL to keep uppercase man(7) conventions. That would reduce brain load. :) Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: What is our ChangeLog management policy?

:51:56 +0200 (12 days ago) | getaddrinfo.3: Note that 'errno' is set in parallel with EAI_SYSTEM - Alejandro Colomar Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

.ad l/.ad b

.ad Begin line adjustment for output lines in current adjust mode. .ad c Start line adjustment in mode c (c=l,r,c,b,n). ] But what does each mode mean? I couldn't find anything about them in the manual page. Thanks, Alex -- Alejandro Colomar Li

.B, .I disable hyphenation?

hyphenation for .B and .I? Are there any inconveniences in doing so that I can't see? Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: AW: .ad l/.ad b

my impromptu Interpretation of 'n'. Thanks, then it seems that we don't need it (otherwise we would have been using it in all pages already). Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: .B, .I disable hyphenation?

Hi Branden, On 9/12/21 7:27 PM, G. Branden Robinson wrote: Hi, Alex! At 2021-09-12T14:56:39+0200, Alejandro Colomar (man-pages) wrote: Hi Branden, Usually, when a manual page highlights a term, either in bold or italics, it usually is a special identifier (macro, function, command name or

Re: We have OSC 8 terminal hyperlink support now

bout it at all? Regards, Branden [1] For example, I had to compile and install a more recent version of less(1) to test out my OSC 8 changes. Thus I wound up in the following situation. $ man -aw less /home/branden/share/man/man1/less.1 /usr/share/man/man1/less.1

Re: We have OSC 8 terminal hyperlink support now

Hi, Branden! On 10/2/21 7:45 PM, G. Branden Robinson wrote: Hi, Alex! At 2021-10-02T18:45:58+0200, Alejandro Colomar (man-pages) wrote: I was curious why man: and not man://, so I had a look at what uri(7) says about it. Curiously, it talks about man:. That's a good question and on

Re: We have OSC 8 terminal hyperlink support now

Hi, Brandem! On 10/6/21 2:53 PM, G. Branden Robinson wrote: Hi, Alex! At 2021-10-02T20:08:03+0200, Alejandro Colomar (man-pages) wrote: On 10/2/21 7:45 PM, G. Branden Robinson wrote: There is the question of what to do if a man page cross reference is ambiguous, Nothing, IMO. Even if the

Re: We have OSC 8 terminal hyperlink support now

On 10/6/21 3:57 PM, Alejandro Colomar (man-pages) wrote: function pdfman() { if (($# == 0)); then     >&2 echo "Usage: ${FUNCNAME[0]} [man options] [[section] page ...] ..."; Oops! Since it only supports a single page, it should be: >&2 echo &qu

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

Hi, Branden! On 10/18/21 7:34 AM, G. Branden Robinson wrote: Hi, Alex! At 2021-10-17T21:33:24+0200, Alejandro Colomar wrote: Break URIs before a single slash, not after. I found no GNU-specific (or any other at all) source that recommends breaking long URIs after a slash. So follow Chicago

Re: Two trivial questions

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

Re: SEE ALSO fails

m the dreaded Isla de Muerta. It's an island that cannot be found, except by those who already know where it is." -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

The 3-faces problem

roff. The weird thing is that WIDTH, even if it's in the same word as '_', it correctly ends up in bold. I'm using 1.22.4 (Debian Sid). Thanks! Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: The 3-faces problem

othing you can do short of modifying less. Ahh, it's less's fault then. Okay, I can live with that. I thought I was doing it wrong. Thanks! Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: The 3-faces problem

On 11/2/21 18:49, G. Branden Robinson wrote: Hi, Alex! At 2021-11-02T17:57:28+0100, Alejandro Colomar (man-pages) wrote: Hey Branden! I need your wisdom :) I hope to find some, someday... ;-) I'm facing the 3-faces problem right now. I'm trying to write the following senten

Re: The 3-faces problem

Hi, Branded! On 11/2/21 19:45, G. Branden Robinson wrote: Hi, Alex! At 2021-11-02T19:07:05+0100, Alejandro Colomar (man-pages) wrote: On 11/2/21 18:49, G. Branden Robinson wrote: printf '_\\fB_\\fI_\\f(BI_\n' | nroff | cat -s Yes, I see 4 different glyphs. Okay, so that much

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

Hi Branden, (D'oh! I used the wrong email address for all of these mails :-/) On 1/24/22 22:13, Alejandro Colomar wrote: > Hi Branden, > > And another html bug; however, this one seems to be a browser bug, but > please confirm. > > For the following code: > > [

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

On 1/25/22 01:29, G. Branden Robinson wrote: Hi, Alex! At 2022-01-24T21:48:51+0100, Alejandro Colomar wrote: I wrote a filter chess game a few days ago, and wrote some manual pages for it. When I decided to serve the manual pages online on my website, I found a few bugs, that I guess are

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

Hi Branden, On 1/25/22 01:58, G. Branden Robinson wrote: Hi Alex, At 2022-01-24T22:13:32+0100, Alejandro Colomar wrote: Hi Branden, And another html bug; however, this one seems to be a browser bug, but please confirm. Maybe not. For the following code: [ .TP .B \(aq\-\(aq Empty white

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

ent. Deri James has done stuff > like this before, so I know it's possible. It's just something I need > to learn, though my preference would be for someone to give me a fish > while I consider what sort of bait and tackle I'd like to have someday. > ;-) > > This

Re: groff_man_style(7): wfix needed

Hi Branden, On 1/25/22 03:12, G. Branden Robinson wrote: > Hi, Alex! > > At 2022-01-24T23:07:52+0100, Alejandro Colomar wrote: >> Hi, Branden! >> >> My brain returned EAMBIGUOUS for the following paragraph: >> >> [ >>\(aq Basi

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

Hi Branden, On 1/25/22 17:12, G. Branden Robinson wrote: > Hi, Alex, > > Quite bizarrely, I did not get this message in my inbox, nor even in my > spam folder. Thanks, GMail! :-| > > At 2022-01-24T22:32:13+0100, Alejandro Colomar wrote: >> Some wish. For the follow

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

is added, it should have a switch, and be disabled by default. Anyway, considering that it's likely to be a lot of work to implement, and only slightly useful, it would also be perfectly reasonable to discard this wish. Thanks, Alex -- Alejandro Colomar Linux man-pages comai

Re: preview of man(7) navigation/hyperlink features in groff 1.23

pages in PDF, I have written a few PDF documents using man(7), and for those, this feature is great. P.S.: I tried ms, as you recommended, but I'm not yet convinced by it. I'll still use man(7) for a while, I think. My only problem with man(7) is .TH, which I can't remove :/

CHECKSTYLE: Report problems with a non-zero status

ematic code, so I'll see some shy error on standard error once, but then if I run make(1) again, I'll believe that everything is OK. So, my suggestion is to return non-zero when -rCHECKSTYLE reports something. Does it make sense? Thanks, Alex -- Alejandro Colomar Linux man-p

CHECKSTYLE: Report consecutive .?P (paragraph macros)

would have no false positives, I think. Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: CHECKSTYLE: Report problems with a non-zero status

> cat > deadly.tmac > .am an-style-warn > . ab > > Does this help? It's up and running. Now I can try to learn all of those groff requests with time. It works perfectly, so please dismiss this bug report. I think this configurability is better than having a hardcoded defau

Re: CHECKSTYLE: Report consecutive .?P (paragraph macros)

tps://symas.com/the-sad-state-of-c-strings/ That one was quite interesting. strecpy() is s clean of a C string copy function! Thank you! Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: CHECKSTYLE: Report problems with a non-zero status

nderstand it. But I have time for that. I think I prefer the LANDMINE approach. That way I see a few bugs at once. I think it will be useful for reviewing man-pages(7) patches. I'm planning to add this to the man-pages(7) Makefile when I get it working on chessutils(7) and am happy with it. Regards, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: CHECKSTYLE: Report consecutive .?P (paragraph macros)

s-init.6 mandoc: share/man/man6/chess-init.6:10:2: ERROR: skipping unknown macro: .MR chess\-init 6 mandoc: share/man/man6/chess-init.6:12:2: WARNING: skipping paragraph macro: IP empty -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

mandoc warning: line scope broken: RE breaks TP (was Re: CHECKSTYLE: Report consecutive .?P (paragraph macros))

Hi Branden, Bjarni, On 2/2/22 01:32, Bjarni Ingi Gislason wrote: > On Mon, Jan 31, 2022 at 12:52:41AM +0100, Alejandro Colomar (man-pages) wrote: >> Hi Branden, >> >> Recently you reported to me a style error: >> >> [ >> .PP >> .TP >> tag >&g

mandoc warning: line scope broken: RE breaks TP (was Re: CHECKSTYLE: Report consecutive .?P (paragraph macros))

CC += mandoc On 2/2/22 03:19, Alejandro Colomar (man-pages) wrote: > Hi Branden, Bjarni, > > On 2/2/22 01:32, Bjarni Ingi Gislason wrote: >> On Mon, Jan 31, 2022 at 12:52:41AM +0100, Alejandro Colomar (man-pages) >> wrote: >>> Hi Branden, >>> >&g

style: .MR

them should be used. Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

[BUG] Hyperlink macros: breaking should conserve the full hyperlink

nd most importantly, isnt' part of the hyperlink. When I try to open the link, I'm directed to <https://www.kernel.org/doc/html/latest/process/>, which may be a non-existing URI, or may be a wrong URI. Tried with GNU groff version 1.23.0.rc1.1592-ae492. Cheers, Alex -- Aleja

groff_man_style.7: Hyperlink macros: \: before or after '#', '?'?

sting > style was consistent, but I'm not sure and it could have been wishful > reading on my part. :) Yup, groff(1) is quite consistent in that :) Cheers, Alex [1]: <https://lists.gnu.org/archive/html/groff/2021-10/msg00046.html> -- Alejandro Colomar Linux man-page

Ping: mandoc warning: line scope broken: RE breaks TP (was Re: CHECKSTYLE: Report consecutive .?P (paragraph macros))

Ping On 2/2/22 03:19, Alejandro Colomar (man-pages) wrote: > Hi Branden, Bjarni, > > On 2/2/22 01:32, Bjarni Ingi Gislason wrote: >> On Mon, Jan 31, 2022 at 12:52:41AM +0100, Alejandro Colomar (man-pages) >> wrote: >>> Hi Branden, >>> >&g

Re: style: .MR

s no manual page reference going on. From there, man(7) tradition seems to prescribe .B, and groff(1) style seems to prescribe .I... Cheers, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/

Re: groff_man_style.7: Hyperlink macros: \: before or after '#', '?'?

On 2/7/22 22:35, G. Branden Robinson wrote: > Hi, Alex! > > At 2022-02-07T19:46:43+0100, Alejandro Colomar (man-pages) wrote: >> Hi Branden, >> >> I see that groff_man_style(7) gives advice on where to break URIs >> regarding slashes and dots, but not '

Re: style: .MR

ntic tag classes" (my pie-in-the-sky idea > above), or bloating the macro name space for a something of limited and > specialized function, and the last is my least favorite by a long shot. > > If someone else has a better imagination, please speak up. > I think the solution in th

Re: [BUG] Hyperlink macros: breaking should conserve the full hyperlink

Hi Branden! On 2/7/22 22:53, G. Branden Robinson wrote: > Hi, Alex! > > At 2022-02-07T19:58:33+0100, Alejandro Colomar (man-pages) wrote: >> Hi Branden, >> >> I realized that when you break a hyperlink, the terminal shows an >> incorrect link. >> >> F

<    1   2   3   4   5   6   7   >