Follow-up Comment #9, bug #63958 (project groff):
FWIW, AT&T nroff renders it as:
$ nrcon -mdoc /tmp/x | less
timerdday(3) BSD Programmer's Manual
timerdday(3)
NAME
timerdday - compute time of launch operation within window
SYNOPSIS
void
timerdday(str
Follow-up Comment #8, bug #64018 (project groff):
Just chiming in that the change from GNU groff 1.22.x to 1.23 in GNU mdoc is
wrapping all my manpages badly because it reduces the already very narrow
screen estate.
I’m using AT&T nroff with UCB mdoc to write my manpages, but make their
rendering
Follow-up Comment #10, bug #64018 (project groff):
Merely ugly.
Old:
SYNOPSIS
mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] [file [arg1 ...]]
mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] -c cmd [arg0 ...]
mksh [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] -s
Follow-up Comment #11, bug #64018 (project groff):
Oh sorry, submitted too early.
The codebase is the “last” nroff I could use under the Caldera licence,
i.e. that was shipped with a BSD covered by these. The macropackages are a
conglomerate from the TUHS archives and pre-mdocml OpenBSD’s, but I
Follow-up Comment #11, bug #63958 (project groff):
Sorry, didn’t know about the formatting, it’s not all that clear in lynx,
and the preview looked okay… in lynx, at least.
I very much don’t like the mdocml output that doesn’t indent continuation
lines. (On the other hand, UCB mdoc indents “too m
Follow-up Comment #13, bug #63958 (project groff):
(you can press ^Xe in a in lynx,
and it will spawn your $EDITOR on it; it’s
okay for shorter things though)
The current continuation indent in gnroff in Debian sid
seems to be… the width of Nm plus one space. Ingenious.
(We’re talking about
Follow-up Comment #14, bug #64018 (project groff):
> Possibly, _mdoc_(7) page authors knew this and carefully edited the
> ones that did, so that now no one sees them.
Exactly, we do that… I recently also begun rewording things to
avoid hyphenation as well, although only with “french” spacing
(
Follow-up Comment #15, bug #63958 (project groff):
> Another approach would be to have every argumentful call to `Nm` update an
> internal register that stores the continuation indentation amount.
Is that not too late at that point? Don’t we need to set the
indent before the .Nm gets rendered?
Follow-up Comment #16, bug #63958 (project groff):
Oh wait, continuation indent is different depending on whether it’s a
section 1/8 or section 2/3!
For section 1/8 (.Nm) we already behave identically (save for the base
indent), so the Nm-based thing is already done õÕ
For section 2/3 (.Ft) howe
Follow-up Comment #17, bug #63958 (project groff):
Well, maybe one thing. SYNOPSIS is not justified in nroff/UCB mdoc: (this is
with the latest commit to change the continuation indent already applied)
SYNOPSIS
timerdday [-+abCefhiklmnprUuvXx] [-+o option] [-T [!]tty|-] [file [arg1
Follow-up Comment #16, bug #64018 (project groff):
My stance on that is: you can do two spaces after a full stop if you want (I
won’t as I’m continental-european), but not in fixed-width / monospaced
settings, as the dot is already widened there by necessity. But I was just
using the terms america
Follow-up Comment #20, bug #64018 (project groff):
Hmh. I personally don’t care about the obsolete/legacy man(7) macropackage,
only mdoc(7), but 7n sounds like *quite* a lot, and I would rather mdoc(7)
stick to 5n as it used to.
___
Reply
Follow-up Comment #23, bug #64018 (project groff):
Thanks for the history! I also don’t see it used anywhere really.
>By the way, do we still have that ancient README file in the groff git tree?
>I think that OpenBSD still has it lying around in the source tree in
>/usr/src/share/tmac/mdoc/README
13 matches
Mail list logo
