From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] usb(3) patch
Date: Sun, 20 Jun 2021 20:58:11 +0930 [thread overview]
Message-ID: <8B46E0A98BD2712374CA9527E736B5F7@musolino.id.au> (raw)
In-Reply-To: <BBCF358ED57C45F01A278FA4BF64C751@9lab.org>
> The print version of usb(3) contains a verbatim `delim $$` at
> the top of the page. Remove it as it looks like a mishap that
> occurred during a bulk import (see `git/log /sys/man/3/usb`.
No, this is required. It is setting the delimiter for eqn(1). Have a
look at /sys/man/3/usb:369. Without setting the delimiter this part
is ignored by eqn(1) and rendered incorrectly when viewed with page
(e.g. `man -P 3 usb`).
next prev parent reply other threads:[~2021-06-20 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 23:59 igor
2021-06-20 11:28 ` Alex Musolino [this message]
2021-06-20 23:22 ` igor
2021-06-21 8:42 ` [9front] [PATCH] manual: preprocess usb(3) with eqn for print output Anthony Martin
2021-06-21 10:30 ` [9front] usb(3) patch Alex Musolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8B46E0A98BD2712374CA9527E736B5F7@musolino.id.au \
--to=alex@musolino.id.au \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).