zsh-users
 help / color / mirror / code / Atom feed
From: Meino Christian Cramer <Meino.Cramer@gmx.de>
To: zsh-users@sunsite.dk
Subject: coproc eperiments
Date: Fri, 29 Jul 2005 19:23:45 +0200 (CEST)	[thread overview]
Message-ID: <20050729.192345.41642707.Meino.Cramer@gmx.de> (raw)

Hi,

 I am currenlty experimenting with the coproc command.

 If I am doing the "hello world"-version of coproc:

	coproc bc
	noglob echo 3*6 >&p
	read a <&p; echo $a

 Everthing is working fine.

 But if I am doing:

	coproc bc
	rxvt zsh &

	( and then in the new shell
	noglob echo 3*6 >&p
	Bad file descriptor

 As I think to know (*VERY* carefully) beside other things the
 filedescriptors of a parent process are inherited to the child
 process.

 Why is the zsh started by rxvt started by the first zsh not able to
 use &>p ?

 keep zshing!
 Meino

	


             reply	other threads:[~2005-07-29 17:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 17:23 Meino Christian Cramer [this message]
2005-08-03  7:53 ` Peter Stephenson

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=20050729.192345.41642707.Meino.Cramer@gmx.de \
    --to=meino.cramer@gmx.de \
    --cc=zsh-users@sunsite.dk \
    /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).