bug#3696: marked as done (23.1.50; C-x # quits the frame before buffer-modified confirmation)

[Emacs bug Tracking System]

Your message dated Sun, 28 Jun 2009 23:29:35 -0400
with message-id <87eit3zpi8.fsf@stupidchicken.com>
and subject line Re: 23.1.50; Buffer-modified confirmation goes to wrong frame 
in daemon mode
has caused the Emacs bug report #3696,
regarding 23.1.50; C-x # quits the frame before buffer-modified confirmation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3696: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3696
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 23.1.50; Buffer-modified confirmation goes to wrong frame in daemon mode
>
>
>
>
> Date: 
>
> Sat, 27 Jun 2009 21:35:35 +0300
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
>
>
>
>
> In daemon/client mode "C-x #" (server-edit) quits too early from its
> frame and leaves the confirm "Buffer foo modified; kill anyway? (yes or
> no)" in wrong frame's minibuffer. If there are no other frames the
> confirm is totally hidden. Steps to reproduce:
>
>  1. Start Emacs in daemon mode:
>
>         emacs -Q --daemon
>
>  2. Open an independent Emacs frame:
>
>         emacsclient -c -n
>
>  3. Leave that frame and start to edit a file in client mode:
>
>         emacsclient -c -- foo
>
>  4. Frame opens with buffer/file "foo". Now modify the buffer and type
>     "C-x #" (server-edit). Answer "n" in the question whether to save
>     the file "foo". The frame for file "foo" closes.
>
>  5. In the other frame, the one we opened first, has the question
>
>         Buffer foo modified; kill anyway? (yes or no)
>
>     in its minibuffer. I think it should have been shown in the frame
>     where buffer "foo" was.
>
> Here's an example of weird situation this bug can lead to. Don't close
> this Emacs daemon session yet.
>
>  6. Close all frames.
>
>  7. Start editing a file:
>
>         emacsclient -c -- foo
>
>  8. Modify the buffer, leave the buffer with "C-x #" and answer "n" in
>     the question whether to save the file. The frame for file "foo"
>     closes. The confirmation question is invisible because there are no
>     frames to show it.
>
>  9. Open new independent frame:
>
>         emacsclient -c -n
>
> 10. The frame opens but its content is empty. Emacs is still waiting for
>     user's input in the minibuffer but the question is invisible.
>
> 11. Press any key to skip the question. Now the frame is displayed
>     normally. Buffer "foo" is still in the buffer list.
>
>
> Quite obviously the question "Buffer foo modified; kill anyway? (yes or
> no)" should be displayed in the frame of the buffer "foo" before closing
> the frame.
>
>
>
> In GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.12.12)
>  of 2009-06-27 on mithlond
> Windowing system distributor `The X.Org Foundation', version 11.0.10402000
> configured using `configure  '--prefix=/home/dtw/local''
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: 23.1.50; Buffer-modified confirmation goes to wrong frame in daemon mode
>
>
>
>
> Date: 
>
> Sun, 28 Jun 2009 23:29:35 -0400
>
>
>
>
> > In daemon/client mode "C-x #" (server-edit) quits too early from its
> > frame and leaves the confirm "Buffer foo modified; kill anyway? (yes or
> > no)" in wrong frame's minibuffer.
> >
> > Quite obviously the question "Buffer foo modified; kill anyway? (yes or
> > no)" should be displayed in the frame of the buffer "foo" before closing
> > the frame.
>
> I don't see why we need to prompt twice, so in this case it should be OK
> to suppress the usual kill-buffer prompt.  I've checked in a fix for
> this into the trunk.
>
> --- End Message ---