Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: "Donal K. Fellows" <donal.k.fellows@xxxxxxxxx>
- Date: 30 Nov 2006 10:04:51 -0800
Jeff Hobbs wrote:
No, the lack of a std channels is particular to Windows gui subsystem
apps and OS X apps run from the Finder.
I've seen the equivalent on some Unix desktops (don't remember the
details of which) where the applications were being started with the
std channels being *closed* (and not redirected to/from /dev/null).
IIRC, Tcl doesn't deal well with this situation...
Donal.
.
- Follow-Ups:
- References:
- Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: WilliamKF
- Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: Stéphane A.
- Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: Fredderic
- Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: Kevin Kenny
- Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: Fredderic
- Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- From: Jeff Hobbs
- Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- Prev by Date: Re: full-screen window?
- Next by Date: my first Tck/Tk program... and an XML question
- Previous by thread: Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- Next by thread: Re: Error: channel "stdout" wasn't opened for writing when "exec >&@stdout printenv"
- Index(es):
Relevant Pages
|
|