Re: Releasing groff 1.22.5?

2020-10-21 Thread Bertrand Garrigues via
Hi, On Wed, Oct 21 2020 at 01:24:25 AM, Bertrand Garrigues wrote: > Building a 1.23.rc1 tag unexpectedly broke all the mom examples > generation (there's just garbage in the pdf files). I'll try to figure > out why tomorrow. This is because of the: const char *revision = "rc1"; in the gene

Re: Learning troff - where to start?

2020-10-21 Thread Wim Stockman
maybe you can start by reading the book. it has new life on github. https://github.com/larrykollar/Unix-Text-Processing Op wo 21 okt. 2020 om 21:47 schreef Johann Höchtl : > > On 19.10.20 14:14, Johann Höchtl wrote: > > > > On 15.10.20 16:37, Pierre-Jean Fichet wrote: > >> To fetch for ideas on h

Re: Learning troff - where to start?

2020-10-21 Thread Johann Höchtl
On 19.10.20 14:14, Johann Höchtl wrote: On 15.10.20 16:37, Pierre-Jean Fichet wrote: To fetch for ideas on how to do this or that, maybe can I also point to my macros, as they'll work with neatroff too, and implement a lot of things: https://github.com/pjfichet/utmac/ I installed utmac by

Re: Releasing groff 1.22.5?

2020-10-21 Thread Ingo Schwarze
Hi, Ingo Schwarze wrote on Thu, Oct 15, 2020 at 05:32:32PM +0200: > Meanwhile, i heard rumours that the upcoming change in libc that will > cause %n in writeable memory to abort the program will cause some > gnulib ./configure tests to (wrongly) fail, again resulting in > compilation of vasnprint

Re: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

2020-10-21 Thread Steffen Nurpmeso
|Steffen has withdrawn most/all of his other patches and even after reading I do not know what this has to do with this bug. |this report a few times I'm not clear on what exactly the problem is supposed |to be. | |The "solution", "drop gnulib", is not likely, especially not during an RC |c