GNU bug report logs -
#11725
24.1; confirm-nonexistent-file-or-buffer with after-completion value
Previous Next
Reported by: Szunti <szunti <at> gmail.com>
Date: Sat, 16 Jun 2012 17:39:02 UTC
Severity: normal
Found in version 24.1
Fixed in version 24.2
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
Full log
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Using the default value of "after-completion" of the variable
"confirm-nonexistent-file-or-buffer" never asks for confirmation.
I made a git bisect, the first bad commit is:
commit 064b509639208159ca7c619bccf319aef7950146
Author: Stefan Monnier <monnier <at> iro.umontreal.ca>
Date: Mon Mar 12 00:10:59 2012 -0400
* lisp/minibuffer.el (minibuffer-complete): Don't get confused
when the
function is run twice via different commands.
(complete-with-action): Fix docstring.
Steps to reproduce after bad commit:
1) made two files in bash:
$ cd /tmp
$ touch almafa almacsutka
2) open emacs
C-x C-f /tmp/al[TAB][RET]
[TAB] completes to /tmp/alma, then after pressing [RET], a new file
called alma is open, instead of asking for confirmation.
This bug report was last modified 12 years and 333 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.