From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] fmt(1) standard behaviour
Date: Mon, 19 Oct 2009 12:43:11 +0100 [thread overview]
Message-ID: <df49a7370910190443i2de349dcp60410caf46f7ec15@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00910181525q6d5cd8e0y4b4c401a60051aa7@mail.gmail.com>
the reason is that the algorithm is
simpler if fmt reads all the words and then
formats them.
if you could modify the source in a simple way to make it
incremental (for instance by flushing the words at
the end of each paragraph) i imagine the patch
might be accepted.
2009/10/18 Rudolf Sykora <rudolf.sykora@gmail.com>:
> I may not fully understand the problem, but wouldn't it be just fine
> if fmt output anything it can already output?
> I.e., filled lines are output, on encountering '\n' the (generally
> unfilled) line is output...
> (Or what is the reason that fmt waits for EOF?)
>
> R
next prev parent reply other threads:[~2009-10-19 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<fe41879c0910181300s3e1ba6efueda064db0b8a474@mail.gmail.com>
2009-10-18 21:33 ` erik quanstrom
2009-10-18 22:25 ` Rudolf Sykora
2009-10-19 11:43 ` roger peppe [this message]
2009-10-18 20:00 Akshat Kumar
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=df49a7370910190443i2de349dcp60410caf46f7ec15@mail.gmail.com \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.net \
/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).