unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hans-Bernhard Broeker <broeker@physik.rwth-aachen.de>
Cc: emacs-devel@gnu.org
Subject: Re: gnuplot vs. emacs' compile command
Date: Mon, 26 May 2003 11:06:26 +0200 (MET DST)	[thread overview]
Message-ID: <Pine.OSF.4.44.0305261048390.13660-100000@acaxp6.physik.rwth-aachen.de> (raw)
In-Reply-To: <E19JiIs-0007fP-I5@fencepost.gnu.org>

On Sat, 24 May 2003, Richard Stallman wrote:

> It is not so bad as all that.  Many things in Emacs can loop, and people
> need to know about C-g.

Right.  But even so, a visible reminder might be helpful.  Since Emacs
won't react to _any_ user input except C-g in this situation, I think it
should announce this fact in a minibuffer message.

> That doesn't mean there is no room for improvement here.  Perhaps Emacs
> should use a different criterion.  But I am not sure what it should be.
> (Currently it waits for all writers to close the pipe, and then for
> termination of the original process.)

The criterion is fine, as far as I'm concerned.  At least gnuplot can be
taught to live with it.

What I'm less sure about is whether the wait loop for this subshell should
affect all the rest of Emacs, too.  At the moment, it blocks all user
interaction until the external process is finished, or C-g is pressed.

-- 
Hans-Bernhard Broeker (broeker@physik.rwth-aachen.de)
Even if all the snow were burnt, ashes would remain.

  reply	other threads:[~2003-05-26  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jebrxxc1h6.fsf@sykes.suse.de>
     [not found] ` <Pine.OSF.4.44.0305201411310.26315-100000@acaxp6.physik.rwth-aachen.de>
     [not found]   ` <3ECE499C.481FF0C0@physik.rwth-aachen.de>
2003-05-24 23:19     ` gnuplot vs. emacs' compile command Richard Stallman
2003-05-26  9:06       ` Hans-Bernhard Broeker [this message]
2003-05-27 12:45         ` Richard Stallman
2003-05-27 13:04           ` Hans-Bernhard Broeker
2003-05-28 13:55             ` Richard Stallman

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=Pine.OSF.4.44.0305261048390.13660-100000@acaxp6.physik.rwth-aachen.de \
    --to=broeker@physik.rwth-aachen.de \
    --cc=emacs-devel@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).