From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Dan Jacobson <jidanni@dman.ddts.net>,
arafune@debian.org, emacs-devel@gnu.org
Subject: Re: FAQ: gnuplot vs. emacs' compile command
Date: 12 Feb 2004 14:34:11 -0500 [thread overview]
Message-ID: <jwv3c9g857c.fsf-monnier+emacs/devel@asado.iro.umontreal.ca> (raw)
In-Reply-To: <m3fzdgl5n7.fsf@kfs-l.imdomain.dk>
> Did anyone actually look at this bug back in May ?
> FYI, I have included the text at the referenced link here.
What is the bug exactly?
My understanding is of the problem:
when Emacs exits, gnuplot is killed because its stdout is connected to
Emacs (i.e. it receives a SIGPIPE or SIGHUP or somesuch).
Stefan
> Dan Jacobson <jidanni@dman.ddts.net> writes:
>> Fellas, the gnuplot team may have found ugly emacs process bugs, see
>> <...>
>>
> : Dan Jacobson <jidanni@dman.ddts.net> wrote:
> :
> : > Using emacs -eval '(compile "make")'
> : > With: echo "plot 'file';pause -1"|gnuplot -persist
> : > just flashes the graph for a split second.
> :
> : So let's get into dissecting this further. The first candidate to
> : remove is 'make'. It doesn't really do anything useful in this whole
> : setup, so we might as well get rid of it. Let's replace it by a shell
> : script doing the same things. And while at it, let's get rid of the
> : separate data file, too:
> :
> : --- gpaction ---
> : gnuplot -persist <<EOS
> : plot '-'
> : 1 1
> : 2 2
> : e
> : EOS
> : ---- end ---
> :
> : sh gpaction # does the plot and returns
> : emacs -eval '(compile "sh gpaction")' # doesn't plot, but returns
> : emacs -eval '(shell-command "sh gpaction")' # plot, but no return
> :
> : For the latter, emacs is unresponsive --- it's obviously waiting for
> : something to happen, which doesn't. Only after you terminate the
> : gnuplot graph window (key 'q' into it), or press Ctrl-G in emacs to
> : forcibly break out of the wait loop, it will continue.
> :
> : During that pause, look at the output from 'ps jx' and you'll find
> : that gnuplot_x11 is an orphan --- i.e. it's the only surviving process
> : in its process group. In "shell-command", emacs apparently doesn't
> : kill it, whereas in "compile", it probably does.
> : --
> : Hans-Bernhard Broeker (broeker@physik.rwth-aachen.de)
> : Even if all the snow were burnt, ashes would remain.
> --
> Kim F. Storm http://www.cua.dk
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2004-02-12 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871xz7jrk0.fsf@jidanni.org>
[not found] ` <87d6iqhz62.fsf@jidanni.org>
[not found] ` <87addrv76t.fsf@jidanni.org>
2004-02-12 14:43 ` FAQ: gnuplot vs. emacs' compile command Kim F. Storm
2004-02-12 19:34 ` Stefan Monnier [this message]
2004-02-12 22:47 ` Kim F. Storm
2004-02-13 0:05 ` Dan Jacobson
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=jwv3c9g857c.fsf-monnier+emacs/devel@asado.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
--cc=arafune@debian.org \
--cc=emacs-devel@gnu.org \
--cc=jidanni@dman.ddts.net \
/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).