From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: tbl broken on \_/\= for spanned columns
Date: Mon, 17 Oct 2022 04:26:55 +0200 [thread overview]
Message-ID: <20221017022655.pmcjidqfqcuwz74s@tarta.nabijaczleweli.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
Hi!
-- >8 --
.Dd
.Dt STTY 1
.Os
.Sh DESCRIPTION
.TS
c s
l l .
\_
b c
.TE
-- >8 --
(reduced from a real table, as in I did actually run into this)
is rendered as such by mandoc 1.14.5-1 off Debian and CVS HEAD:
-- >8 --
STTY(1) General Commands Manual STTY(1)
DESCRIPTION
─
b c
Debian October 17, 2022 Debian
-- >8 --
and as such if you 9s/b/bBbBbB/:
-- >8 --
STTY(1) General Commands Manual STTY(1)
DESCRIPTION
──────
bBbBbB c
Debian October 17, 2022 Debian
-- >8 --
This is wrong: the cell that contains the line spans over both b and c.
Compare groff (1.22.4-6) with the correct render:
-- >8 --
DESCRIPTION
──────
b c
-- >8 --
and
-- >8 --
DESCRIPTION
───────────
bBbBbB c
-- >8 --
Best,
наб
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-10-17 2:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221017022655.pmcjidqfqcuwz74s@tarta.nabijaczleweli.xyz \
--to=nabijaczleweli@nabijaczleweli.xyz \
--cc=discuss@mandoc.bsd.lv \
/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).