From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@frontiernet.net>,
Ingo.Wilken@Informatik.Uni-Oldenburg.DE (Ingo Wilken),
zsh-workers@math.gatech.edu
Subject: Re: Completion bug introduced in 3.0.3
Date: Tue, 1 Jul 1997 23:10:18 -0700 [thread overview]
Message-ID: <970701231018.ZM8001@candle.brasslantern.com> (raw)
In-Reply-To: <199707020451.AAA10907@hzoli.home>
On Jul 2, 12:51am, Zoltan Hidvegi wrote:
} Subject: Re: Completion bug introduced in 3.0.3
}
} > Another thing: I use a TCL script that sets its stdout stream to
} > non-blocking. This somehow affects zsh, as all interactive commands
} > started after the TCL script (like "ftp" or "more") immediately terminate
I meant to mention this before ...
It's an extremely bad idea for any program to set a tty device for non-
blocking I/O. This doesn't "somehow affect zsh," it affects the modes
of the file descriptor associated with the tty; which happens to be a
dup of the one zsh continues using for future processes, and therefore
it affects those processes as well.
I don't know why bash and tcsh don't show the problem -- either they are
explicitly resetting the blocking state, or they are using a different
scheme for setting up the stdin/out/err descriptors when they create
children. (It's possible that they're using /dev/fd/ or /proc/$$/fd/
rather than dup().)
I don't think ttyctl -f is going to have any effect on this, because the
non-blocking I/O ioctl isn't one that's done through the tty driver
structures; a quick grep through the zsh sources doesn't reveal any
likely-looking calls.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1997-07-02 6:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-02 3:48 Ingo Wilken
1997-07-02 4:41 ` Geoff Wing
1997-07-02 5:43 ` Bart Schaefer
1997-07-02 4:51 ` Zoltan Hidvegi
1997-07-02 6:10 ` Bart Schaefer [this message]
1997-07-02 6:55 ` Zoltan Hidvegi
1997-07-04 0:53 ` Ingo Wilken
1997-07-02 5:12 ` Bart Schaefer
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=970701231018.ZM8001@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=Ingo.Wilken@Informatik.Uni-Oldenburg.DE \
--cc=hzoli@frontiernet.net \
--cc=zsh-workers@math.gatech.edu \
/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).