Proposed: change `pm` request argument semantics (was: process man(7) (or any other package of macros) without typesetting)

Hi Alex, At 2023-08-17T21:12:35+0200, Alejandro Colomar wrote: > I've had this desire for a long time, and maybe now I have a strong > reason to ask for it. [...] > The problem is that at no point you can have the .roff source, after > the man(7) macros have been expanded. Would it be possible to

Re: Proposed: change `pm` request argument semantics (was: process man(7) (or any other package of macros) without typesetting)

[self-follow-up] Fixing a footnote oops. Numbers corrected in quoted material. At 2023-08-17T18:44:14-0500, G. Branden Robinson wrote: [...] > I think we can. I've been mulling this for months, and now that I'm > on the threshold of implementing a `for` request as a string

mandoc(1) and diversions (was: Proposed: change `pm` request argument semantics)

At 2023-08-18T03:24:53+0200, Ingo Schwarze wrote: > > Understanding *roff a little better 6 years later, I can more easily > > imagine ways to run AT&T troff out of memory on a PDP-11. > > Ultra-long diversions would be one way,[1] > > [1] Nobody _except_ mandoc(1) seems to handle this well. Credi

Re: groff features for hyperlinked man pages (was: No 6.05/.01 pdf book available)

Hi Alex, At 2023-08-18T15:50:21+0200, Alejandro Colomar wrote: > On 2023-08-15 02:50, G. Branden Robinson wrote: > >>> I just re-read this, and am confused. '\-' is an ASCII character, > >>> isn't it? In fact, all of the Linux man-pages pathnam

Re: [PATCH] grotty(1): Don’t mention -T latin1 twice.

Hi Lennart, At 2023-08-19T19:33:10+, Lennart Jablonka wrote: > Fixes: 52f661f080f9 ("[man page]: Parallelize output driver intros.") > --- > src/devices/grotty/grotty.1.man | 1 - > 1 file changed, 1 deletion(-) Thanks! Applied and pushed. Also, since it's been a while since I've mentioned

Re: [PATCH] [grotty]: Use terminfo.

Hi Lennart, Thanks a lot for taking a stab at this! In lieu of a proper code review, I'll just riff on this to get the issues out before an audience. At 2023-08-19T20:08:06+, Lennart Jablonka wrote: > This has nothing at all to do with making it easier to customize the > look of man pages.

[bug #64577] [grops] can't embed/download fonts from a subdirectory

Follow-up Comment #10, bug #64577 (project groff): Thanks for correcting my addled advice regarding `-F` and $GROFF_FONT_PATH, Deri! ___ Reply to this item at:

[bug #64572] [man] UR, MT with no link text misrender on PDF when -rU1

to 1). diff --git a/ChangeLog b/ChangeLog index 00fe1c9aa..e1cc60ce8 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,12 @@ +2023-08-22 G. Branden Robinson + + * tmac/an.tmac: Stop setting `an*can-hyperlink` if formatting + for PDF; we don't yet have support for this implemented,

[bug #64576] [pdf.tmac] pdf*href option handling insufficiently flexible

Update of bug #64576 (project groff): Status: In Progress => None ___ Follow-up Comment #3: Not anticipated for my next push. ___ R

[bug #64575] [PATCH] doc/pic.ms: document .PY

Update of bug #64575 (project groff): Status:None => In Progress Assigned to:None => gbranden ___ Follow-up Comment #1: Hi Dave, [comment #0

[bug #64576] [pdf.tmac] pdf*href option handling insufficiently flexible

Follow-up Comment #5, bug #64576 (project groff): [comment #4 comment #4:] > Just completed a fix to allow any input to be used as a valid *roff identifier. This allows all UTF-8 to be used as well. So both "Known Issues" in my NewGropdf document are now ticked off. :-) Wow! Push, push! (As Her

[bug #64531] [ms] footnote continues emptily to next page

Update of bug #64531 (project groff): Status:None => Need Info Assigned to:None => gbranden ___ Follow-up Comment #1: I think this may be a

[bug #64529] [ms] confusing diagnostics when starting document with blank line or `KF` call

Update of bug #64529 (project groff): Status:None => Need Info Assigned to:None => gbranden Summary: [ms] anomalous diagnostic for initial keep => [ms] confusing diagnostics when st

[bug #64336] [mm] loses long floating display

t; 1.24.0 ___ Follow-up Comment #2: Pushed a few days ago. commit 3b615aa0fac692a8a24442a14726e71594c5f805 Author: G. Branden Robinson Date: Sat Aug 19 02:53:49 2023 -0500 [mm]: Fix Savannah #64336 (lost floats at end). * contrib/mm/m.tmac: Flush di

[bug #64582] [troff] idea: require end-of-input traps to explicitly exit

: None ___ Follow-up Comments: --- Date: Tue 22 Aug 2023 07:04:10 PM UTC By: G. Branden Robinson Spawned off of bug #64336. > [R]equire end-of-input traps (those planted with the `em` > request) to explicitly exit w

Re: '-' vs '\-' in TH (man(7))

Hi Alex, I have divided feelings about this issue. At 2023-08-20T21:10:52+0200, Alejandro Colomar wrote: > I just noticed that the Linux man-pages use '-' in TH. That's > surprising to me, as Michael was careful to use '\-' correctly. > > In the documentation, I couldn't find anything that says

Re: OSC8 hyperlink support in ncurses

Hi Thomas, At 2023-08-23T03:24:51-0400, Thomas Dickey wrote: > On Tue, Aug 22, 2023 at 01:12:04PM -0400, Dusty Mabe wrote: > > I'm wondering if anyone has ever requested OSC8 hyperlink support > > [1] in ncurses > > This is probably the first mention on this list. > > I don't see any use in my w

terminal escape sequences (was: [PATCH] [grotty]: Use terminfo.)

out regarding tmux,[1] it doesn't "do anything" with these escape sequences (except pass them through). Similarly, all grotty(1) does is produce them; it implements no code for reading or executing anything to do with OSC 8 escape sequence parameters. > G. Branden Robinson wrote on Su

bisecting with submodules: a pain

Hi Bertrand, I hope this message finds you well! Do you have any advice for going a Git bisection of the groff repo given that the gnulib submodule is present? I had occasional trouble with this before the 1.23.0 release but now it is much worse, and the disappearing "uniwidth.h" file breaks all

Re: OSC8 hyperlink support in ncurses

Hi Thomas, At 2023-08-23T15:25:24-0400, Thomas Dickey wrote: > On Wed, Aug 23, 2023 at 03:21:43AM -0500, G. Branden Robinson wrote: > > There was a humdinger of an argument about this on Egmont Koblinger's > > Gist about this feature. > > > > h

Re: Footer trap in a A4 PDF

Hi Matteo, At 2023-08-25T14:25:06+0200, Matteo Bini wrote: > I'm writing some documents that will be exported in PDF with A4 paper > size. I'm using my own macro package. [...] > This is how I output to PDF: > groff -K utf8 -m mymacro -M . -P -pa4 -T pdf in.roff > out.pdf > > I would expect the w

Re: Footer trap in a A4 PDF

Hi Matteo, At 2023-08-25T16:51:15+0200, Matteo Bini wrote: > Thanks for the answer Branden, > it's an honour to get a reply directly from you! It's an honor to have users who care enough to submit reports against a package, rather than casting it aside as unsatisfactory! > I've compiled your ROF

Re: Footer trap in a A4 PDF

At 2023-08-25T12:46:49-0400, Peter Schaffter wrote: > On Fri, Aug 25, 2023, G. Branden Robinson wrote: > > (Once upon a time, like 25 years ago, there was a tool called xruler or > > similar that made it easy to measure distances on the screen. > > Twenty-five years ago,

Re: Footer trap in a A4 PDF

Hi Matteo, At 2023-08-25T18:32:02+0200, Matteo Bini wrote: > On 2023-08-25 10:20, G. Branden Robinson wrote: > > Attaching screenshots of Evince viewing the document in "Dual" mode, > > when produced with Debian's groff 1.22.4 and stock groff 1.23.0 > > I ha

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

Hi Alex, I didn't forget about this. 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, >_Lengthof(), which wasn't accepted for C23, but hopefull

introduction to groff en español (was: About hyphenation)

Hi Walter, At 2023-08-26T12:42:06+0200, Walter Alejandro Iglesias wrote: > Recently I found some groff manual written in Spanish (standalone, not > a translation of the groff manual in English) I followed your link and found it here: https://cartaslinux.files.wordpress.com/2016/12/manual_groff.p

stale directory in CVS-managed WWW pages for groff project

Hi folks, There is a stale directory in the GNU groff project's website. https://www.gnu.org/software/groff/manual/html_node/ This corresponds to the groff 1.22.4 release, which is nearly 5 years old. The directory also shows up in ViewVC. https://web.cvs.savannah.gnu.org/viewvc/groff/groff/ma

Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project

Hi Alfred, At 2023-08-26T09:43:09-0400, Alfred M. Szmidt wrote: >There is a stale directory in the GNU groff project's website. > >https://www.gnu.org/software/groff/manual/html_node/ > >This corresponds to the groff 1.22.4 release, which is nearly 5 years >old. > >The direc

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

Hi Alex, At 2023-08-26T00:55:16+0200, Alejandro Colomar wrote: > The good news is that I like the implementation. I just don't like the > name. I have a sizeof_array() macro that does > > #define sizeof_array(a) (sizeof(a) + must_be_array(a)) > > That is, it calculates the size in bytes that

Re: Baffling accented glyphs issue

Hi Peter, At 2023-08-27T00:06:39-0400, Peter Schaffter wrote: > On Sat, Aug 26, 2023, Bjarni Ingi Gislason wrote: > > Lesson to learn: always use the information you have and give it to > > the program, for example "groff" with option "-K. > > > > groff -Kutf8 -V file > > > > preconv -eutf8 file

Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project

Hi Alfred, It looks like I need some coaching with CVS. It's been a long, long time since I used it daily. At 2023-08-26T14:15:55-0400, Alfred M. Szmidt wrote: >I asked my CVS checkout what the status of the former is. > >$ cvs status | grep html_node || echo NO RESULT >cvs status:

Re: [Savannah-hackers-public] stale directory in CVS-managed WWW pages for groff project

Hi Alfred, Success! At 2023-09-01T11:41:57-0400, Alfred M. Szmidt wrote: >$ cvsu [...] > Not a typo, it is part of the cvsutils package. Aha! Today I learned...(and "apt-got"). >$ cvs update -PAd > > Right, cvs update will try to add the files back. Did you do remove? > You also need

Re: [PATCH v2] [grotty]: Use terminfo.

At 2023-08-30T20:54:09+, Lennart Jablonka wrote: > > Subject: [PATCH v2] [grotty]: Use terminfo. > > Branden: ENQ Indeed! At 2023-08-21T21:40:18+, Lennart Jablonka wrote: > This has nothing at all to do with making it easier to customize the > look of man pages. > > Hyperlinks are still

Re: [PATCH v2] [grotty]: Use terminfo.

[self-follow-up] At 2023-09-01T12:47:58-0500, G. Branden Robinson wrote: > > + if (curr_back_idx != back_idx) { > > +putp(tparm(set_a_background, back_idx, 0, 0, 0, 0, 0, 0, 0, 0)); > > +curr_back_idx = back_idx; > > What were people thinking? It's SO

Re: [PATCH v2] [grotty]: Use terminfo.

At 2023-09-01T12:47:58-0500, G. Branden Robinson wrote: > I'm happy with this and will start merging. Any tweaks I make will be > in a subsequent commit, unless merging it as-is breaks the > build/tests, in which case I'll let you know. I

Re: [PATCH v2] [grotty]: Use terminfo.

ms to be the only failing case, and it is catching a real problem, from what I can see. At 2023-09-01T22:03:54+, Lennart Jablonka wrote: > Quoth G. Branden Robinson: > > At 2023-08-21T21:40:18+, Lennart Jablonka wrote: > > > This has nothing at all to do with making it easier

Re: Leaders

Hi Peter, I get the same output you do from your second example. I do observe that `\a` in interpretation mode doesn't get warned about, even with '-ww'. That may be a defect. At 2023-09-02T16:19:08-0400, Peter Schaffter wrote: > Question 1: > Is \a only interpreted in copy mode as this would s

Re: Leaders

[self-follow-up] Hi Peter, On second thought--in the form of empirical measurements rather than hand-waving conjecture--I think you've found a bug. Consider the following input, which I've degraded to an ASCII spelling of "chateau" to permit some comparative analysis (keep reading). $ cat long-

Re: Leaders

Hi Lennart, At 2023-09-02T22:35:25+, Lennart Jablonka wrote: > No, there aren’t. Your message does not contain the SOH bytes; you > could as well put replacement “^A”s there. I was attempting to suggest their presence. > The point is that the width of the line of periods is determined by

Re: Leaders

At 2023-09-03T23:43:29+, Lennart Jablonka wrote: > What I intended to express is an explanation for how it could come to > be that tabs and leaders behave in that way: It was possible because > quite seldom someone wanted a tab or leader in filled text. Because > long headings in a TOC are r

Re: 1.23 prints some strange error

Hi Walter, At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote: > On Mon, Sep 11, 2023 at 07:18:59PM +0200, Walter Alejandro Iglesias wrote: > > I normally use OpenBSD in my desktop, which still comes with groff > > 1.22.4. Today I booted an old laptop with Debian testing (Devuan to > >

Re: [groff] 05/16: doc/meref.me.in: Update and revise.

Hi Dave, At 2023-09-11T19:43:48-0500, Dave Kemper wrote: > I have comments on two of the numerous changes of this commit. > > > this material can then be resequenced > > +by the > > +.b pdfswitchtopage > > +macro (for PDF output), > > by a tool that processes the output format, > > or physical

Re: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition

Hi Larry, At 2023-09-19T16:39:25-0700, Larry McVoy wrote: > One of the projects I thought I'd do in my retirement, but haven't > done, was to provide man page / paper as in "a paper", not tree paper, > versions of all the GNU info stuff. I could not be less thrilled with > info, yeah there are wa

Re: Special characters

Hi Merijn, At 2023-09-22T08:43:37+0200, H.Merijn Brand via wrote: > On Thu, 21 Sep 2023 18:51:42 +, Lennart Jablonka wrote: > > > [groff 1.23] renders all manual pages useless > > > > If you aren’t careful, you could evoke the impression your hyperbole > > is to be taken literally. > > :)

Re: [PATCH v3] [grotty]: Use terminfo.

Hi Lennart, At 2023-09-21T19:00:44+, Lennart Jablonka wrote: > > Date: Tue, 5 Sep 2023 02:09:29 + > > Subject: [PATCH v3] [grotty]: Use terminfo. > > ENQ ACK. I've gotten a bit sidetracked learning more about terminfo and ncurses...and a dreaded, predictable thing happened. I found the

Re: Special characters

At 2023-09-22T10:56:06+0200, H.Merijn Brand wrote: > Shorted reply. Might expand on this later No worries. I acknowledge that my emails sometimes resemble homework assignments. > I realized when I re-read that this morning and apologized in my reply > I'll apologize again if that was not clear

Re: custom NS and NE man(7) macros

[looping in groff list; find start of thread at <https://lists.gnu.org/archive/html/bug-ncurses/2023-09/msg00076.html>.] At 2023-09-24T19:45:22-0400, Thomas Dickey wrote: > On Sun, Sep 24, 2023 at 03:12:47PM -0500, G. Branden Robinson wrote: > > I see the following macro definit

Re: custom NS and NE man(7) macros

At 2023-09-25T06:08:18-0500, Dave Kemper wrote: > On 9/25/23, G. Branden Robinson wrote: > > If my reading of groff release history is correct,[1] groff 1.19 > > came out in February 2004 > > The release of groff 1.19 was announced in Apr 2003 > (http://lists.gnu.org/

Re: custom NS and NE man(7) macros

Hi Doug, You didn't say, but I reckon this is a survey of man(7) macros that might be considered extensions? At 2023-09-25T19:26:13-0400, Douglas McIlroy wrote: > Used in connection with man(7): > PS/PE That one's pretty rare. It may be that most page authors are too lazy to write fallb

Re: custom NS and NE man(7) macros

[It looks like Doug hybridized our thread over to TUHS again. :D Forwarding my reply thence back to the groff list.] Hi Doug, At 2023-09-26T09:38:07-0400, Douglas McIlroy wrote: > > You didn't say, but I reckon this is a survey of man(7) macros that > > might be considered extensions? > > My pr

Re: [htmlxref.cnf] Please update link to the Groff manual

Hi Gavin & Thérèse, At 2023-09-30T16:22:32+0100, Gavin Smith wrote: > On Sat, Sep 23, 2023 at 12:44:31PM +0200, Thérèse Godefroy wrote: > > Hello Gavin, > > > > The new URL of the node version is > > https://gnu.org/s/groff/manual/groff.html.node/ > > And there is a mono version. > > > > A patch

Re: [htmlxref.cnf] Please update link to the Groff manual

Hi Ingo, At 2023-09-30T22:07:44+0200, Ingo Schwarze wrote: > Now that i see this bumpy ride explained at length, i realize the > link on this overview page of mine is currently broken, too: > > https://mandoc.bsd.lv/links.html > > First paragraph, first line, second link ("manual"). > Rather p

Re: [htmlxref.cnf] Please update link to the Groff manual

[self-follow-up] At 2023-09-30T15:59:13-0500, G. Branden Robinson wrote: > I concede that having a working "/html_node/" URL by hook or by crook > (or by symlink) is probably a good idea given the list of URLs linking > to it that you presented above. I find I have a problem

Re: XREF in man(7)

Hi Alex, At 2023-10-03T20:22:17+0200, Alejandro Colomar wrote: > On Tue, Oct 03, 2023 at 08:16:00PM +0200, Alejandro Colomar wrote: > > Hi Branden, > > > > I've imported some archaic pages. Those pages used some ".XREF" > > after the TH and before SH NAME. They seem to be a duplication of > > t

Re: [htmlxref.cnf] Please update link to the Groff manual

Hi Gavin, Ingo, Dave, and Thérèse, Thanks to all of you for your feedback, patience, and advice. At 2023-09-30T20:10:01+0100, Gavin Smith wrote: > On Sat, Sep 30, 2023 at 01:15:09PM -0500, G. Branden Robinson wrote: > > As for why I chose the name I did, that was simply an

Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP

Hi Alex, At 2023-10-23T12:47:21+0200, Alejandro Colomar wrote: > On Mon, Oct 23, 2023 at 04:15:23AM -0500, G. Branden Robinson wrote: > [Added groff@, to have some mailing list] Ah, okay, well, in so doing you have exposed some brain farts of mine to the world. But I have no doubt tha

Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP

Hi Ingo, At 2023-10-24T02:13:34+0200, Ingo Schwarze wrote: > 5. On top of all that, i have a hard time to think of any macro > that has a more wicked failure mode than .TQ in case the > formatter does not support it. The output visually looks > perfectly fine, and the reader gets no

Re: [htmlxref.cnf] Please update link to the Groff manual

At 2023-10-14T18:04:47+0200, Thérèse Godefroy wrote: > I added a RedirectMatch directive similar to the one above to the > site-wide .htaccess. Now the html_node URLs work. Thanks, Thérèse. I'm afraid I may need still more help. I'm trying to .htaccess some spot fixes for known stale URLs on the

Re: 1.23 prints some strange error

Hi Walter & Dave, At 2023-09-11T19:45:30+0200, Walter Alejandro Iglesias wrote: > If instead of sourcing hyphen.tr from my macros with .mso I source it > directly from the roff document with .so those error messages > desapear. As Dave mentioned, this is explained by soelim(1) not being run on th

Re: 1.23 prints some strange error

Hi Walter, At 2023-10-25T14:25:42+0200, Walter Alejandro Iglesias wrote: > > This transcript isn't as useful as it could be, because it didn't > > disclose to me what character encoding was used for list.tr on the > > file system. Running the file(1) command on it and sharing that > > would help.

`\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix)

Hi Alex, At 2023-10-25T21:38:59+0200, Alejandro Colomar wrote: > On Wed, Oct 25, 2023 at 01:54:24PM -0500, G. Branden Robinson wrote: > > diff --git a/man2/open.2 b/man2/open.2 > > index 4c921723c..6603dfdff 100644 > > --- a/man2/open.2 > > +++ b/man2/open.2 > > @

Re: 1.23 prints some strange error

At 2023-10-25T16:20:27+0200, Walter Alejandro Iglesias wrote: > What you did above is not the step by step way I posted to reproduce > the bug. Of course it won't be helpful if you overlook it. You've already gotten what I would have thought to be a sufficient explanation of the diagnostic messag

Why does man(7) have 3 paragraph macros for the same thing? (was: `\c`, mdoc(7), and man(7) extension macros)

At 2023-10-26T16:12:36+0200, Alejandro Colomar wrote: > Regarding PP, LP, and P, what's the history of them? Why do we have > the 3? I'm willing to reduce them to just one. I invite Doug McIlroy to go on record, but my surmise is that they were introduced as crutches for people already familiar

Re: Why does man(7) have 3 paragraph macros for the same thing? (was: `\c`, mdoc(7), and man(7) extension macros)

At 2023-10-26T16:58:13+0200, Alejandro Colomar wrote: > On Thu, Oct 26, 2023 at 09:51:40AM -0500, G. Branden Robinson wrote: > > At 2023-10-26T16:12:36+0200, Alejandro Colomar wrote: > > > Regarding PP, LP, and P, what's the history of them? Why do we > > > have th

Re: 1.23 prints some strange error

Hi Walter, At 2023-10-26T17:21:21+0200, Walter Alejandro Iglesias wrote: > Ah, now I understand where's the problem, as it happens to me, groff > 1.22.4 also ingores what you're explaining. For me, the output doesn't change, but groff 1.22.4 doesn't emit a diagnostic. But that's not a surprise.

Re: Why does man(7) have 3 paragraph macros for the same thing? (was: `\c`, mdoc(7), and man(7) extension macros)

[self-correcting follow-up] At 2023-10-26T09:51:42-0500, G. Branden Robinson wrote: > In ms(7), `LP` sets a paragraph that is left-aligned, and `PP` sets > one with a first-line indentation. > > In man(7), all (ordinary) paragraphs behave analogously to ms(7)'s > `PP`. A fi

Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP

At 2023-10-24T12:31:04+0200, Alejandro Colomar wrote: > In less(1) I use similar heuristics to find what I want: '/--unused' > will get me exactly where I expect. You might want to adapt this habit to '/ +--unused'. (1) It's less to type and (2) in groff 1.24.0, the base paragraph inset will

Re: `\c`, mdoc(7), and man(7) extension macros (was: [PATCH 1/2] man*/: srcfix)

Hi Alex, At 2023-10-26T16:12:36+0200, Alejandro Colomar wrote: > Yup. I have similar feelings about C++, BTW. I have a hard time > understanding complex languages. I prefer simpler languages. Most > features can be implemented as library code, without complicating the > language. Just know th

Re: About verbatim dashes in PostScript output

Hi Jan, At 2023-10-28T15:18:05+0200, Jan Engelhardt wrote: > A recent LWN.net article (paywalled > for a while) For the benefit of those reading this in the future, the article should be free to read starting about 2 November 2023. > pointed at https://bugs.de

Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP

Hi Alex, At 2023-10-28T17:55:50+0200, Alejandro Colomar wrote: > On Sat, Oct 28, 2023 at 07:27:49AM -0500, G. Branden Robinson wrote: > > At 2023-10-24T12:31:04+0200, Alejandro Colomar wrote: > > > In less(1) I use similar heuristics to find what I want: > > > '/

Re: mandoc -man -Thtml bug: inconsistent vertical space before .TP

Hi Ingo, Fair warning: this message is (even) more opinionated than usual. At 2023-10-26T18:37:58+0200, Ingo Schwarze wrote: > G. Branden Robinson wrote on Tue, Oct 24, 2023 at 04:54:21AM -0500: > > I haven't explicitly made the connection to HTML before, > > Well, when desi

Reminder of bleeding-egde groff resource

Hi folks, I hadn't mentioned it in a while so I wanted to advise people of the availability of 20 PDF documents I keep up to date with groff's development in Git. For those who don't want to mess with fetching and building groff from source, and/or don't subscribe to (or have trouble following th

Re: Merging the new gropdf

Hi Deri, At 2023-11-07T17:33:06+, Deri wrote: > On Monday, 6 November 2023 17:47:13 GMT G. Branden Robinson wrote: > > Slowly. I landed two small changes this weekend, but they're not > > things most folks are looking for. > > Thanks for this. Hoping to do m

Re: Support regarding input of unicode chars

Hi Gustavo, At 2023-11-08T07:29:49+, Gustavo Calvo wrote: > Hi! Is there a way to use character U+2112 in my document? So far I > have tried `\[u2112]`, which does seem to work for characters like > `\[u0394]` that are listed in the groff_char manual. Sure. There are a couple of approaches.

Re: -ms regression

t into a confused state. What do you think? If I am not persuasive, please consider sharing the document source, or at least the initial part of it, with me and I'll see what happens when I crash my mental model of The Right Way(tm) up against the work of your practiced hand. Regards

Re: .Li in mdoc(7), was: `\c`, mdoc(7), and man(7) extension macros

At 2023-11-09T19:31:39-0500, James K. Lowden wrote: > (I don't like "Sy =", for logical and asthetic reasons. Logically, > it's not a "symbol", in that it doesn't stand for anything but itself. (Careful now, or the shambling zombie of Jacques Derrida is going to kick down the door and subject us

Re: your mail

Hi Doug, At 2023-11-11T07:31:31-0500, Douglas McIlroy wrote: > >> This diagnostic in -ms 1.23.0 breaks a document that works with 1.22.4: > >> > >> error: .AB is not allowed after first .AB, .LP, .PP, .IP, .SH or > >> .NH > >> > >> This dictum is unreasonably prescriptive. The "error" is

Re: Regarding groff, soelim, and macros

Hi Riza, At 2023-11-14T06:59:54+0300, Riza Dindir wrote: > I am having trouble again with macros, soelim. > > I am writing a document that will have pic's and equation's in it. I > wanted to separate these into files. One file for each chapter. That sounds reasonable. > But I am having trouble

Re: -man fails to use ANSI commands

Hi Anton, At 2023-11-19T14:53:24+0300, Anton Shepelev wrote: > `groff -man -Tutf8' does not seem to handle font > styles on my terminal. I have made sure that plain > `groff' works as expected: > > This is > .ft B > strange >

Re: building groff 1.23.0 on z/OS

[shifting discussion to main groff list] Hi Mike, At 2023-11-18T17:35:26-0800, Mike Fulton wrote: > I have hit a problem trying to build the latest groff. > I am able to successfully build 1.22.4 > > The issue I am hitting is that there is a `#include ` before > the `config.h` file is included.

Re: Why does groff require psutils?

Hi Lukas, At 2023-11-19T17:31:40+0100, Lukas Javorsky wrote: > I've been approached by a maintainer of the `psutils` package that the > groff is the only package that still requires it. He wants to get rid > of the package as many of the dependencies have shifted from it, but > the groff is still

Re: -man fails to use ANSI commands

Hi Anton, At 2023-11-20T00:20:46+0300, Anton Shepelev wrote: > `export | grep -i sgr' finds nothing, unfortunately. Where > else can I look for the reason of -man treating my virtual > terminal as a printer? Once I find it, I will bring it up > with the administrator of that system, and then per

Re: -man fails to use ANSI commands

Hi Anton, At 2023-11-20T18:38:19+0300, Anton Shepelev wrote: > G. Branden Robinson to Anton Shepelev: > > If you're still using groff 1.22.4, some distribu- > > tions used a device control command to tell > > grotty(1) to shut off SGR support. > > Indee

Re: Instructions for minimal documents

Hi Oliver, At 2023-11-21T13:37:13+0100, Oliver Corff via wrote: > while experimenting with the mm macro package for the first time I > noticed that from the very start it did not behave exactly as expected > --- which was entirely due to my lacking of understanding of some > basics. Before diggin

Re: -man fails to use ANSI commands

Hi Anton, At 2023-11-21T11:36:09+0300, Anton Shepelev wrote: > G. Branden Robinson to Anton Shepelev: > >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312935 [...] > > The more I learned, the more I realized just how > > wrong that guy was. > > I have

Re: bad line counts from eqn 1.23.0

Hi Doug, At 2023-11-21T15:06:45-0500, Douglas McIlroy wrote: > eqn issues a .lf for every .EN. In 1.23.0 the line number is assigned > as if there were only one line of eqn text between .EQ and .EN, > regardless of how many lines actually are present. Thus the two > fragments below yield identical

Re: GNU groff in articles

At 2023-11-21T12:02:20+0300, Anton Shepelev wrote: > Jim Hall: > > > Several weeks ago, I interviewed Dr. Marshall Kirk > > McKusick about how he writes his books using groff: > > https://technicallywewrite.com/2023/10/13/groffbooks > > McKusick writes about orphan elimination, end-of- > line

Re: Instructions for minimal documents

Hi Oliver, At 2023-11-21T15:06:37+0100, Oliver Corff via wrote: > Dear Branden, > > you got me immediately on this one. Please accept my sincerest > apologies, the production environment here still is based on 1.22.4. No apologies necessary; as a Debian user since the 1990s I know how long it ca

Re: Using the mm package, how to display journal title and author affiliations?

Hi Oliver, At 2023-11-21T18:56:51+0100, Oliver Corff wrote: > the first steps with mm look quite promising, and the (optional) goal > of approaching the typesetting appearance of the original in the > translation (for the benefit of the reader who wants to consult the > original) is definitely ach

Re: A weird problem with mm title page macros

Hi Oliver, At 2023-11-21T19:49:09+0100, Oliver Corff wrote: > I tried to play with 4.MT by copying and renaming it as 6.MT and > calling .MT 6, but then the result is as if I had no .MT call at all. > Strange. As weird as it seems, that's documented. MT [type [addressee]] Selec

Re: A weird problem with mm title page macros

Hi Oliver, At 2023-11-21T22:58:45+0100, Oliver Corff via wrote: > I get *your* point, but I was lured to believe that I could write my > own Memorandum Type by copying an existing one in the ../tmac/mm/ > directory and assigning an appropriate number. I thought "types 0 to 5 > are supported" can b

Re: Why does groff require psutils?

At 2023-11-26T15:34:10+0100, Ingo Schwarze wrote: > not related to the "psutils" questions, but this almost made my > eyes fall out. Evidently... > Alexis wrote on Sun, Nov 26, 2023 at 12:28:25PM +0100: > > > Would replacing the following in src/preproc/html/pre-html.cpp > > s = make_string("p

Re: using pic with -Thtml

At 2023-11-29T19:11:27+0100, hbezemer--- via wrote: > Thanks Dave, that makes it clear for me. > > I've tried my first minimal example. but now with -ms and this gives a > good result. Thus: echo ".PS\nbox\n.PE" | pic | groff -Thtml -ms > works. > > Would it be useful to modify the -mm PS and PE

Re: Groff hdtbl tables disappear near the footer

[Mike CCed just to be sure he gets this] Hi Mike, At 2023-12-04T18:43:15+, Mike wrote: > I am new to groff. I am more a designer than a coder, so my > understanding here may be lacking. No worries. This list is definitely not just for programmers. > I created a CV template using groff + ms

Re: Help with citations in groff

At 2023-12-04T17:50:46-0600, Dave Kemper wrote: > On 12/1/23, Darris Hawks wrote: > > There are a couple of things that are unclear to me after reading > > the manual for GNU refer. [...] > Can you clarify what documentation you were reading--and, if it was > the refer(1) man page, which version o

Proposed GNU troff behavior change: require end-of-input macros to exit

Hi folks, I have a *roff language reform to suggest. I propose that GNU troff stop behaving like AT&T troff in one aspect of end-of-input macro processing, documented in our Texinfo manual. -- Request: .em macro Set a trap at the end of input. MACRO is executed after the last line of

Re: Proposed GNU troff behavior change: require end-of-input macros to exit

[self-follow-up] Some clarifications, to our Texinfo manual and to my own remarks... At 2023-12-08T15:34:28-0600, G. Branden Robinson wrote: > The '\c' in the above example needs explanation. For historical > reasons (and for compatibility with AT&T &#x

Re: Updating eqn

At 2023-12-08T14:00:30+1100, Damian McGuckin wrote: > > (And one of these days I'd like to support cube roots and subscripts > > and superscripts on the left side of symbols. I'd like to bring > > eqn's capabilities closer to those of TeX. I hate typing in all > > those backslashes.) > > You just

Re: sys-apps/groff-1.23.0: explicitly disable compatibility wrappers

Hi Fabian, I saw the following in a commit[1] of yours. "On Prefix systems, compatibility wrappers are generated because the default action is "auto". These wrappers, however, do not function well on certain systems (Illumnos for instance), but from tests it appears they are not necessary either

Re: sys-apps/groff-1.23.0: explicitly disable compatibility wrappers

Hi Fabian, At 2023-12-09T19:25:19+0100, Fabian Groffen wrote: > On Illumnos, with 1.23.0 default configure, if I do this: > > % bzcat /gentoo/prefix64/usr/share/man/man3p/snprintf.3p.bz2 | ( cd > /gentoo/prefix64/usr/share/man && /gentoo/prefix64/usr/libexec/man-db/zsoelim > ) | ( cd /gentoo/pr

  1   2   3   4   5   6   7   8   9   10   >