Re: Description of the naming conventions for variables, macros, etc in MS?

T. Kurt Bond wrote: > Is there a description of the naming conventions used in the groff ms > macros for variables, macros, and so forth? An * seems to mean > internal and ! seems to mean array, for instance. What does @ mean? I think it’s an internal destination-like thing. For example, a l

Re: Footnote line length ratio to current line length

On 8/6/20, T. Kurt Bond wrote: > If you don't set either FL or fn:MCLL the groff ms macros default to > making the footnote length 5/6 the length of the current line length. That's a bizarre default. Defaults should reflect the most common cases. Footnotes are typically the full width of the co

Re: Footnote line length ratio to current line length

For what it is worth, I like this idea (and the fact a patch was included). It's always sort of bugged me that it limits it to 5/6, I'm sure there was a reason but I think it should match line length. On Thu, Aug 06, 2020 at 11:53:38AM -0400, T. Kurt Bond wrote: > groff_ms(7) says that changing th

Description of the naming conventions for variables, macros, etc in MS?

Is there a description of the naming conventions used in the groff ms macros for variables, macros, and so forth? An * seems to mean internal and ! seems to mean array, for instance. What does @ mean? -- T. Kurt Bond, tkurtb...@gmail.com

Footnote line length ratio to current line length

groff_ms(7) says that changing the number register FL is effective at the next footnote. That seems to be true only for one column text. In multicolumn text you have to change the undocumented fn:MCLL after calling .MC. fn:MCLL is an alias for the number register pg@fn-colw, which is set when .M

Re: Groff should not permit ANSI escapes using \N'27'

> > I don't think they're stripped for security reasons, but because groff > repurposes chunks of the control-character code space for its own uses. Oh. Erh, I didn't know that... I kind of assumed that, being the escape character, it was filtered for the reasons I described earlier. Is this rea

Re: Future of groff Texinfo manual (was: documentation of hyphenation)

At 2020-07-24T12:37:26-0400, Larry Kollar wrote: > G. Branden Robinson wrote: > > > > Hmm! It seems the ms stuff in our Texinfo manual may have started > > life as an ms document after all. > > > > IIRC, Larry Kollar is sometimes seen on this list. Maybe he'd be > > willing to share a copy of

Re: how far can i go with grotty?

Hi Marc, At 2020-07-24T19:46:21+0200, Marc Chantreux wrote: > hello roffers, > > i wrote this filter > > sed ' > 1i.TS\ > tab(:);\ > lB l l l. > $a.TE > ' | tbl |groff -kTutf8 | sed '/^$/q' > > so i can get readable tables as stdout of my shell scripts. i wrote it > as a

Re: tbl: off-by-one line error at table ends with grotty?

At 2020-07-25T11:09:04-0400, Doug McIlroy wrote: > > Why would you want a table *inside* a paragraph rather than > > starting a new paragraph after a table? > > The table may be in a floating keep (e.g. .KF in -ms mmacros). > Then it's quite likely to pop up in the middle of a paragraph. > > Th

Re: ATTN groff Savannah administrators: category request

At 2020-07-25T08:11:36-0500, Dave Kemper wrote: > Does anyone ever collect data on closed groff bug reports for > anything? If so, closed bugs concerning -me should also be moved to > the new category. > > Offhand this seems to include > > http://savannah.gnu.org/bugs/?54958 > http://savannah.gn

Re: \: re-enables hyphenation--should it?

At 2020-07-25T13:09:29-0500, Dave Kemper wrote: > On 7/25/20, Steve Izma wrote: > > Doesn't this depend on the definition of a word boundary? > > Yes. I admit I've done no testing or research for this thread, but > past experience tells me that the \% escape treats whitespace and not > much else

Re: \: re-enables hyphenation--should it?

At 2020-07-31T17:41:06-0500, Dave Kemper wrote: > On 7/31/20, Larry Kollar wrote: > > It’s a space, which I would presume ends a word. A zero-width space, > > by definition, but still a space. > > I suppose that depends where you're getting your definition. The > groff(7) man page and the Texinf

Re: Groff should not permit ANSI escapes using \N'27'

At 2020-07-28T00:26:49+1000, John Gardner wrote: > Hi folks, > > Raw escape characters (U+001B) get stripped from source-code during > formatting, but inserting one is still possible using \N'27': I don't think they're stripped for security reasons, but because groff repurposes chunks of the cont

[ms] Is there any way to change the amount of space before a section header?

At 2020-08-02T02:03:19-0400, T. Kurt Bond wrote: > I'd like to reduce the amount of space before a section header. I'd really > like to have the amount of space be proportional to the depth of the > section header. I've tried defining my own version of SH-NO-TAG in my > source file, but it doesn'

Re: Old -me repository?

At 2020-08-03T14:24:00-0500, Dave Kemper wrote: > Heirloom troff and groff both include forks of Eric Allman's original > -me macro set. According to the header blocks of the respective > files, groff's -me macros are forked from version 2.31 of Allman's, > and Heirloom's from version 2.14. Is th