Re: Proposed: stop subjecting right-hand sides of `char` family requests to character translation

Hi Doug, At 2023-04-02T13:40:41-0400, Douglas McIlroy wrote: > My mistake. I found the word "entity" in groff.7, not groff_char.7. I've pushed some documentation revisions to master that eliminate use of the term "entity" when discussing groff's input language. I had found it confusing, too.

[groff] 01/01: ANNOUNCE: Reflect Savannah #64091 fix.

gbranden pushed a commit to branch master in repository groff. commit 3aa8c89371c9b67585c2fc3432ddef260b7755c6 Author: G. Branden Robinson AuthorDate: Tue Apr 25 00:16:47 2023 -0500 ANNOUNCE: Reflect Savannah #64091 fix. --- ANNOUNCE | 6 +++--- 1 file changed, 3 insertions(+), 3

[bug #64091] doc/groff.texi: consider clarifying text about sentence spacing

Update of bug #64091 (project groff): Status: Need Info => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

[groff] 06/06: [docs]: Reduce use of term "entity".

gbranden pushed a commit to branch master in repository groff. commit 0223aef4164a7b07cb933a397894878bb61773b5 Author: G. Branden Robinson AuthorDate: Mon Apr 24 19:58:08 2023 -0500 [docs]: Reduce use of term "entity". Doug McIlroy noted this vague term, which groff employs for

[groff] 02/06: [docs]: Further clarify end-of-sentence detection.

gbranden pushed a commit to branch master in repository groff. commit 3778beb2e00f28262c02de2bea7db5915c734c2b Author: G. Branden Robinson AuthorDate: Sun Apr 23 20:15:12 2023 -0500 [docs]: Further clarify end-of-sentence detection. (One hopes.) * doc/groff.texi

[groff] 05/06: doc/groff.texi: Use idiomatic Texinfo notation.

gbranden pushed a commit to branch master in repository groff. commit bd22b5bd0d26d0e3191f25a291960c4595dc873b Author: G. Branden Robinson AuthorDate: Mon Apr 24 19:30:15 2023 -0500 doc/groff.texi: Use idiomatic Texinfo notation. Use "@code{\@key{RET}}" and "@code{\@key{SP}}"

[groff] 03/06: [docs]: Tweak escape/control character discussion.

gbranden pushed a commit to branch master in repository groff. commit 05b804f05583e8675e9c5df812c3ca0f89721cb7 Author: G. Branden Robinson AuthorDate: Mon Apr 24 07:50:18 2023 -0500 [docs]: Tweak escape/control character discussion. * Introduce term "ordinary character", an input

[groff] 04/06: doc/groff.texi: Drop old cautionary note.

gbranden pushed a commit to branch master in repository groff. commit a9eeeab065a209f615cccba4e9ca9b427eb6ba0d Author: G. Branden Robinson AuthorDate: Mon Apr 24 08:59:36 2023 -0500 doc/groff.texi: Drop old cautionary note. This material dates to commit 21260e1cd2, 7 June 2002.

[groff] 01/06: PROBLEMS: Update expected diagnostic text.

gbranden pushed a commit to branch master in repository groff. commit dbd2b2007280f5125227307ff6962c0948366aef Author: G. Branden Robinson AuthorDate: Mon Apr 24 17:27:17 2023 -0500 PROBLEMS: Update expected diagnostic text. Thanks to Dave Kemper for catching this. --- PROBLEMS |

[bug #64105] [eqn] off-by-one error in line numbering

URL: Summary: [eqn] off-by-one error in line numbering Group: GNU roff Submitter: gbranden Submitted: Tue 25 Apr 2023 02:14:24 AM UTC Category: Preprocessor eqn

Re: [mom] Extraneous empty line that starts a new page

Hi, Branden. On Mon, Apr 24, 2023, G. Branden Robinson wrote: > > Regardless, when I process the document with groff 1.23.0.rc1.3711-25fb > > and mom-2.5_c, passing pdfmom the -b flag (but not the -w flag), I > > receive a string of errors of the form > > > > troff: backtrace:

Re: [mom] Extraneous empty line that starts a new page

Frederick -- On Mon, Apr 24, 2023, Frederic Chartier wrote: > I'm running groff 1.22.3, by the way. It's been patched but not > since 2016 so if it's bugs I'm seeing, they're not new. Can you check whether you're using the latest version of mom (2.5_c)? If not, you can get it at

Re: groff-1.23.0.rc4 - no ./configure?

At 2023-04-25T01:35:03+0200, Alejandro Colomar wrote: > > Curious way to put it. I wondered something along those lines > > recently: Is it possible to teach cgit how to create a tarball? It > > would be nice if I just made a tag and cgit would do the automated > > process necessary for the

Re: groff-1.23.0.rc4 - no ./configure?

On 4/25/23 00:25, Alejandro Colomar wrote: > [CC += CGit] > > Hi Branden! > > On 4/25/23 00:14, G. Branden Robinson wrote: >> Hi Oliver, >> >> At 2023-04-24T22:40:23+0200, Oliver Corff wrote: >>> I went to https://git.savannah.gnu.org/cgit/groff.git today to >>> download the rc4 tarball

Re: [mom] Extraneous empty line that starts a new page

[self-clarification] At 2023-04-24T18:13:09-0500, G. Branden Robinson wrote: > Space management around tables is the responsibility of each macro > package. The job of tbl(1) itself is to render the table. There was > a bug in the past several versions of groff in this area, but it > involved

Re: [mom] Extraneous empty line that starts a new page

Hi Frederic, At 2023-04-24T21:56:58+0200, Frederic Chartier wrote: > Here's another tbl-related problem I've encountered, in case the two > are connected. Groff acts as if every table were preceded by an empty > paragraph. This is why there is so much vertical space between the > headings and the

Re: [mom] Extraneous empty line that starts a new page

Hi Peter, Thanks for riding to my support-department rescue. :) At 2023-04-24T14:55:00-0400, Peter Schaffter wrote: > > Something's gone badly wrong, and I'm not sure what. > > Indeed. > > > Possibly the document's state is invalid (mom(7) is not > > implemented sloppily). > > The document

Re: groff 1.23.0.rc4 available for testing

At 2023-04-24T11:18:32-0500, Dave Kemper wrote: [...] > PROBLEMS shows example warnings worded this way: > > troff:man/groff_char.7:1000: warning: can't find special character '.j' > > My build generated warnings worded like this: > > troff: backtrace: file 'man/groff_char.7':1033 >

Re: groff-1.23.0.rc4 - no ./configure?

[CC += CGit] Hi Branden! On 4/25/23 00:14, G. Branden Robinson wrote: > Hi Oliver, > > At 2023-04-24T22:40:23+0200, Oliver Corff wrote: >> I went to https://git.savannah.gnu.org/cgit/groff.git today to >> download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the >> archive. > > I've

Re: groff injects blank page

Hi Carlos, At 2023-04-24T11:17:08-0400, Carlos wrote: > On Mon, Apr 24, 2023 at 12:44:38AM -0500, G. Branden Robinson wrote: > > The `cR` register is documented in groff_man(7). The `ps4html` > > register is...not documented. :-| > > Thank you for advising me against this > > And by the looks

Re: groff-1.23.0.rc4 - no ./configure?

Hi Oliver, At 2023-04-24T22:40:23+0200, Oliver Corff wrote: > I went to https://git.savannah.gnu.org/cgit/groff.git today to > download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the > archive. I've made the same mistake myself! The official distribution archives are not available via

Re: groff-1.23.0.rc4 - no ./configure?

On Mon, Apr 24, 2023 at 10:40:23PM +0200, Oliver Corff wrote: > Dear all, > > I went to https://git.savannah.gnu.org/cgit/groff.git today to download > the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the archive. > > How do I configure the makefile? I fail to see a ./configure script. > >

groff-1.23.0.rc4 - no ./configure?

Dear all, I went to https://git.savannah.gnu.org/cgit/groff.git today to download the rc4 tarball groff-1.23.0.rc4.tar.gz and unpacked the archive. How do I configure the makefile? I fail to see a ./configure script. Thank you, Best regards, Oliver. -- Dr. Oliver Corff Mail:

Re: [mom] Extraneous empty line that starts a new page

On 2023-04-24 14:55 -0400, Peter Schaffter wrote: > I've never seen this behaviour before. It's been a while since I > needed tbl(1) in a mom document so I'm thinking it crept in during > one of the past year's bazillion commits. Most likely something to > do with tbl(1) or with gropdf(1). At

Re: [mom] Extraneous empty line that starts a new page

Sorry for top-quoting Branden's reply _in toto_ but it will make replying easier. On Sun, Apr 23, 2023, G. Branden Robinson wrote: > Hi Frederic, > > At 2023-04-24T01:37:00+0200, Frederic Chartier wrote: > > I've stumbled on another problem with -mom. There is a table at > > the bottom of a

Re: mdoc(7): CHECKSTYLE

Hi Branden, On 4/24/23 07:31, G. Branden Robinson wrote: Hi Alex, At 2023-04-23T16:17:06+0200, Alejandro Colomar wrote: I got some errors from mdoc(7), which were probably due to the LANDMINE .

Re: groff 1.23.0.rc4 available for testing

I encountered only one tiny issue: PROBLEMS has an item titled "I get warnings about special characters in the groff_char(7) man page" that includes sample warnings that don't match the warnings troff currently generates. I noticed this because when the build threw those warnings, the first thing

Re: groff injects blank page

On Mon, Apr 24, 2023 at 12:44:38AM -0500, G. Branden Robinson wrote: > Hi Carlos, > > At 2023-04-23T11:38:39-0400, Carlos wrote: > > On Sat, Apr 22, 2023 at 04:33:52PM -0500, G. Branden Robinson wrote: > > > At 2023-04-22T16:46:00-0400, Carlos wrote: > > > > Sure. But no one's sure of the cause

[bug #64059] 'make install' fails when you build outside the source tree

Update of bug #64059 (project groff): Summary: 'make install' fails when you build on a different directory => 'make install' fails when you build outside the source tree ___ Reply to this item at:

Re: user-defined characters, translation maps, and environment binding

[self-follow-up] It turns out groff has changed the way not merely `char`, but the vaunted `tr` itself, has worked before. https://git.savannah.gnu.org/cgit/groff.git/commit/?id=21260e1cd2f6fed6b7798fae6078c4e0270d9641 Once upon a time, you could do this: .tr éÉ ...and on non-preconv'ed

Re: Comprehension problem with macros

At 2023-04-24T12:11:02+0100, Ralph Corderoy wrote: > > > yes, I remember having heard of the two different modes > > > > "Copy mode" and (not copy mode), which didn't have a name in CSTR > > #54. (Terser is better. :-| ) > > No name is needed. It would be clutter to add it. troff is either in

Re: user-defined characters, translation maps, and environment binding

At 2023-04-24T11:31:10+0100, Ralph Corderoy wrote: > > > .char £ pound sterling > > > .char $ United States dollar > > > . > > > The £ and $ are almost at par. > > > . > > > .tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ > > > £ crashes overnight! > > > .

Re: Comprehension problem with macros

Hi Branden, > > yes, I remember having heard of the two different modes > > "Copy mode" and (not copy mode), which didn't have a name in CSTR #54. > (Terser is better. :-| ) No name is needed. It would be clutter to add it. troff is either in copy mode or is not in copy mode. There is no

Re: Terminal problem? man formatting problem?

Thank you indeed! Long bygone are the times when I still actively worked with the X Window System and Athena Widgets. The shift-+ had slipped by, I was so accustomed to use ctrl-+. Branden had already told me to use -fn. Thank you again, Oliver. On 24/04/2023 11:55, Frederic Chartier

[bug #64104] [troff] you can set the escape, control, and no-break control characters to the same thing

Update of bug #64104 (project groff): Summary: [troff] you can set the control and no-break control characters to the same thing => [troff] you can set the escape, control, and no-break control characters to the same thing

Re: user-defined characters, translation maps, and environment binding

Hi Branden, > > .char £ pound sterling > > .char $ United States dollar > > . > > The £ and $ are almost at par. > > . > > .tr aAbBcCdDeEfFgGhHiIjJkKlLmMnNoOpPqQrRsStTuUvVwWxXyYzZ > > £ crashes overnight! > > . > > .pl \n(nlu > > ^D > > The pound

[bug #64104] [troff] you can set the control and no-break control characters to the same thing

Follow-up Comment #2, bug #64104 (project groff): Missing word typo. [comment #1 comment #1:] > Oh, also, we should bring the hammer down on trying to set the escape character to either of the control characters, if that hammer is NOT being dropped already. Basically, when attempting to assign

[bug #64104] [troff] you can set the control and no-break control characters to the same thing

Follow-up Comment #1, bug #64104 (project groff): Oh, also, we should bring the hammer down on trying to set the escape character to either of the control characters, if that hammer is being dropped already. ___ Reply to this item at:

[bug #64104] [troff] you can set the control and no-break control characters to the same thing

URL: Summary: [troff] you can set the control and no-break control characters to the same thing Group: GNU roff Submitter: gbranden Submitted: Mon 24 Apr 2023 10:08:22 AM UTC

[bug #64103] [troff] changing the control character doesn't affect macro definition endings

URL: Summary: [troff] changing the control character doesn't affect macro definition endings Group: GNU roff Submitter: gbranden Submitted: Mon 24 Apr 2023 09:57:43 AM UTC

Re: Terminal problem? man formatting problem?

On 2023-04-24 03:49 +0200, Oliver Corff wrote: > I cannot use xterm, uxterm and Eterm on my system because of the high > screen resolution; those terminal windows appear as tiny stamps which do > not accept the Ctrl-+ resizing command. With XTerm, the font can be set in three ways that I know

user-defined characters, translation maps, and environment binding (was: Proposed: stop subjecting right-hand sides of `char` family requests)

Returning to this issue for a moment before I get back to 1.23 release candidate concerns... At 2023-04-01T19:45:19-0400, Douglas McIlroy wrote: > The first use of .char that came to mind was > .char \[ntilde] \o'n~' > which would collide badly with the following ancient trick for >

[bug #64101] improve diagnostic for bad string argument

Follow-up Comment #1, bug #64101 (project groff): I just ran into the same diagnostic! We may be poking our fingers into similar things. But in my case, I got it on legitimate input. I'll file a separate bug for the incorrect diagnosis (rather than the wording) but wanted to record it here as

Re: Disposition of groff 1.23.0.rc4 feedback issues

[self-follow-up] I thought I should update the list below with more complete regression- from-1.22.4 information. At 2023-04-20T15:00:47-0500, G. Branden Robinson wrote: > I've pushed a new personal staging branch, branden-2023-04-20 to > groff's Git repository. I've also pushed some