discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jan Stary <hans@stare.cz>
To: discuss@mdocml.bsd.lv
Subject: Re: makewhatis stuck on groffer.1
Date: Mon, 22 Apr 2019 10:32:26 +0200	[thread overview]
Message-ID: <20190422083226.GA36008@www.stare.cz> (raw)
In-Reply-To: <20190421230359.GD31325@athene.usta.de>

Hi Ingo,

> Jan Stary wrote on Sat, Apr 20, 2019 at 08:21:45PM +0200:
> Wow, that ancient version of groffer.1 can barely be called a manual
> page.  It is low-level groff all over the place.  More than 600 lines
> of low-level groff code (macro definitions) in a single manual page...
> That's insane.
> Actually, insanity was to be expected, given that it was written
> by Bernd Warken.  But i wouldn't have expected it to be *that* bad.
> 
> Here is a minimal example of the specific issue you are reporting:
> 
>    $ echo '.while n .break' | mandoc -Tlint | head -n 1
>   mandoc: <stdin>:1:10: UNSUPP: unsupported roff request: break
>    $ echo '.while n .break' | mandoc
>   [endless loop]
> 
> The commit below fixes the endless loop.

thank you, it works now.

> There appear to be a few more issues with that manual page that i'm
> currently looking at.

Yeah, it _is_ insane. AFAICS, it is the only manpage that defines

	.de author
	This file was written by
	.MTO "" "Bernd Warken" .

for example, which gets rendered as

	AUTHOR
	       This file was written by


Jan
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2019-04-22  8:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 18:16 makewhatis stuck on groff.1 Jan Stary
2019-04-20 18:18 ` makewhatis stuck on groffer.1 Jan Stary
2019-04-20 18:21   ` Jan Stary
2019-04-21 23:03     ` Ingo Schwarze
2019-04-22  8:32       ` Jan Stary [this message]
2019-04-23 12:01         ` 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=20190422083226.GA36008@www.stare.cz \
    --to=hans@stare.cz \
    --cc=discuss@mandoc.bsd.lv \
    --cc=discuss@mdocml.bsd.lv \
    --subject='Re: makewhatis stuck on groffer.1' \
    /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

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