Hi,
Russ Allbery wrote on Sat, Dec 24, 2022 at 02:43:44PM -0800:
> "G. Branden Robinson" writes:
>> At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
>>> I've been curious: how much use do you see of groff outside
>>> of man pages?
I use it for the slides of all my conference presentations,
and
Hi Branden,
> > # Get a count of the number of lines before the first blank line, which
> > # we'll pass to .Vb as its parameter. This tells *roff to keep that
> > many
> > # lines together. We don't want to tell *roff to keep huge blocks
> > # together.
> > my @lines =
At 2022-12-24T14:43:44-0800, Russ Allbery wrote:
> I probably should have assumed. One of the things that I've noticed
> over and over about free software is that nothing new ever truly
> replaces something old in a comprehensive sense. I can think of very
> few programs that truly no one is
On Saturday, 24 December 2022 01:26:22 GMT Richard Morse wrote:
> > I've been curious: how much use do you see of groff outside of man pages?
>
> I realize I’m just one person, but my use of groff (and Heirloom for using
> useful fonts) is entirely outside of man pages…
>
> Ricky
At the start
* On 2022 24 Dec 16:45 -0600, Russ Allbery wrote:
> "G. Branden Robinson" writes:
> > At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
>
> >> I've been curious: how much use do you see of groff outside of man
> >> pages?
About 18 months ago I received some good help on this list for setting
up
Hi All,
On 23/12/2022 21:49, Russ Allbery wrote:
I've been curious: how much use do you see of groff outside of man pages?
Well, I've never written a single man page with the man macro set. I
have to confess, though, that during the early 1990s I wrote software
for MSDOS (that was the only
"G. Branden Robinson" writes:
> At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
>> I've been curious: how much use do you see of groff outside of man
>> pages?
> Others have answered this but I would also point you to Ralph Corderoy's
> page on the subject.
> https://www.troff.org/pubs.html
"G. Branden Robinson" writes:
> These are all correct statements.
> There are two major points to make here.
> 1. Request invocations are not macro calls. So all that stuff about
> double quotes we were talking about doesn't apply here. :(
> Sorry about that. That was a language
"G. Branden Robinson" writes:
> At 2022-12-23T10:03:13-0800, Russ Allbery wrote:
>> Yeah, the difficulty lies mostly in the layering, because people can
>> write POD source that is nonsensical in a man page context but that I
>> still have to do something with. Stuff like C<<< B<< L >> >>>.
>
Hi Russ,
At 2022-12-23T14:42:42-0800, Russ Allbery wrote:
> Incidentally, the rules for the second argument to .ds appear to not
> follow the normal rules for macro arguments.
>
> .ds C` ""
>
> defines \*(C` to a single double-quote, but:
>
> .ds C`
>
> defines \*(C` to """, not to " as
At 2022-12-23T12:49:15-0800, Russ Allbery wrote:
> "G. Branden Robinson" writes:
> > Right. Four or five years ago I proposed a new groff special
> > character identifier `\(hm` to cover this case. But this was not
> > met with assent, and I concede that the problem may be confined to
> > man
Hi Russ,
At 2022-12-23T10:03:13-0800, Russ Allbery wrote:
> "G. Branden Robinson" writes:
> > That's fair, and it isn't the first time I've heard capable people
> > express the opinion that having a document translator produce
> > idiomatic man(7) font alternation macro calls rather than chains
On 24/12/22 12:26, Richard Morse wrote:
On Dec 23, 2022, at 3:49 PM, Russ Allbery wrote:
I've been curious: how much use do you see of groff outside of man pages?
I realize I’m just one person, but my use of groff (and Heirloom for using
useful fonts) is entirely outside of man pages…
Like
On Dec 23, 2022, at 3:49 PM, Russ Allbery wrote:
>
> I've been curious: how much use do you see of groff outside of man pages?
I realize I’m just one person, but my use of groff (and Heirloom for using
useful fonts) is entirely outside of man pages…
Ricky
"G. Branden Robinson" writes:
>For the (neutral) double quote, you have recourse to an obscure
> syntactical feature of AT 'troff'. Because a double quote can begin a
> macro argument, the formatter keeps track of whether the current
> argument was started thus, and doesn't require a space
"G. Branden Robinson" writes:
> Right. Four or five years ago I proposed a new groff special character
> identifier `\(hm` to cover this case. But this was not met with assent,
> and I concede that the problem may be confined to man pages.
I've been curious: how much use do you see of groff
"G. Branden Robinson" writes:
> That's fair, and it isn't the first time I've heard capable people
> express the opinion that having a document translator produce idiomatic
> man(7) font alternation macro calls rather than chains of font selection
> escape sequences was Just Too Damned Hard. If
At 2022-12-13T11:33:50-0800, Russ Allbery wrote:
> Just a quick reply on one part of this with more to come later.
Sure, no worries.
> "G. Branden Robinson" writes:
> > Oh, I know. I've seen Pod::Man's preamble. I think what distressed
> > me originally about it was that, like docbook-to-man,
Just a quick reply on one part of this with more to come later.
"G. Branden Robinson" writes:
> Oh, I know. I've seen Pod::Man's preamble. I think what distressed me
> originally about it was that, like docbook-to-man, it seemed to make
> man(7) seem like a write-only language.
This bothers
Hi Russ,
[finally getting back to this]
At 2022-11-28T08:45:34-0800, Russ Allbery wrote:
> "G. Branden Robinson via tz" writes:
>
> > Most people won't see a difference because groff 1.22.4 (and earlier
> > releases going back to, I think, 2009) the man(7) macro package
> > remaps the hyphen
20 matches
Mail list logo
