From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-mailinglist@schneiderp.de,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Redirection to stderr
Date: Mon, 10 Jul 2017 10:33:00 -0000 [thread overview]
Message-ID: <b4de479d-882e-4e61-2916-1b54f318d76c@gmail.com> (raw)
In-Reply-To: <baa3a4f84968dd6aa9869d2c9f58197f.squirrel@mail.schneiderp.de>
On 10/07/2017 11:06, cygwin-mailinglist wrote:
> Hi Marco,
>
> thanks for your reply. I'm mailing you personally because at first I only
> subscribed to the mailing list digest (so I didn't receive your response
> directly) and cannot or don't know yet how to reply to your mail to the
> list which I only see in the web archive.--
reply to both.
> As to your question: The redundant redirection of "stderr to itself"
> appears in the context of a larger system of scripts which permit
> configuring the destination of the redirection. The original reads
> something like ''2> "$STDERR_TARGET"''. The elegance is that I can
> configure where diagnostic output goes by simply setting an environment
> variable. The scripts simply use whatever "file system location" (possibly
> /dev/stderr) is configured.
>
> Rationale aside, it is a bug, isn't it?
I guess a side effect of a lost race.
Redirecting something on itself it is not guarantee to work.
> Peter
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next parent reply other threads:[~2017-07-10 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <baa3a4f84968dd6aa9869d2c9f58197f.squirrel@mail.schneiderp.de>
2017-07-10 10:33 ` Marco Atzeri [this message]
2017-07-10 12:02 ` cygwin-mailinglist
2017-07-10 13:05 ` Andrey Repin
2017-07-10 13:41 ` Peter Schneider
2017-07-10 16:32 ` Eliot Moss
2017-07-10 18:43 ` Hans-Bernhard Bröker
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=b4de479d-882e-4e61-2916-1b54f318d76c@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-mailinglist@schneiderp.de \
--cc=cygwin@cygwin.com \
/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).