From: "Dwight Shih" <d.shih@rightbox.com>
To: zsh-workers@sunsite.dk
Subject: Bang completion kills zsh in emacs process buffer
Date: Fri, 19 Sep 2003 10:38:19 -0500 [thread overview]
Message-ID: <20030919153819.57F1878F31@smtp.us2.messagingengine.com> (raw)
I understand why the bug occurs, but it's been 4 or 5 years since I've
been inside the zsh code and I'm unclear on the best way to correct the
problem.
Here's the environment:
Mac OS X 10.2.6
zsh-4.1.1
emacs 21.3.50
My emacs was built from CVS sources on 17 August, as the Mac OS X
windows
support not yet available in an official distribution. However, it looks
like this could happen in any version of emacs running with native
windows support.
To reproduce:
start emacs
M-x shell #if necessary M-x customize-variable
explicit-shell-file-name to zsh binary
$ pwd
$ echo !$ #zsh will now die
In the debugger, zsh dies at hist.c:1092 trying to do a zputs(prt,shout)
because the file pointer shout is null.
As best I can tell, shout is normally initialized in init_shout, called
from init_io at init.c:452. Walking through init_io, SHTTY never gets
opened because the shell doesn't seem to be running in a tty (I would
expect this to be true in any windowed emacs). So when it comes time to
call init_shout, we conclude that since we're not using a tty, we're not
going to need shout.
I would appreciate it if someone who understood the logic behind
interactive and non-interactive shells and the file pointers involved
would take a look and tell me whether it's better to always set shout in
init_io (either by direct assignment to stdout or dup) or test for
shout==null in hist.c
Thanks,
Dwight Shih
next reply other threads:[~2003-09-19 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 15:38 Dwight Shih [this message]
2003-09-19 16:18 ` Peter Stephenson
2003-09-19 17:02 ` Dwight Shih
2003-09-19 17:19 ` Peter Stephenson
[not found] <20030919175443.B24767835C@smtp.us2.messagingengine.com>
2003-09-19 18:19 ` 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=20030919153819.57F1878F31@smtp.us2.messagingengine.com \
--to=d.shih@rightbox.com \
--cc=zsh-workers@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).