From: David Kastrup <dak@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs Environment Variables
Date: Wed, 28 Nov 2007 19:06:11 +0100 [thread overview]
Message-ID: <85mysy8cto.fsf@lola.goethe.zz> (raw)
In-Reply-To: o2fr6iaxqht.fsf@hasgksssven.desy.de
Sven Utcke <utcke+news@informatik.uni-hamburg.de> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Peter Dyballa <Peter_Dyballa@Web.DE> writes:
>
>> > How often do you need to separate stdout and stderr in some shell?
>>
>> Huh?
>>
>> dd if=something of=something 2>>logfile | tar xf -
>
> So what?
>
> (dd if=something of=something | tar xf - ) >& logfile
Depends on tar not outputting anything...
>> Stuff like that is completely common for scripting. Or even just
>>
>> echo "This is an error." >&2
>
> echo "This is an error." > /dev/stderr
Unportable even between tcsh and tcsh since it relies on the existence
of a non-standard device.
>> You know, there is a reason that both stdout and stderr exist.
>
> Yes, and tcsh doesn't handle this too well. But just like Peter I'm
> bitten by this _much_ more rarely than by the absence of a "find last
> command starting with" functionality in Bash...
C-r works pretty well here.
> Maybe our usage-patterns are different?
More likely our understanding of the context. I tell people that csh
sucks for scripting, and they tell me that I am wrong since they don't
care about scripting.
Somewhat surreal.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2007-11-28 18:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 13:43 Emacs Environment Variables Phi
2007-11-23 21:09 ` Barry Margolin
2007-11-24 9:34 ` Peter Dyballa
2007-11-24 12:48 ` Ismael Valladolid Torres
2007-11-24 13:38 ` Peter Dyballa
2007-11-24 14:02 ` Ismael Valladolid Torres
[not found] ` <mailman.4026.1195912966.18990.help-gnu-emacs@gnu.org>
2007-11-24 16:41 ` David Kastrup
2007-11-25 6:25 ` Tim X
2007-11-25 9:06 ` David Kastrup
[not found] ` <mailman.4025.1195911521.18990.help-gnu-emacs@gnu.org>
2007-11-24 13:45 ` Phi
2007-11-25 6:18 ` Tim X
2007-11-25 10:18 ` Peter Dyballa
[not found] ` <mailman.4054.1195985894.18990.help-gnu-emacs@gnu.org>
2007-11-25 10:44 ` David Kastrup
2007-11-25 11:36 ` Harald Hanche-Olsen
2007-11-25 13:25 ` Peter Dyballa
[not found] ` <mailman.4059.1195997121.18990.help-gnu-emacs@gnu.org>
2007-11-25 13:55 ` David Kastrup
2007-11-25 14:54 ` Peter Dyballa
2007-11-25 15:19 ` David Kastrup
2007-11-25 15:50 ` Peter Dyballa
[not found] ` <mailman.4071.1196004563.18990.help-gnu-emacs@gnu.org>
2007-11-28 16:51 ` Sven Utcke
2007-11-28 18:06 ` David Kastrup [this message]
2007-11-30 12:25 ` Sven Utcke
2007-11-30 11:46 ` Johan Bockgård
2007-11-30 12:28 ` Sven Utcke
2007-11-30 13:32 ` Johan Bockgård
2007-11-30 15:17 ` Peter Dyballa
2007-12-03 10:17 ` Sven Utcke
[not found] ` <mailman.4354.1196435852.18990.help-gnu-emacs@gnu.org>
2007-12-03 10:20 ` Sven Utcke
2007-11-28 16:43 ` Sven Utcke
2007-12-01 10:54 ` Peter Dyballa
2007-11-25 13:25 ` Peter Dyballa
2007-11-27 8:03 ` Tim X
2007-11-27 10:00 ` Peter Dyballa
[not found] ` <mailman.4168.1196157656.18990.help-gnu-emacs@gnu.org>
2007-11-27 10:28 ` David Kastrup
2007-11-27 16:27 ` Joel J. Adamson
2007-11-28 9:02 ` Tim X
2007-12-23 2:01 ` David Combs
2007-11-28 8:55 ` Tim X
[not found] ` <mailman.4022.1195908516.18990.help-gnu-emacs@gnu.org>
2007-11-25 6:02 ` Tim X
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85mysy8cto.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).