GNU bug report logs -
#11939
24.1; `save-buffers-kill-emacs' loses minibuffer focus when it calls `list-processes'
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Fri, 13 Jul 2012 18:07:01 UTC
Severity: normal
Found in version 24.1
Done: martin rudalics <rudalics <at> gmx.at>
Bug is archived. No further changes may be made.
Full log
Message #62 received at 11939 <at> debbugs.gnu.org (full text, mbox):
> I attach the first version of `with-temp-buffer-window',
> however, with a redefined `y-or-n-p'. Try it with your code but with
> `yes-or-no-p' aliased to `y-or-n-p'.
>
> Here, with emacs -Q
> (progn
> (defalias 'yes-or-no-p 'y-or-n-p)
> (load "~/with-temp-buffer-window.el")
> (shell)
> (setq minibuffer-auto-raise t)
> (setq pop-up-frame-function
> (lambda () (make-frame '((minibuffer . nil)))))
> (setq pop-up-frames t))
I did this:
1. Used my setup. Then did the defalias. Then loaded your file. Then `M-x
shell'. Then `C-x C-c'. Then `y'. No problem.
2. emacs -Q, then used your code above, but first loaded cygwin-mount.el and
setup-cygwin.el. C-x C-c. No problem.
HTH.
BTW, you did not answer my question of how you get shell etc. to work on Windows
with emacs -Q and without Cygwin. I'm still interested to learn what you are
doing in that regard.
> I suppose that we should (at least optionally) have all functions
> accessing the minibuffer redirect frame focus to it first.
I thought that was already the case - it seems to be. In the problem reported
for this bug the minibuffer frame had the focus, but it then lost it because of
a frame switch (I mean, because a new frame creation by Windows switched the
focus).
This bug report was last modified 12 years and 288 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.