unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 21833@debbugs.gnu.org, si@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	[thread overview]
Message-ID: <83mvuigwig.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0STS=do_YcBTnUm5z92ZZFT3GU5mK-1MeYCsBb9-NnX_-A@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 13 Nov 2015 01:27:32 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, 21833@debbugs.gnu.org, Stelian Iancu <si@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?





  reply	other threads:[~2015-11-13  7:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 22:43 bug#21833: 24.4; desktop-kill, which is interactive, is in kill-emacs-hook Michael Arntzenius
2015-11-12 20:07 ` Stelian Iancu
2015-11-12 20:11   ` Glenn Morris
2015-11-12 20:24     ` Stelian Iancu
2015-11-12 20:50       ` Eli Zaretskii
2015-11-12 21:38         ` Glenn Morris
2015-11-12 23:04           ` Juanma Barranquero
2015-11-12 23:38             ` Glenn Morris
2015-11-12 23:53               ` Juanma Barranquero
2015-11-13  0:27                 ` Juanma Barranquero
2015-11-13  7:59                   ` Eli Zaretskii [this message]
2015-11-13  9:39                     ` Juanma Barranquero
2015-11-13 10:03                       ` Eli Zaretskii
2015-11-13 10:17                         ` Juanma Barranquero
2015-11-13 14:07                           ` Eli Zaretskii
2015-11-13 14:36                             ` Juanma Barranquero
2015-11-13  7:56                 ` Eli Zaretskii
2015-11-13  9:30                   ` Juanma Barranquero
2015-11-13 10:01                     ` Eli Zaretskii
2015-11-13 10:14                       ` Juanma Barranquero
2015-11-13 14:05                         ` Eli Zaretskii
2015-11-13 14:35                           ` Juanma Barranquero
2015-11-13 18:55                             ` Eli Zaretskii
2015-11-15 11:54                               ` Juanma Barranquero
2015-11-15 19:40                                 ` Eli Zaretskii
2015-11-13  8:36           ` Eli Zaretskii

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=83mvuigwig.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21833@debbugs.gnu.org \
    --cc=lekktu@gmail.com \
    --cc=si@siancu.net \
    /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).