discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Stephen Gregoratto <dev@sgregoratto.me>
Cc: discuss@mandoc.bsd.lv
Subject: Re: Assert fails when outputting mdoc -> man with EQN
Date: Sat, 15 Feb 2020 16:17:11 +0100	[thread overview]
Message-ID: <20200215151711.GB85600@athene.usta.de> (raw)
In-Reply-To: <20200215142807.xsiwplllqpp735yg@dextop.sgregoratto.me>

Hi Stephen,

Stephen Gregoratto wrote on Sun, Feb 16, 2020 at 01:28:07AM +1100:

> I recently forked a simple password generator[1] and converted some
> equations in the manpage[2] to eqn.

That's not a particularly good idea for such simple formulas.
It harms portability for little benefit.

> For some reason, converting from mdoc to man triggers an assertion

The reason is that eqn(7) and tbl(7) output modules simply do not exist.
Your eqn(7) code is parsed into an abstract syntax tree as usual,
and then that syntax tree would have to be converted back into eqn(7)
code embedded in the man(7) output, or - even more difficult - into
man(7) code proper.

Writing such eqn(7) and tbl(7) code generators would require a
non-trivial amount of work.  I added an entry to the TODO file, see
below.  But given that -T man is mostly needed for software that
wants to be unusually portable and given that using eqn(7) or tbl(7)
significantly restricts portability in the first place, this doesn't
feel like a particularly high-priority task.

Yours,
  Ingo


- -T man does not handle eqn(7) and tbl(7)
  Stephen Gregoratto 16 Feb 2020 01:28:07 +1100
  loc **  exist **  algo **  size ***  imp **
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

      reply	other threads:[~2020-02-15 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 14:28 Stephen Gregoratto
2020-02-15 15:17 ` Ingo Schwarze [this message]

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=20200215151711.GB85600@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=dev@sgregoratto.me \
    --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).