From: Dan Nicolaescu <dann@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
10169@debbugs.gnu.org, Jim Meyering <jim@meyering.net>
Subject: bug#10169: a simple interrupt evokes abort?! (but only with (require 'saveplace))
Date: Sat, 03 Dec 2011 16:04:15 -0500 [thread overview]
Message-ID: <yxqfwh1xt80.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <m28vmuavbw.fsf@igel.home> (Andreas Schwab's message of "Sat, 03 Dec 2011 09:54:59 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> Glenn Morris wrote:
>>
>>> Now interrupts are silently ignored:
>>>
>>> bash> ./emacs -Q
>>> ctrl-C # in the shell
>>>
>>> just prints ^C.
>>
>> Correction, not silently ignored: Emacs prints "Quit" but is otherwise
>> unaffected.
>
> IMHO this is the correct behaviour for an interactive programm.
Why do you think that and what other widely use programs can you name
that have the same behavior?
Why do you think that pretest is the right time to do such a change to a
long available behavior, and why is it OK to do it with zero discussion?
next prev parent reply other threads:[~2011-12-03 21:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 12:24 bug#10169: a simple interrupt evokes abort?! (but only with (require 'saveplace)) Jim Meyering
2011-12-01 16:03 ` Paul Eggert
2011-12-01 16:13 ` Jim Meyering
2011-12-01 18:09 ` Glenn Morris
2011-12-01 18:42 ` Andreas Schwab
2011-12-01 19:00 ` Glenn Morris
2011-12-01 19:02 ` Glenn Morris
2011-12-03 8:54 ` Andreas Schwab
2011-12-03 21:04 ` Dan Nicolaescu [this message]
2011-12-03 21:26 ` Andreas Schwab
2011-12-03 22:07 ` Dan Nicolaescu
2011-12-03 22:23 ` Andreas Schwab
2011-12-03 22:46 ` Dan Nicolaescu
2011-12-03 22:53 ` Daniel Colascione
2011-12-04 2:08 ` Chong Yidong
2011-12-04 9:37 ` Andreas Schwab
2011-12-04 15:05 ` Richard Stallman
2011-12-02 0:34 ` Dan Nicolaescu
2011-12-01 19:25 ` Stefan Monnier
2011-12-01 19:38 ` Dan Nicolaescu
2011-12-03 20:21 ` Glenn Morris
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=yxqfwh1xt80.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=10169@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jim@meyering.net \
--cc=schwab@linux-m68k.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).