From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fmt(1) standard behaviour
Date: Sun, 18 Oct 2009 17:33:53 -0400 [thread overview]
Message-ID: <aa94b99dd5c8340b9625597e062fcb3b@ladd.quanstro.net> (raw)
In-Reply-To: <<fe41879c0910181300s3e1ba6efueda064db0b8a474@mail.gmail.com>>
> it never actually formats any lines. If, on the other hand, while
> formatting on stdin, fmt(1) formatted on a line-by-line basis (per
> '\n'), then its use (at least for me) could be greatly widened.
i don't think this will help. unless you multithread fmt (seems silly),
you're going to have the input or output blocking problem. you
can imagine an arbitrarly long line choking your proposed setup,
as you can imagine that outputting on '\n' to confuse you if you
expect output after every line.
- erik
next parent reply other threads:[~2009-10-18 21:33 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 [this message]
2009-10-18 22:25 ` Rudolf Sykora
2009-10-19 11:43 ` roger peppe
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=aa94b99dd5c8340b9625597e062fcb3b@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).