GNU bug report logs - #10613
24.0.92; Odd behavior of kill interspersed with suspend: document or change?

Previous Next

Full log

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

From: Daniel Colascione <dancol <at> dancol.org>
To: Reuben Thomas <rrt <at> sc3d.org>, 10613 <at> debbugs.gnu.org
Subject: Re: bug#10613: Please consider this report again
Date: Wed, 14 Feb 2018 18:00:18 -0800

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.

Previous Next

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