From: ori@eigenstate.org
To: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] page epub support
Date: Mon, 16 Nov 2020 09:27:35 -0800 [thread overview]
Message-ID: <E060B0300CDB9ECFF7ED60AF35E625B4@eigenstate.org> (raw)
In-Reply-To: <0A56B70EFBA44C61E499C76EAFEBD15F@prosimetrum.com>
Quoth umbraticus@prosimetrum.com:
> With the flush, I only get the first (blank) page. I think I
> understand why the flush is there (to get each item as a separate read
> in the while(read){addpage} that follows), so I don't really
> understand why removing it makes things work...
This fix looks wrong.
It seems like we have a bug in our awk input buffering with
fflush:
cpu% echo `''{seq 10} | awk '{print $0; fflush}'
1
2
3
4
5
6
7
8
9
10
cpu% echo `''{seq 10} | awk '{print $0; fflush}'
1
The fix should be in awk.
next prev parent reply other threads:[~2020-11-16 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:31 umbraticus
2020-11-16 17:27 ` ori [this message]
2020-11-17 12:21 ` [9front] " qwx
2020-11-20 7:11 ` Anthony Martin
2020-11-20 8:28 ` umbraticus
2020-11-20 23:29 ` qwx
2020-11-20 15:43 ` ori
2020-11-17 2:42 ` sl
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=E060B0300CDB9ECFF7ED60AF35E625B4@eigenstate.org \
--to=ori@eigenstate.org \
--cc=umbraticus@prosimetrum.com \
/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).