GNU bug report logs - #43376
A more aware "compilation process is running; kill it? (yes or no) "

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 43376 in the body.
You can then email your comments to 43376 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: A more aware "compilation process is running; kill it? (yes or no) "
Date: Sun, 13 Sep 2020 21:28:55 +0800

When one is looking at the prompt
"A compilation process is running; kill it? (yes or no) "
but then the compilation finishes,
wouldn't it be great if the prompt realized that fact and changed itself?
emacs-version "26.3"

Message #10 received at 43376 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 43376 <at> debbugs.gnu.org
Subject: Re: bug#43376: A more aware "compilation process is running; kill
 it? (yes or no) "
Date: Sun, 13 Sep 2020 19:14:17 +0200

積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> When one is looking at the prompt
> "A compilation process is running; kill it? (yes or no) "
> but then the compilation finishes,
> wouldn't it be great if the prompt realized that fact and changed itself?

Perhaps...  but if it changes just when you're about to type "yes", then
you'll end up typing "yes" into some random buffer, which isn't nice.

I this the UI should avoid, as far as possible, pulling the rug out from
under the user.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #13 received at 43376 <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 43376 <at> debbugs.gnu.org
Subject: Re: bug#43376: A more aware "compilation process is running;
 kill it? (yes or no) "
Date: Mon, 14 Sep 2020 20:29:12 +0800

Yes, one would think: "When we realize that now there is nothing to ask
about, just go ahead and do what the user originally wanted (run the
second compilation.)"

OK, but maybe he forgot he had a compilation running, and at least he
would like to see the output first before running the second
compilation.

So maybe when we realize there is nothing left to ask the user about,
first throwaway any answer he already started typing,
and change the question to just
"proceed? (y or n)".

>>>>> "LI" == Lars Ingebrigtsen <larsi <at> gnus.org> writes:

LI> I this    the UI should avoid, as far as possible, pulling the rug out from
      ^think^
LI> under the user.

Message #16 received at 43376 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 43376 <at> debbugs.gnu.org
Subject: Re: bug#43376: A more aware "compilation process is running; kill
 it? (yes or no) "
Date: Mon, 14 Sep 2020 14:30:43 +0200

積丹尼 Dan Jacobson <jidanni <at> jidanni.org> writes:

> So maybe when we realize there is nothing left to ask the user about,
> first throwaway any answer he already started typing,
> and change the question to just
> "proceed? (y or n)".

Same thing, really -- the user is starting to type "yes" and then it
changes to something else.  So I don't think this is a workeable idea.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.