|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#12766: closed (read-from-minibuffer does not preserve current-buffer) |
Date: | Sat, 10 Nov 2012 11:08:02 +0000 |
Your message dated Sat, 10 Nov 2012 12:07:04 +0100 with message-id <address@hidden> and subject line Re: bug#12766: read-from-minibuffer does not preserve current-buffer has caused the debbugs.gnu.org bug report #12766, regarding read-from-minibuffer does not preserve current-buffer to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 12766: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12766 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: read-from-minibuffer does not preserve current-buffer Date: Mon, 29 Oct 2012 16:29:29 -0400 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
--- End Message ---
--- Begin Message ---Subject: Re: bug#12766: read-from-minibuffer does not preserve current-buffer Date: Sat, 10 Nov 2012 12:07:04 +0100 Can we close this bug?Yes.Closed. Thanks, martin
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |