From: Mingye Wang <firstname.lastname@example.org>
Subject: Re: No/broken handling of backspaces in the source?
Date: Fri, 23 Sep 2022 09:39:54 +0800 [thread overview]
Message-ID: <CAD66C+aRx3Yi_qrO4RcKEETh1o6rSc6M3D+U963MJKAkYPpRTw@mail.gmail.com> (raw)
> It's unclear to me if this is supposed to happen, but I didn't see it in
> the TODO, so.
I believe this is intended behavior for mandoc, at least with regard
to terminal output. Consult the "ASCII Output" and "Locale Output"
sections of mandoc(1), and you shall see:
>Font styles are applied by using back-spaced encoding such that [...] > This markup is typically converted to appropriate terminal
> sequences by the pager or ul(1). To remove the markup, pipe the
> output to col(1) -b instead.
In other words, mandoc output is not for direct consumption by the
terminal. Try using `-T html` instead -- that should tell you whether
mandoc has really interpreted the thing.
To unsubscribe send an email to email@example.com
prev parent reply other threads:[~2022-09-23 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 17:03 наб
2022-09-23 1:39 ` Mingye Wang [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).