Hi folks,
In light of the recent discussion about the aq ("apostrophe quote")
character escape, please review the attached patch.
Please find attached a patch to set a better example for ourselves and
our readers.
N.B. that I did not do blind substitutions; uses of the escape outside
of prose co
At 2017-04-30T17:11:30+0100, Ralph Corderoy wrote:
> Hi Branden,
>
> > The remaining man pages categorize as follows:
> >
> > mandb(1)FONT_MACRO_C
> > nmcli(1)DOCBOOK_C
> > passwd(1) DOCBOOK_C
> ...
>
> Have you a summary combi
At 2017-04-30T19:34:20-0400, James K. Lowden wrote:
> On Fri, 28 Apr 2017 01:15:05 -0400
> "G. Branden Robinson" wrote:
> > C adopted designated initializers, a sop to those who can't recall
> > what order a struct's fields come in.
>
> I guess you're implying that designated initializers, while
At 2017-04-30T21:06:12+0100, Ralph Corderoy wrote:
> Hi Branden,
>
> > > > Also, the linitan(1) tool that is a huge part of Debian package QA
> > > > checks man pages for many problems, and I think this is one of
> > > > them.
> > >
> > > I had a look at https://lintian.debian.org/tags-all.html, s
On Fri, 28 Apr 2017 01:15:05 -0400
"G. Branden Robinson" wrote:
> the benefit to the user is relatively few keystrokes above those
> > needed for the text.
>
> Did you write your DocBook-based user guide in ed?
>
> Nothing has come close to saving me more keystrokes than at the
> shell prompt
Hi Branden,
> > > Also, the linitan(1) tool that is a huge part of Debian package QA
> > > checks man pages for many problems, and I think this is one of
> > > them.
> >
> > I had a look at https://lintian.debian.org/tags-all.html, searching
> > for `manpage', but didn't spot it?
...
> Here are so
At 2017-04-30T15:07:15+0100, Ralph Corderoy wrote:
> Hi Branden,
>
> > 22 . if '\*[.T]'utf8' \
> > 23 .char - \[hy]
> > 24 .
> >
> > Also, the linitan(1) tool that is a huge part of Debian package QA
> > checks man pages for many problems, and I think this is one of them.
>
>
Hi Doug,
> The convention of dropping irrelevant attributes may have been
> justified during the experimental days of pic's development, but seems
> cheesy now, nearly 40 years on.
I agree a "strict" parsing, considering all attributes relevant, that
disallows `box radius 3' would ease writing pi
Hi Branden,
> > Besides, i did not even try to list ad-hoc non-roff man(7) parsers.
>
> This may warrant another thread, but how many of _those_ are still
> alive?
There's https://manned.org/
It's useful because it has man pages from many different systems, and
saves having to install a large pac
Hi Branden,
> The remaining man pages categorize as follows:
>
> mandb(1)FONT_MACRO_C
> nmcli(1)DOCBOOK_C
> passwd(1) DOCBOOK_C
...
Have you a summary combining your two survey-result sets?
For this email, it's
$ sed '/^ma
>
> *By mixing low-level roff(7) syntax into your mdoc(7) document, like
> defining*
*your own macros, you gratuitiously endanger portability.*
...
*You are being selfish. If you forcefully redefine standard macros, the
> result*
*will look unnatural to *everyone else**
Some documents I write
Hi,
Ingo wrote:
> Manuals tend to have so much font jumping anyway
> that they are often not very visually pleasing and look noisy.
That's true. And my crude understanding of typography is that 𝑖𝑡𝑎𝑙𝑖𝑐 is
normally used for emphasis, with 𝐛𝐨𝐥𝐝 being kept in reserve for that odd
time when t
Hi Ingo,
> That leads to a natural suggestion solving *both* of these problems:
>
> - Make sure *all* output devices (even UTF-8) render - as a
>typographic hyphen (U+2010 HYPHEN) even in manual pages.
>That solves the second problem brought up in this mail.
>Yes, it will require fixi
Hi John,
John Gardner wrote on Sun, Apr 30, 2017 at 10:50:23PM +1000:
> .de XR
> . Xr \\fB\\$1\\fP \\$2
> ..
That's a bad idea for three reasons.
1. It already stands out by the (N), additional font change is not
required. Manuals tend to have so much font jumping anyway
that they are
Hi Branden,
> 22 . if '\*[.T]'utf8' \
> 23 .char - \[hy]
> 24 .
>
> Also, the linitan(1) tool that is a huge part of Debian package QA
> checks man pages for many problems, and I think this is one of them.
I had a look at https://lintian.debian.org/tags-all.html, searching for
Chained commands are easier to follow with syntax highlighting:
[image: Inline images 1]
But I'm still in agreement with Ralph here, at least with regards to
complex formatting. Lines like `.It Ar radius` are fine, but the Ns and No
commands... ugh. Even when formatting with mdoc, I find it benef
Hi Ingo,
> > > .Fl S Ar var Ns Op Pf = Ar value
> >
> > This has reminded me of one reason I didn't get on with mdoc. Only
> > the `Fl' is obviously mdoc's, due to the `.' invocation. The rest
> > are a mix of command and data, but without any sigil one's left
> > guessing unless the command set
Sorry for the delayed response. Some pull-requests needed tending to before
I had a chance to go through all this.
First, thank you all so much for your help and patience! It truly means a
lot. I've not yet got arcs drawing correctly, but I feel I'm coming close.
Branden's pointers on trigonometry
18 matches
Mail list logo
