unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Reuben Thomas <rrt@sc3d.org>, 10613@debbugs.gnu.org
Subject: bug#10613: Please consider this report again
Date: Wed, 14 Feb 2018 18:00:18 -0800	[thread overview]
Message-ID: <33f5af87-b578-a6fc-22a2-55188734e3ba@dancol.org> (raw)
In-Reply-To: <CAOnWdohFLLZLkZNgFCuk99GW8EzL_L3mR7Zrc9sCxAyn3iTHaA@mail.gmail.com>

On 02/13/2018 01:19 AM, Reuben Thomas wrote:
> Unfortunately the two responses to my report seem to have focussed on 
> just one word, which I probably chose badly. Sorry about that.
> 
> 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?
> 

I'd argue that Emacs should detect computer suspension somehow, treat it 
as a command, and reset any closely-spaced-interaction state it's been 
keeping. I don't think the original report is a bug.





      parent reply	other threads:[~2018-02-15  2:00 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
2018-02-15  1:51     ` Noam Postavsky
2018-02-15  2:00   ` Daniel Colascione [this message]

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=33f5af87-b578-a6fc-22a2-55188734e3ba@dancol.org \
    --to=dancol@dancol.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 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).