From: Mohamed Akram <mohd.akram@outlook.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: "discuss@mandoc.bsd.lv" <discuss@mandoc.bsd.lv>
Subject: Re: mandoc inserts extraneous <br> tags inside <pre>
Date: Sun, 26 Jun 2022 17:29:27 +0000 [thread overview]
Message-ID: <4F394515-B0B2-45F9-87D6-994D86A16223@outlook.com> (raw)
In-Reply-To: <YriREiOT64mO5pJL@asta-kit.de>
> On Jun 26, 2022, at 9:02 PM, Ingo Schwarze <schwarze@usta.de> wrote:
>
> I'm also in the habit of notifiying bug reporters right after fixing
> their bugs, such that they can pick up and use the patch until the
> release comes, if they want to, and such that they can test
> whether the patch really fixes the problem for them.
That’s really awesome. A patch would be sufficient in my case since I’m just running this on my machine. Also, if anyone else comes across this I found a little workaround in the meantime using some sed magic:
mandoc -T html file | sed '/<pre>/,/<\/pre>/{/^<br\/>$/d;}’
Mohamed
prev parent reply other threads:[~2022-06-26 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-25 16:28 Mohamed Akram
2022-06-26 11:16 ` Ingo Schwarze
2022-06-26 16:41 ` Mohamed Akram
2022-06-26 17:02 ` Ingo Schwarze
2022-06-26 17:29 ` Mohamed Akram [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=4F394515-B0B2-45F9-87D6-994D86A16223@outlook.com \
--to=mohd.akram@outlook.com \
--cc=discuss@mandoc.bsd.lv \
--cc=schwarze@usta.de \
/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).