From: Magnus Homann <d0asta@dtek.chalmers.se>
To: rc@hawkwind.utcs.toronto.edu
Subject: rc and Emacs 19.10
Date: Sun, 30 May 1993 19:07:47 -0400 [thread overview]
Message-ID: <9305302307.AA11342@hackes.dtek.chalmers.se> (raw)
The new emacs doesn't work very well with rc. If you use it in
vt100-mode, it just hangs when you press any key. It(emacs) repeatedly
tries to read() stdin, but read() returns "I/O error". This happens in
a signalhandler called on SIGIO. The same goes for sh. Tcsh and csh on
the other hand, manage emacs without problems.
I think it's related to the different ways the shell spawn children.
Unfortunately I don't know where to start looking. Is there anyone who
might have a clue? I tried rc and then emacs from gdb, and then it
worked!!!
I'm sorry I don't tell you all the details, but that's because I don't
understand what's happening :-)
BTW, I'm on SunOS 4.1.3...
Homann
--
Magnus Homann "Just once, I want to hear you scream in pain."
d0asta@dtek.chalmers.se "Play some Rap Music." -- The Last Boyscout
reply other threads:[~1993-05-30 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9305302307.AA11342@hackes.dtek.chalmers.se \
--to=d0asta@dtek.chalmers.se \
--cc=rc@hawkwind.utcs.toronto.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.
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).