an set MANROFFOPT to
-dAD=l to get this behavior for every man page, and I like that this
option exists, but I'm not willing to take the regression and support hit
of having to explain this to every user.)
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
Dave Kemper writes:
> On Fri, Mar 15, 2024 at 8:34 AM G. Branden Robinson
> wrote:
>> At 2024-03-14T22:02:26-0700, Russ Allbery wrote:
>> > Now, any .TP directive restores full justification for all subsequent
>> > text. This appears to be due to the addit
the generated output of Pod::Man of my very first
version in 1999, which strongly implies that it was in Tom Christiansen's
original pod2man script on which Pod::Man was originally based.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
complaint about it, and multiple people
noticed when it broke. Admittedly, the breakage is worse than always
doing full justification, since it changes in the middle of the man page
and thus looks more wrong, but my anecdotal experience is that people
quite like this "feature" of Pod::Man and the advocates for full
justification in nroff seem to be few and far between.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
"G. Branden Robinson" writes:
> At 2024-03-16T12:32:44-0700, Russ Allbery wrote:
>> Okay, I think we've sorted out the way forward for groff that would
>> address the immediate issue. That leaves three questions: should I do
>> something in the next release o
indows
myself in several decades, but I always found it interesting. I've kept
the module working all these years since it's not much additional effort.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
things are "better".
You may find the NOTES section of the Term::ANSIColor man page
interesting, although it's probably out of date since I rely on other
people to send me updates. Term::ANSIColor also comes with test files and
a test file generator that one can cat on a display to see what works.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
or strikethrough and double-underline. I need to add those to the module.
I've made some updates, but I am very overdue for another round of work on
that module.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
ecedence to LICENSES
over COPYING and picking up the copy of the MIT license in that file.
Automatically detecting license information in any complicated scenario is
probably impossible, so it would be nice if GitLab had some way to
override the automatically-detected license. If it does, I hav
eyrie.org/~eagle/software/podlators/>
This package is maintained using Git; see the instructions on the above
page to access the Git repository.
Please let me know of any problems or feature requests not already listed
in the TODO file.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
uotes, and then the double quotes within that
double-quoted string have to be escaped, which *roff does by doubling
them. So:
.CW """$ echo foobar"""
With only two double quotes, I think *roff parses that as an empty string.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
tring ends with three double quotes, but it's better
to think of it as one escaped double quote, which is written as "", and
then the double quote that ends the argument.
This should then produce the output that you want.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
t know that was preferred. I installed the attached patch
> into the tzdb development repository
Just be warned that \f(CR is not a valid font name in all *roff
implementations, which is why Pod::Man uses \f(CW by default. Not sure
how much you care. (And, to be honest, not sure how much
nch of bugs, and I'm dubious enough people
still use troff to make it worth the effort, but apparently the HTML
converters may use them and in theory they work now. So I have left them
alone.)
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
some rather tedious font manipulation in Pod::Man,
although most of the font complexity is still due to the Solaris bug.
I'm guessing that \f(CR would have cleared bold, and \f(CW doesn't because
it's weird and special, and that's why this isn't a bug?
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
t; mandoc maintainer Ingo Schwarze and I both recommend against performing
> string definitions, or interpolating strings, in man pages.
Pod::Man of course does tons of this. I'm always open to alternatives,
but they're all there for a reason
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
ample I don't use .EE/.EX and instead roll my own,
which is kind of sad, let alone stuff like .TQ, .UR, or .SY.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
king as someone maintaining a generator, it's very difficult to know
when I can drop support for old Unixes. It's also very painful to be
wrong; if I delete a bunch of compatibility code, and then later someone
really wants it back, adding it back in is awful.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
Do you know if any platform uses them for
man pages right now? The two implementations I mostly target are groff
and mandoc, since that seems to cover the vast majority of modern systems
and the remainders are using some legacy UNIX code base that basicallly
doesn't exist outside of that UNIX.
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
ell, the correct rule for escaping the second argument to
.ds is that you should double any *leading* double quote, but leave all
the other double quotes alone.
.ds C` "
appears to define \*(C` to the empty string. (I'm not sure where this all
might be documented.)
--
Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
"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 somethi
e this all might be documented.)
> Would it surprise you to learn that I've rewritten parts of groff's
> Texinfo manual to discuss these matters in detail? ;-)
Ah, excellent, thank you. Pod::Man 5.01 will fix some latent bugs in this
area (mostly only relevant if people co
"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 su
23 matches
Mail list logo
