From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 6945@debbugs.gnu.org
Subject: bug#6945: active-minibuffer-window returns nil when prompt overwritten by message
Date: Mon, 30 Aug 2010 15:57:41 +0200 [thread overview]
Message-ID: <AANLkTinQhXLDfxCwvtbJCwXe1+qUO0Pk=2hkvNxqBcDR@mail.gmail.com> (raw)
In-Reply-To: <87sk1wjjo4.fsf@escher.home>
On Mon, Aug 30, 2010 at 3:48 PM, Stephen Berman <stephen.berman@gmx.net> wrote:
>
> I guess I misunderstood -- I thought you were reporting you saw no
> prompt and could not get it with the above recipe. As for
> active-minibuffer-window not returning a window, maybe I still
> misunderstand, but I get the message "active-minibuffer-window = nil"
That is what I get too.
> not only with the above progn, but also with this:
>
> (progn
> (run-with-idle-timer 1 nil 'message "idle message")
> (run-with-idle-timer 2 nil 'temp-active-mb)
> )
>
> and even just with this:
>
> (run-with-idle-timer 2 nil 'temp-active-mb)
>
> So the prompt seems to make no difference. Or do you see (or expect)
> something different?
I expected active-minibuffer-window to return a window, but as Andreas
has pointed out y-or-n-p is implemented in a different way. It just
call `message' and then read a key from the user.
However I would like to detect such situations too. From the users
point of view they are very similar to other prompts. (If you replace
`y-or-n-p' with `yes-or-no-p' then active-minibuffer-window will
return a window.)
next prev parent reply other threads:[~2010-08-30 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 10:30 bug#6945: active-minibuffer-window returns nil when prompt overwritten by message Lennart Borgman
2010-08-30 12:44 ` Stephen Berman
2010-08-30 13:09 ` Lennart Borgman
2010-08-30 13:48 ` Stephen Berman
2010-08-30 13:57 ` Lennart Borgman [this message]
2010-08-30 13:11 ` Andreas Schwab
2010-08-30 13:46 ` Lennart Borgman
2020-08-20 18:25 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTinQhXLDfxCwvtbJCwXe1+qUO0Pk=2hkvNxqBcDR@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=6945@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.