From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 10613@debbugs.gnu.org
Subject: bug#10613: Please consider this report again
Date: Wed, 14 Feb 2018 19:05:06 +0200 [thread overview]
Message-ID: <83606zy01q.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdohFLLZLkZNgFCuk99GW8EzL_L3mR7Zrc9sCxAyn3iTHaA@mail.gmail.com> (message from Reuben Thomas on Tue, 13 Feb 2018 09:19:04 +0000)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 13 Feb 2018 09:19:04 +0000
>
> But I think the report remains valid: suspending Emacs is not a movement, not an editing command, so why
> should it affect the behaviour of the next kill?
>
> Consider: if I suspend the computer on which I am running Emacs, then it does not affect the behaviour of
> Emacs in any way (or shouldn't!). When I resume, Emacs will behave exactly as if nothing had happened in
> the interim (other than time having passed).
>
> So from Emacs's perspective, why should "suspend-emacs" behave differently?
There's any number of Emacs commands that are neither movement nor
editing. For example, iconify-frame.
It might be a useful feature to not interrupt a series of kills across
these commands, but that's not how this feature was programmed: it
specifically looks at the last command, and makes no exceptions.
So this is not a bug, it's a request for a new feature.
next prev parent reply other threads:[~2018-02-14 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:21 bug#10613: 24.0.92; Odd behavior of kill interspersed with suspend: document or change? Reuben Thomas
2012-02-02 8:10 ` Kevin Rodgers
2018-02-13 0:32 ` Noam Postavsky
2018-02-13 9:19 ` bug#10613: Please consider this report again Reuben Thomas
2018-02-14 17:05 ` Eli Zaretskii [this message]
2018-02-15 1:51 ` Noam Postavsky
2018-02-15 2:00 ` Daniel Colascione
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83606zy01q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10613@debbugs.gnu.org \
--cc=rrt@sc3d.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.