From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch: import replacement for ape/patch
Date: Mon, 23 May 2022 21:38:11 -0500 [thread overview]
Message-ID: <20220523213811.003a6079@spruce.localdomain> (raw)
In-Reply-To: <YouEs1pT6AGSYIj+@beryllium.local>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Mon, 23 May 2022 12:57:23 +0000
Humm <hummsmith42@gmail.com> wrote:
> >Content-Type: application/x-troff-man
>
> text/troff exists.
A man page is a specific kind of troff file.
(do mime types even matter?)
>
> The following options are supported:
> .\" …
> .IR git/export (1)
>
> .SH BUGS
>
> In troff, blank lines are UB. They should be removed or replaced by
> lines with just a period.
>
Is that true? I'm having trouble finding a reference.
https://www.gnu.org/software/groff/manual/html_node/Basics.html
Sometimes a new output line should be started even though the current
line is not yet full; for example, at the end of a paragraph. To do
this it is possible to cause a break, which starts a new output line.
Some requests cause a break automatically, as normally do blank input
lines and input lines beginning with a space.
That blank line needs to be removed anyways since it adds extra space
between the SEE ALSO section and BUGS section.
Also fixed a typo: apply -> applies
See attached.
Thanks,
Amavect
[-- Attachment #2: patch.man --]
[-- Type: application/x-troff-man, Size: 1023 bytes --]
next prev parent reply other threads:[~2022-05-24 2:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 22:57 ori
2022-05-22 23:09 ` ori
2022-05-23 3:18 ` Amavect
2022-05-23 12:57 ` Humm
2022-05-24 2:38 ` Amavect [this message]
2022-05-24 16:39 ` Humm
2022-05-24 18:44 ` umbraticus
2022-05-24 19:42 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-24 21:19 ` Amavect
2022-05-23 21:40 ` ori
2022-05-23 23:51 ` ori
2022-05-28 21:09 ` ori
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=20220523213811.003a6079@spruce.localdomain \
--to=amavect@gmail.com \
--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).