From: Steffen Nurpmeso <sdaoden@yandex.com>
To: tech@mdocml.bsd.lv
Subject: Re: Nested list spacing issue
Date: Tue, 11 Nov 2014 11:49:22 +0100 [thread overview]
Message-ID: <20141111104922.duMfYE60%sdaoden@yandex.com> (raw)
In-Reply-To: <20141110220614.GD20056@iris.usta.de>
Hallo Ingo,
Ingo Schwarze <schwarze@usta.de> wrote:
|Hi Steffen,
|
|Steffen Nurpmeso wrote on Mon, Nov 10, 2014 at 08:03:18PM +0100:
|> forget about this, this is an issue with mawk(1) which doesn't
|[...]
|> Sorry for the noise.
|
|Well, i didn't look at the mawk(1) issue, but your bug report
Well _i_ think that if mawk(1) optimizes 'print >> NAME' by
creating some kind of file object but then if i use 'getline <
NAME' it should look wether it did so for NAME and fflush(3) that
cache automatically, since fflush("") isn't portable awk. But
even if, imho. Let's see what Thomas Dickey says.
|with respect to mandoc(1) is valid in any case, and i have fixed it.
|
|> I'm sure it's known
|
|This bug was not known, thanks for reporting.
Great this nudged for an audit that actually had some outcome.
Nonetheless way too hasty; still: all awks worked equally well in
first place, so i didn't even spend a thought on that a growth of
the manual page that was used for testing correlated with the
mawk(1) I/O buffer size and a missing automatic fflush("") and
finally resulted in a premature EOF of the mdoc(7) documented what
finally was presented to mandoc(1).
Ciao,
--steffen
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2014-11-11 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 17:40 Steffen Nurpmeso
2014-11-10 19:03 ` Steffen Nurpmeso
2014-11-10 22:06 ` Ingo Schwarze
2014-11-11 10:49 ` Steffen Nurpmeso [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=20141111104922.duMfYE60%sdaoden@yandex.com \
--to=sdaoden@yandex.com \
--cc=tech@mdocml.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).