From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] usb(3) patch
Date: Mon, 21 Jun 2021 20:00:01 +0930 [thread overview]
Message-ID: <B195508DE6C8BBFB50A64389454A9F1D@musolino.id.au> (raw)
In-Reply-To: <65ED76F7654551B63A97751B216B408F@9lab.org>
> I realise I did not accurately state where I saw the issue, namely
> with the printed version of the manuals. There, at the top of the
> page there is a verbatim `delim $$` printed, here a picture:
>
> • https://9lab.org/img/plan9/random/usb3.man.book.jpg
>
> Need to repro the typesetting steps of the book and see what
> happened there…
We're just not running eqn(1) for usb(3) in /sys/man/mkfile. I've
pushed a couple of changes to fix it.
prev parent reply other threads:[~2021-06-21 10:34 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
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 ` Alex Musolino [this message]
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=B195508DE6C8BBFB50A64389454A9F1D@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).