From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hget
Date: Mon, 29 Mar 2004 22:36:02 +0100 [thread overview]
Message-ID: <94907f663aa077b5526b10a39a34ecda@vitanuova.com> (raw)
In-Reply-To: <7a4a127e36d445afb8476a59d48819d6@terzarima.net>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
i think output duplication is more dangerous than output truncation.
the latter can be determined from the error status anyway, which the
former cannot.
hence my preference for an option that will explicitly allow seeking
on output, rather than one which will suppress it.
[-- Attachment #2: Type: message/rfc822, Size: 1943 bytes --]
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hget
Date: Mon, 29 Mar 2004 23:23:16 +0100
Message-ID: <7a4a127e36d445afb8476a59d48819d6@terzarima.net>
if you're anxious, perhaps it might be reasonable to provide an
option (say -e if it's not used) that tells hget not to produce
output until it is error-free (or at an end, -e works either way).
i actually have got another idea but it's more involved,
and probably not worthwhile for this case.
next prev parent reply other threads:[~2004-03-29 21:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 0:58 [9fans] rio and acme scrolling Micah Stetson
2004-03-27 1:51 ` Russ Cox
2004-03-27 5:07 ` Micah Stetson
2004-03-27 15:01 ` David Presotto
2004-03-27 15:07 ` Sape Mullender
2004-03-27 15:12 ` David Presotto
2004-03-27 20:58 ` Derek Fawcus
2004-03-27 15:22 ` Richard Miller
2004-03-27 15:36 ` Sape Mullender
2004-03-27 15:38 ` David Presotto
2004-03-27 15:38 ` Russ Cox
2004-03-27 17:03 ` Richard Miller
2004-03-27 16:07 ` andrey mirtchovski
2004-03-27 20:11 ` Micah Stetson
2004-03-27 20:45 ` thinkpads (was Re: [9fans] rio and acme scrolling) Axel Belinfante
2004-03-28 11:07 ` [9fans] rio and acme scrolling matt
2004-03-29 15:18 ` splite
2004-03-27 20:27 ` Micah Stetson
2004-03-27 23:57 ` Micah Stetson
2004-03-27 3:14 ` jmk
2004-03-27 10:21 ` a
2004-03-27 10:50 ` Dave Lukes
2004-03-29 13:41 ` blstuart
2004-03-29 14:33 ` Russ Cox
2004-03-29 14:36 ` matt
2004-03-29 15:57 ` Axel Belinfante
2004-03-29 17:31 ` Axel Belinfante
2004-03-29 18:42 ` [9fans] hget rog
2004-03-29 19:50 ` Russ Cox
2004-03-29 20:12 ` rog
2004-03-29 20:16 ` Russ Cox
2004-03-29 20:40 ` rog
2004-03-29 20:42 ` Russ Cox
2004-03-29 21:12 ` rog
2004-03-29 22:23 ` Charles Forsyth
2004-03-29 21:36 ` rog [this message]
2004-03-29 23:39 ` Charles Forsyth
2004-03-29 22:48 ` rog
2004-03-29 21:46 ` boyd, rounin
2004-03-29 23:01 ` rog
2004-03-29 22:17 ` boyd, rounin
2004-03-29 23:34 ` rog
2004-03-29 22:49 ` boyd, rounin
2004-03-30 10:19 ` Steve Simon
2004-03-30 0:02 ` Charles Forsyth
2004-03-29 23:22 ` rog
2004-03-29 19:58 ` David Tolpin
2004-03-29 20:08 ` David Tolpin
2004-03-29 20:18 ` rog
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=94907f663aa077b5526b10a39a34ecda@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/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).