discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jan Stary <hans@stare.cz>
To: discuss@mandoc.bsd.lv
Cc: Ingo Schwarze <schwarze@usta.de>
Subject: Re: .Bl -tag -width ".mdoc macro" not recognised sometimes(?)
Date: Sun, 5 Jun 2022 22:48:05 +0200	[thread overview]
Message-ID: <Yp0WheGU2kqJReNS@www.stare.cz> (raw)
In-Reply-To: <20220605201637.yaxcaveqsyf7da4d@tarta.nabijaczleweli.xyz>

> > In general, if a feature is used in important, widely used manual
> > pages, that raises the priority of supporting it - even though in
> > this case, admittedly, even a very high priority would help little
> > to overcome the significant difficulty of implementing it.
> 
> Not that it's the be-all end-all, but DCS[1] says:
>   116 files grepped (95 results)
> (if you filter by src:groff, that accounts for
>  65 files grepped (65 results))
> this includes mandoc:
> -- >8 --
> mdocml_1.14.6-1/TODO
> 
> - When the -width string contains macros, the macros must be rendered
>   before measuring the width, for example
>     .Bl -tag -width ".Dv message"
>   in magic(5), located in src/usr.bin/file, is the same
>   as -width 7n, not -width 11n.
> -- >8 --
> continuing from CVS:
> -- >8 --
>   The same applies to .Bl -column column widths;
>   reported again by Nicolas Joly Thu, 1 Mar 2012 13:41:26 +0100 via wiz@ 5 Mar
>   reported again by Franco Fichtner Fri, 27 Sep 2013 21:02:28 +0200
>   reported again by Bruce Evans Fri, 17 Feb 2017 21:22:44 +0100 via bapt@
>   loc ***  exist ***  algo ***  size **  imp ***
> -- >8 --
> 
> There's also one result for
>   -column ".
> from manpages-l10n.
> 
> Most of them are relatively simple:
>   .Cm restrict_loggedin_tty Ns = Ns Ar ttyglob*
>   .Ev DNSDB_API_KEY , APIKEY
>   .Fl bullet
> this affects them, but, well, not much (45/30, 26/21, 10/7, respectively),
> my 59/13 is, decidedly, a 3.26-fold edge-case.
> 
> I'd say that the shorthand assessment from the TODO and yours, above,
> are unfortunately accurate.
> 
> [1]: https://codesearch.debian.net/search?q=-width+%22.&literal=1

For comparison, in OpenBSD's /usr/share/man,
the only use is the self-referencing roff(7).

/usr/share/man/man1/indent.1:.Bl -tag -width "./.indent.pro" -compact
/usr/share/man/man1/make.1:.Bl -tag -width ".ARCHIVE"
/usr/share/man/man1/make.1:.Bl -tag -width ".ARCHIVE"
/usr/share/man/man1/make.1:.Bl -tag -width ".NOTPARALLEL"
/usr/share/man/man1/make.1:.Bl -tag -width ".NOTPARALLEL"
/usr/share/man/man1/make.1:.Bl -tag -width ".PRECIOUS"
/usr/share/man/man5/elf.5:.Bl -tag -width ".shstrtab"
/usr/share/man/man7/roff.7:.Bl -tag -width ".Bl -tag -width 2i" -offset indent -compact
/usr/share/man/man8/restore.8:.Bl -tag -width "./restoresymtable" -compact
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2022-06-05 20:48 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   ` наб
2022-06-05 19:43     ` Ingo Schwarze
2022-06-05 20:16       ` наб
2022-06-05 20:48         ` Jan Stary [this message]
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=Yp0WheGU2kqJReNS@www.stare.cz \
    --to=hans@stare.cz \
    --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).