help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: %B/%T outside Rs isn't Parsed: groff mismatch
Date: Thu, 13 Oct 2022 00:08:24 +0200	[thread overview]
Message-ID: <20221012220824.hhqgvlci4x74k3qc@tarta.nabijaczleweli.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]


-- >8 --
.Dt STTY 1
.%B Seventh Edition Ns -style
-- >8 --
-- >8 --
     S\b_e\b_v\b_e\b_n\b_t\b_h\b_ E\b_d\b_i\b_t\b_i\b_o\b_n\b_-style
-- >8 --
on groff, but
-- >8 --
STTY(1)                     General Commands Manual                    STTY(1)

     _\bS_\be_\bv_\be_\bn_\bt_\bh _\bE_\bd_\bi_\bt_\bi_\bo_\bn _\bN_\bs _\b-_\bs_\bt_\by_\bl_\be

Linux 5.10.0-17-amd64                                    Linux 5.10.0-17-amd64
-- >8 --
on mandoc (CVS HEAD and 1.14.5-1 off Debian).

mdoc(7), In-line says:
  Macro   Callable   Parsed   Arguments
  %B      No         No       >0
so while I think this accurately reflects mandoc behaviour,
that's incompatible with groff.

In /usr/share/groff/1.22.4/tmac/doc.tmac I see, simplified:
  .de %B
  .ie \n[doc-is-reference] \{\
  .el \{\
  .nop \*[doc-Em-font]\c
and likewise for %T: they are Parsed.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2022-10-12 22:08 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221012220824.hhqgvlci4x74k3qc@tarta.nabijaczleweli.xyz \
    --to=nabijaczleweli@nabijaczleweli.xyz \
    --cc=discuss@mandoc.bsd.lv \


* 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).