Re: [groff] Release Candidate 1.22.4.rc3

Hi Branden, > Last I checked (years ago), the texinfo development mailing list was > openly discussing its options for winding up the project. It's just > not very ergonomic for anyone except militant Emacs partisans, and > pinfo, the info browser with key bindings friendly to mere mortals, is >

Re: [groff] Release Candidate 1.22.4.rc3

Hi Larry, Larry Kollar wrote on Thu, Nov 29, 2018 at 11:02:32PM -0500: > Cool. Believe it or not, that's the first time I've seen mdoc options > done that way. Most everyone seems to run them together on a single line, That's surprising, given that Cynthia developed mdoc(7) long before Werner

Re: [groff] Release Candidate 1.22.4.rc3

On Thursday, 29 November 2018 13:52:53 GMT Mike Bianchi wrote: > Wow! > Just a quick glance and I learned about \n[.F] ! Never knew that. > ((Also never saw a number register with string content.)) > page 113 > \n[.F] This string-valued register returns the current input file >

Re: [groff] Release Candidate 1.22.4.rc3

> Yeah. Even Mojave (the latest MacOS) has Groff 1.19.2. I basically have > to recompile and overwrite the base install after every system update. You should really be using Homebrew for that: $ brew install groff $ which groff /usr/local/bin/groff However, the problem Ingo

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: > >> Being a fan of semantic markup myself, I'd normally agree. >> On the other hand, wouldn't the groff manpages always come >> with a groff formatter? > > Don't FreeBSD manual pages always come with FreeBSD and Linux manual > pages always with Linux? No, they dont't, i

Re: [groff] Release Candidate 1.22.4.rc3

On Thu, Nov 29, 2018 at 12:15:35PM +, Deri wrote: > : > You can get a preview of what I have done by downloading the groff book here:- > http://chuzzlewit.co.uk/groff_book.pdf Wow! Just a quick glance and I learned about \n[.F] ! Never knew that. ((Also never saw a number register

Re: [groff] Release Candidate 1.22.4.rc3

On Thursday, 29 November 2018 01:03:26 GMT G. Branden Robinson wrote: > At 2018-11-29T00:25:05+, Deri wrote: > > I'm interested in the groff book which is currently generated from the > > texinfo document. I have done some work which merges texinfo source > > and several man pages to produce

Re: [groff] Release Candidate 1.22.4.rc3

Hi Larry, Larry Kollar wrote on Wed, Nov 28, 2018 at 11:42:00PM -0500: > Ingo Schwarze wrote: >> Branden wrote: >>> * My semantic macro package extending groff_man(7), if I can get it >>> where I'm happy with it and folks on the list don't bleed from the >>> eyes about it. >> That would be a

Re: [groff] Release Candidate 1.22.4.rc3

Hi Larry, Larry Kollar wrote on Wed, Nov 28, 2018 at 11:09:20PM -0500: > Ingo Schwarze wrote: >> While i'm well aware that what i'm saying here is a commitment to >> a huge project, i'm willing to translate the whole groff texinfo >> documentation into groff_mdoc(7). > That's going to be an

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: >> * My semantic macro package extending groff_man(7), if I can get it >> where I'm happy with it and folks on the list don't bleed from the >> eyes about it. > > That would be a HUGE step backwards, making the groff manual pages > even less portable (they are already

Re: [groff] Release Candidate 1.22.4.rc3

Ingo Schwarze wrote: > While i'm well aware that what i'm saying here is a commitment to > a huge project, i'm willing to translate the whole groff texinfo > documentation into groff_mdoc(7). That’s going to be an impressive undertaking. I’m trying to visualize the results—would you make each

Re: [groff] Release Candidate 1.22.4.rc3

Hi Brandon, G. Branden Robinson wrote on Wed, Nov 28, 2018 at 06:44:32PM -0500: > At 2018-11-28T23:09:34+0100, Bertrand Garrigues wrote: > > On Sun, Nov 04 2018 at 01:18:32 AM, "G. Branden Robinson" > > wrote: > B. A few bits of my advice in groff_man.7 about which things get marked > up in

Re: [groff] Release Candidate 1.22.4.rc3

Hi, G. Branden Robinson wrote on Wed, Nov 28, 2018 at 08:03:26PM -0500: > The Texinfo manual is far too easy to overlook (I've certainly been > guilty of it) partly because the Texinfo ecosystem itself is not very > healthy. Last I checked (years ago), the texinfo development mailing > list was

Re: [groff] Release Candidate 1.22.4.rc3

At 2018-11-29T00:25:05+, Deri wrote: > I'm interested in the groff book which is currently generated from the > texinfo document. I have done some work which merges texinfo source > and several man pages to produce an indexed pdf. It is not ready for > this release, but I'm hoping to get it

Re: [groff] Release Candidate 1.22.4.rc3

On Wednesday, 28 November 2018 23:44:32 GMT G. Branden Robinson wrote: > The only other thing I would even think of proposing is taking the man > macro package documentation _out_ of the Texinfo manual, since > groff_man.7.man is where that material is actively maintained. I > already have a git

Re: [groff] Release Candidate 1.22.4.rc3

At 2018-11-28T23:09:34+0100, Bertrand Garrigues wrote: > Hi Branden, > > We have both made some commits recently and I think we are not far from > making the final release, I was hoping you'd say something like that. :) > On Sun, Nov 04 2018 at 01:18:32 AM, "G. Branden Robinson" > wrote: > >

Re: [groff] Release Candidate 1.22.4.rc3

Hi Branden, We have both made some commits recently and I think we are not far from making the final release, On Sun, Nov 04 2018 at 01:18:32 AM, "G. Branden Robinson" wrote: > I'd like to propose resolving the following 4 issues before going final. > > 1. Resolve this compiler warning: > >

Re: [groff] Release Candidate 1.22.4.rc3

At 2018-11-04T02:25:37+0100, Bertrand Garrigues wrote: > Apologies for my long silence; due to personal problems I wasn't able to > work on groff these last months. Hi Bertrand, I hope things are getting better for you! > Version 1.22.4.rc2 no longer build on my environment (Archlinux) because

[groff] Release Candidate 1.22.4.rc3

(was: [groff] Release Candidate 1.22.4.rc2) Hi, On Sat, Nov 03 2018 at 11:55:51 AM, Colin Watson wrote: > I hate to nag, but is there any likelihood of a 1.22.4 release in the > somewhat near future? My next relevant deadline is that the freeze for > the next Debian release will begin in