From: Robert Andersson <robert@gslt.hum.gu.se>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: comint-run can't send signals to subjob
Date: Thu, 7 Nov 2002 18:36:41 +0100 [thread overview]
Message-ID: <15818.42153.818972.577133@mozart.gslt.hum.gu.se> (raw)
In-Reply-To: <E189oHP-0007xG-00@fencepost.gnu.org>
>>>>> "RS" == Richard Stallman <rms@gnu.org> writes:
RS> when running a programme in comint-run it will not accept any signals
RS> from this buffer,
RS> I am not sure what it means to "accept signals from a buffer". But
RS> rather than explain it, please send a precise test case. That will
RS> show us more precisely than any amount of description.
RS> Please read the Bugs section in the Emacs manual, which provides
RS> guidelines on how to write a bug report to give us the
RS> necessary information so we can fix the bug.
k, i read the section on understanding bug reporting. thanks. i see
now that my explaination was a tad vague.
the program that i run with comin-run does of course accept signals,
it's comint-run that doesn't send any to the program, eg
M-x comint-run RET swi RET
to start swi prolog (yes this example only works if you got swi
installed and in your PATH maybe a new ispell could do as well???),
then i want to do
C-c C-c
that is, comint-interrupt-subjob to send the swi programme an INT
signal. It does not work on emacs version 21.1.1 or 20.7 running on
solaris 9, though on a solaris 8 box i does using the same emacs
binaries.
in my example above, how do i know that it is not swi that rejects
signals? well i can send it a signal from any tty on the same system
with something like
kill -INT swi-pid
which will work.
actually none of the comint-signals seem to work.
i got an answer from usenet saying that they have had the same problem
with hpux 11... though in this i will not speculate.
i think this was a tad more elaborative don't you think so?
RS> In file included from /usr/openwin/include/X11/Xos.h:79,
RS> from xfaces.c:279:
RS> /usr/include/strings.h:25: conflicting types for `memmove'
RS> /usr/include/iso/string_iso.h:62: previous declaration of `memmove'
RS> /usr/include/strings.h:26: parse error before `0'
RS> /usr/include/strings.h:26: warning: conflicting types for built-in function `memset'
RS> Would you please try the latest pretest and see if it compiles? If it
RS> does not, I hope you will tell us what change is needed to make it
RS> compile. Only a Solaris user can tell us how to fix this problem.
uhm, i can do prolog... i am terrible at c :)
yours,
/robert
--
Systems Administrator
Swedish National Graduate School of Language Technology
prev parent reply other threads:[~2002-11-07 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 18:49 comint-run can't send signals to subjob Robert Andersson
2002-11-07 15:09 ` Richard Stallman
2002-11-07 17:36 ` Robert Andersson [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15818.42153.818972.577133@mozart.gslt.hum.gu.se \
--to=robert@gslt.hum.gu.se \
--cc=bug-gnu-emacs@gnu.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).