Re: FWD: [bug #59270] [PATCH] node.h: avoid C++11 feature (non-const init in class)

2020-10-15 Thread G. Branden Robinson
At 2020-10-14T15:45:16+0200, Ingo Schwarze wrote: > Hi, > > this is the second portability issue that killed the build for me. > Again, i'm looking for an OK to push the fix. > > Since i have little experience with C++, please check that the fix is > correct and matches your intent. TL;DR: LGTM,

FWD: [bug #59276] [PATCH] #include "config.h" before

2020-10-15 Thread Ingo Schwarze
Hi, here is the third fatal build error i encountered while trying to build from git on OpenBSD, this time caused by the recent gnulib update. I'm looking for an OK to push the patch appended below. I think it can (and should) go in before release because including "config.h" in a few additional

Re: [bug #59270] [PATCH] node.h: avoid C++11 feature (non-const init in class)

2020-10-15 Thread Ingo Schwarze
Hi Branden, G. Branden Robinson wrote on Thu, Oct 15, 2020 at 11:34:28PM +1100: > At 2020-10-14T15:45:16+0200, Ingo Schwarze wrote: >> this is the second portability issue that killed the build for me. >> Again, i'm looking for an OK to push the fix. >> >> Since i have little experience with C++

Re: Releasing groff 1.22.5?

2020-10-15 Thread Ingo Schwarze
Hi Bertrand, Bertrand Garrigues via wrote on Thu, Oct 15, 2020 at 12:03:44AM +0200: > On Mon, Oct 12 2020 at 06:08:27 PM, Ingo Schwarze wrote: >> A major problem with gnulib emerged just now that we should perhaps >> treat as a blocker. > [...] >> The code in >> >> gnulib/lib/vasnprintf.c >> >

Re: Learning troff - where to start?

2020-10-15 Thread Pierre-Jean Fichet
Hello alls, I'm a neatroff user, and feels, as a result, compelled to give my opinion. I'll second everyone stating that "Nroff/Troff User Manual" (CSTR 54) is the manual of choice. It's 37 pages of well written documentation, and should cover all your needs: https://www.troff.org/54.pdf Then, yo

Re: FWD: [bug #59276] [PATCH] #include "config.h" before

2020-10-15 Thread Colin Watson
On Thu, Oct 15, 2020 at 03:39:29PM +0200, Ingo Schwarze wrote: > I'm looking for an OK to push the patch appended below. > I think it can (and should) go in before release because > including "config.h" in a few additional files is unlikely > to cause regressions with compilers that do not require

Re: Learning troff - where to start?

2020-10-15 Thread Federico Lucifredi
Hi James > On Oct 14, 2020, at 12:08 PM, James K. Lowden > wrote: > > On Wed, 14 Oct 2020 11:13:39 -0400 > Federico Lucifredi wrote: > >>> For man pages, what you need is knowledge of the man macro package, >>> originally written by James Clark [...] >> >> I removed the ?originally? bit, whi

Re: Learning troff - where to start?

2020-10-15 Thread Larry Kollar
Damian McGuckin wrote: > > The UTP Revival Project recreated the source code because Tim and Sale were > unable to locate a copy of the original source. It is located at: > > http://home.windstream.net/kollar/utp/ > > What an undertaking! > > There is a sentence on that page > >

Re: Learning troff - where to start?

2020-10-15 Thread Larry Kollar
Deri wrote: > The UTP Revival Project recreated the source code because Tim and > Sale >> were unable to locate a copy of the original source. It is located at: >> >>http://home.windstream.net/kollar/utp/ > > > There is a version with clickable contents and index here:- > > https:/