Re: Portability to Mac OS X

2021-11-23 Thread Werner LEMBERG
>> > 6. Some time ago I bumped our minimum required Texinfo version to >> >5.0 (for a few reasons[5]), and this is too new for stock Mac >> >OS X (makeinfo 4.8). However, it should be possible to make >> >generated *.info files part of the distribution archive and >> >thereby red

Re: Portability to Mac OS X

2021-11-23 Thread G. Branden Robinson
Hi, Werner! At 2021-10-27T07:36:13+, Werner LEMBERG wrote: > > 6. Some time ago I bumped our minimum required Texinfo version to > >5.0 (for a few reasons[5]), and this is too new for stock Mac OS > >X (makeinfo 4.8). However, it should be possible to make > >generated *.info file

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread Deri
On Friday, 29 October 2021 21:24:45 BST T. Kurt Bond wrote: > > The pdf I sent to the list yesterday [ > > https://lists.gnu.org/archive/html/groff/2021-10/msg00094.html ] Is > produced entirely by groff and has a full clickable index. > > Wonderful! Someone *was* suitably inspired to implement

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread T. Kurt Bond
> The pdf I sent to the list yesterday [ https://lists.gnu.org/archive/html/groff/2021-10/msg00094.html ] Is produced entirely by groff and has a full clickable index. Wonderful! Someone *was* suitably inspired to implement multiple indexes! Would it be possible to get references to the start of

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread Deri
On Friday, 29 October 2021 19:38:42 BST T. Kurt Bond wrote: > [I hit "reply" on my previous attempt at this email, so it went only to > Ralph. Sorry about that. At least this version has the correct CSTR #.] > I'm an emacs user, and I use the info version of the groff texinfo manual, > as well as

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread T. Kurt Bond
[I hit "reply" on my previous attempt at this email, so it went only to Ralph. Sorry about that. At least this version has the correct CSTR #.] I'm an emacs user, and I use the info version of the groff texinfo manual, as well as the manual pages, and usually go to the trouble of getting the PDF

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread Ralph Corderoy
Hi John, > I was thinking of ms(7) more than manual pages, actually. > Think single-page HTML output. Based on the transcription this list did of Tim O'Reilly's ‘Unix Text Processing’ — now only available second hand, https://amzn.to/3bkamGb — perhaps an shared effort to switch would work for the

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-29 Thread Ralph Corderoy
Hi John, > In lieu of escaped newlines and awkward sed(1) formatting, you can use > the following line to insert an empty line: > > /^Before$/ { N; s/\n/&&/; } With the caveat that the line read by N won't be processed as it would have been otherwise. These two show the difference which might no

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-28 Thread Larry McVoy
On Fri, Oct 29, 2021 at 05:19:00AM +1100, John Gardner wrote: > I was thinking of ms(7) more than manual pages, actually. Think single-page > HTML output. -ms lends itself to parsing nicely. I wrote something called webroff (in perl) that took ms input and spit out a website. In the early days o

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-28 Thread John Gardner
> > https://mandoc.bsd.lv/texi2mdoc/ I was thinking of ms(7) more than manual pages, actually. Think single-page HTML output. mdoc(7) is too restrictive and specialised to lend itself well to the various applications Texinfo manuals are used for. (Anyway, I was just spitballing. I want an excus

Re: Portability to Mac OS X

2021-10-28 Thread Ingo Schwarze
Hi John, John Gardner wrote on Fri, Oct 29, 2021 at 04:27:50AM +1100: > Even better: a preprocessor to convert Texinfo markup to Roff source > (possibly targeting a macro package). I've said it before, and I'll said it > again: Groff needs TeX about as badly as it needs an Instagram page. > > te

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-28 Thread John Gardner
In lieu of escaped newlines and awkward sed(1) formatting, you can use the following line to insert an empty line: /^Before$/ { N; s/\n/&&/; } Note that BSD sed(1) is picky about braces and semicolons. I have groff building successfully on Mac OS X now. > I recently upgraded to macOS 12.0.1 (M

Re: Portability to Mac OS X

2021-10-27 Thread Werner LEMBERG
> 6. Some time ago I bumped our minimum required Texinfo version to >5.0 (for a few reasons[5]), and this is too new for stock Mac OS >X (makeinfo 4.8). However, it should be possible to make >generated *.info files part of the distribution archive and >thereby reduce the depende

Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

2021-10-26 Thread G. Branden Robinson
Hi, Andreas! At 2021-10-27T00:07:22+0200, Andreas Kusalananda Kähäri wrote: > Actually, that only makes it work with OpenBSD sed and GNU sed. It > still fails with > > sed: Unrecognized command: .lf 1 doc/webpage.ms > > when using Plan 9 sed. Not tested with macOS. > > So it looks like