From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: precmd: write error: interrupted
Date: Thu, 25 Apr 2013 11:27:11 -0700 [thread overview]
Message-ID: <130425112711.ZM17317@torch.brasslantern.com> (raw)
In-Reply-To: <klbq25$osh$1@ger.gmane.org>
On Apr 25, 7:44pm, Yuri D'Elia wrote:
}
} On 04/25/2013 06:47 PM, Yuri D'Elia wrote:
} > 2) Why "precmd() { { print "HELLO" } >&- 2>&-; } doesn't suppress the
} > error in this case?
}
} Closest analogue I could find is:
}
} % { { print >&2 } 2>&- } 2>/dev/null
} zsh: write error
Of course what's happening here is in outside-in order. Starting with
the stuff you can mostly see:
1. stderr is redirected to /dev/null (old stderr is saved)
2. stderr is closed (at this point the outer redirection is gone)
3. print generates an error
Now the stuff you can't see happens:
4. zsh gets another error writing to the closed stderr
5. zsh warns about that to the saved stderr from step 1
You avoid the whole mess if you never close stderr, or if you close it
before step 1 (e.g. by "exec 2>&-"), though the latter is impractical
in the case we're discussing.
next prev parent reply other threads:[~2013-04-25 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 16:47 Yuri D'Elia
2013-04-25 17:44 ` Yuri D'Elia
2013-04-25 18:27 ` Bart Schaefer [this message]
2013-04-25 18:16 ` Bart Schaefer
2013-04-25 18:38 ` Peter Stephenson
2013-04-25 22:18 ` Bart Schaefer
2013-04-26 0:52 ` Bart Schaefer
2013-04-25 19:38 ` Yuri D'Elia
2013-04-26 0:53 ` Bart Schaefer
2013-04-25 20:05 ` Yuri D'Elia
2013-04-25 20:58 ` Yuri D'Elia
2013-04-26 15:08 ` Bart Schaefer
[not found] ` <130426080805.ZM18619__18102.73175729$1366989065$gmane$org@torch.brasslantern.com>
2013-04-26 17:59 ` Yuri D'Elia
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=130425112711.ZM17317@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).