GNU bug report logs - #21833
24.4; desktop-kill, which is interactive, is in kill-emacs-hook

Previous Next

Package: emacs;

Reported by: Michael Arntzenius <daekharel <at> gmail.com>

Date: Wed, 4 Nov 2015 23:09:02 UTC

Severity: minor

Merged with 28943

Found in versions 24.4, 25.2

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 21833 <at> debbugs.gnu.org, rgm <at> gnu.org, si <at> siancu.net
Subject: bug#21833: 24.4; desktop-kill, which is interactive, is in kill-emacs-hook
Date: Fri, 13 Nov 2015 09:59:35 +0200

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Fri, 13 Nov 2015 01:27:32 +0100
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 21833 <at> debbugs.gnu.org, Stelian Iancu <si <at> siancu.net>
> 
> I say:
> 
> emacs -Q
> (require 'emacs-lock) <C-x C-e>
> (emacs-lock-mode 'exit) <C-x C-e>
> M-x kill-emacs <RET>
> 
> Expected behavior: emacs is killed ???
> Actual behavior: => Emacs cannot exit because buffer "*scratch*" is locked
> 
> Because I use emacs-lock and I certainly wouldn't expect it to be killed.

Then I guess you are saying that in the case of emacs-lock there's no
similar bug?

I'll probably agree (I don't use that package), but why does it have
to tell us that desktop.el should behave the same?  It doesn't have
the same purpose, right?
This bug report was last modified 4 years and 10 days ago.

Previous Next

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