Subject: bug#12766: closed (Re: bug#12766: read-from-minibuffer does not preserve current-buffer)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 10 Nov 2012 11:08:02 +0000

Your bug report

#12766: read-from-minibuffer does not preserve current-buffer

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
12766: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12766
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#12766: read-from-minibuffer does not preserve current-buffer
From: martin rudalics <[email-masked]>
To: Stefan Monnier <[email-masked]>
Cc: [email-masked]
Date: Sat, 10 Nov 2012 12:07:04 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

>> Can we close this bug?
> Yes.

Closed.

Thanks, martin

Subject: read-from-minibuffer does not preserve current-buffer
From: Stefan Monnier <[email-masked]>
To: [email-masked]
Date: Mon, 29 Oct 2012 16:29:29 -0400
List-Id: <debbugs-submit.debbugs.gnu.org>

Package: Emacs
Version: 24.2.50

% src/emacs -Q --eval "(setq initial-frame-alist '((minibuffer . nil)))"
M-: (with-temp-buffer (list (read-string "toto: ") (current-buffer))) RET

In Emacs 24.2 this always shows the current-buffer to be the temp buffer
(which is a killed buffer by the time M-: prints its result).
But in Emacs trunk, the result depends on whether you issue the M-:
from the normal frame (where it works right) or from the special
minibuffer-only frame, where current-buffer after read-string is
*minibuf-0*!

This is a serious problem, which introduces subtle bugs that can be
pretty difficult to track down.

        Stefan