discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: наб <nabijaczleweli@nabijaczleweli.xyz>
To: discuss@mandoc.bsd.lv
Subject: Re: .Bl -tag -width ".mdoc macro" not recognised sometimes(?)
Date: Sun, 5 Jun 2022 20:28:24 +0200	[thread overview]
Message-ID: <20220605182824.xlnxr4tfb63yuddi@tarta.nabijaczleweli.xyz> (raw)
In-Reply-To: <YpzuG2Nld7nqMwmI@www.stare.cz>

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

On Sun, Jun 05, 2022 at 07:55:39PM +0200, Jan Stary wrote:
> On Jun 05 18:16:35, nabijaczleweli@nabijaczleweli.xyz wrote:
> Quoting mdoc(7):
> 
> 	The -width and -offset arguments accept
> 	macro names as described for Bd -offset,
> 	scaling widths as described in roff(7),
> 	or use the length of the given string.
> 
> Is your -width a macro name (such as Ds) as descibed for -offset? No.
> Is it a scalinbg width as described in roff(7)? No.
> Apparently, mandoc uses the length of the given string then.
> AFAICT, that's what you told it to do.

Ah, yeah, that's fair; this is, apparently, a groffism:
  If ⟨string⟩ starts with a ‘.’ (dot) immediately followed by a valid
  -mdoc macro name, interpret ⟨string⟩ and use the width of the result.
  Almost all lists in this document use this option.

My b.

> Also, mandoc -Tlint please.

-Tlint is clean, save for the empty date and long lines.

Best,
наб

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

  reply	other threads:[~2022-06-05 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 16:16 наб
2022-06-05 17:55 ` Jan Stary
2022-06-05 18:28   ` наб [this message]
2022-06-05 19:43     ` Ingo Schwarze
2022-06-05 20:16       ` наб
2022-06-05 20:48         ` Jan Stary
2022-06-06 10:08         ` Ingo Schwarze

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=20220605182824.xlnxr4tfb63yuddi@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).