tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Baptiste Daroussin <bapt@freebsd.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: Naive patch for handling empty input
Date: Fri, 13 Oct 2023 13:05:19 +0200	[thread overview]
Message-ID: <ZSkkb9WDKI5s8wl8@asta-kit.de> (raw)
In-Reply-To: <m3dpbb2r53tgnzz2mtvck2kgqwer35kxnp4ehycvcgwyh5jjbt@u66ktrucl3db>

Hi Bapt,

Baptiste Daroussin wrote on Fri, Oct 13, 2023 at 12:22:09PM +0200:

> I was looking for compatibility with groff like you showed above, this
> is an "issue" a user reported, he was expecting to have an empty output
> if provided an empty input, but if the current behaviour is how you think
> mandoc should behave, I am fine with closing the report with work as
> intended.

It might be useful to ask the user first *why* they want that
particular behaviour, and how they think mandoc(1) should behave
without .TH or .Dd in general, and why they want specific behaviour
in such cases of degenerate input.

It is conceivable that maybe they have an interesting reason,
and knowing that reason might help to make mandoc better?
I'm not sure it will, but i'm not sure that possibility can be
excluded, either.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv


  reply	other threads:[~2023-10-13 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:30 Baptiste Daroussin
2023-10-13 10:13 ` Ingo Schwarze
2023-10-13 10:22   ` Baptiste Daroussin
2023-10-13 11:05     ` Ingo Schwarze [this message]
2023-10-13 11:22       ` Baptiste Daroussin
2023-10-13 11:52         ` 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=ZSkkb9WDKI5s8wl8@asta-kit.de \
    --to=schwarze@usta.de \
    --cc=bapt@freebsd.org \
    --cc=tech@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).