From: hugo rivera <uair00@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] sed oddity
Date: Tue, 18 Aug 2009 16:41:49 +0200 [thread overview]
Message-ID: <138575260908180741j56414d5dxcfa1fbc30a48bb3d@mail.gmail.com> (raw)
Hi,
is there some reason why sed doesn't check for write errors on its
stdout? (or at least it doesn't report them)
I am implementing a fs, and I wasted my whole afternoon trying to figure out why
sed 300q file > mnt/data
doesn't say anything about the write error I was expecting.
Note that
sed 300q file | cat > mnt/data
shows my error message ;-)
Am I missing something?
Saludos
--
Hugo
next reply other threads:[~2009-08-18 14:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 14:41 hugo rivera [this message]
2009-08-18 14:55 ` Uriel
2009-08-18 15:25 ` Gorka Guardiola
2009-08-18 16:00 ` roger peppe
2009-08-19 10:35 ` Uriel
2009-08-18 15:38 ` erik quanstrom
2009-08-19 7:47 ` hugo rivera
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=138575260908180741j56414d5dxcfa1fbc30a48bb3d@mail.gmail.com \
--to=uair00@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).