From: Stephen Berman <stephen.berman@gmx.net>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6945@debbugs.gnu.org
Subject: bug#6945: active-minibuffer-window returns nil when prompt overwritten by message
Date: Mon, 30 Aug 2010 15:48:27 +0200 [thread overview]
Message-ID: <87sk1wjjo4.fsf@escher.home> (raw)
In-Reply-To: <AANLkTi=4xvLEoyJjnZ9V4N+Nf4Teqo5xnQ5GoFm+aH4T@mail.gmail.com> (Lennart Borgman's message of "Mon, 30 Aug 2010 15:09:23 +0200")
On Mon, 30 Aug 2010 15:09:23 +0200 Lennart Borgman <lennart.borgman@gmail.com> wrote:
> On Mon, Aug 30, 2010 at 2:44 PM, Stephen Berman <stephen.berman@gmx.net> wrote:
>> On Mon, 30 Aug 2010 12:30:37 +0200 Lennart Borgman <lennart.borgman@gmail.com> wrote:
>>
>>> Eval the following
>>>
>>>
>>> (defun temp-active-mb ()
>>> (message "active-minibuffer-window = %s" (active-minibuffer-window)))
>>>
>>> (progn
>>> (run-with-idle-timer 1 nil 'message "idle message")
>>> (run-with-idle-timer 2 nil 'temp-active-mb)
>>> (y-or-n-p "Prompt: ")
>>> )
>>>
>>> This gives me the message "active-minibuffer-window = nil".
>>
>> When I eval the above sexps on GNU Emacs 24.0.50.1 (i686-pc-linux-gnu,
>> GTK+ Version 2.18.6) of 2010-08-22 on escher, I first briefly see the
>> message "Prompt: (y or n)", then "idle message", then
>> "active-minibuffer-window = " with the cursor after "= "; as soon as I
Correction: "active-minibuffer-window = nil" and "= nil", i.e. same as you.
>> type any other key, I get "Prompt: (y or n)" again.
>>
>>> Is there any way then to discover whether Emacs is displaying a prompt
>>> and waiting for input?
>>
>> Are you trying this on MS-Windows? If so, it seems to be a problem
>> there.
>
> Thanks Stephen. However it looks to me from what you write above like
> active-minibuffer-window does not return a window in this case on
> GNU/Linux either.
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"
not only with the above progn, but also with this:
"active-minibuffer-window = nil".
>>
>> When I eval the above sexps on GNU Emacs 24.0.50.1 (i686-pc-linux-gnu,
>> GTK+ Version 2.18.6) of 2010-08-22 on escher, I first briefly see the
>> message "Prompt: (y or n)", then "idle message", then
>> "active-minibuffer-window = " with the cursor after "= "; as soon as I
Correction: "active-minibuffer-window = nil" and "= nil"
>> type any other key, I get "Prompt: (y or n)" again.
>>
>>> Is there any way then to discover whether Emacs is displaying a prompt
>>> and waiting for input?
>>
>> Are you trying this on MS-Windows? If so, it seems to be a problem
>> there.
>
> Thanks Stephen. However it looks to me from what you write above like
> active-minibuffer-window does not return a window in this case on
> GNU/Linux either.
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"
not only with the above progn, but also with this:
"active-minibuffer-window = nil".
>>
>> When I eval the above sexps on GNU Emacs 24.0.50.1 (i686-pc-linux-gnu,
>> GTK+ Version 2.18.6) of 2010-08-22 on escher, I first briefly see the
>> message "Prompt: (y or n)", then "idle message", then
>> "active-minibuffer-window = " with the cursor after "= "; as soon as I
Correction: "active-minibuffer-window = nil" and "= nil"
>> type any other key, I get "Prompt: (y or n)" again.
>>
>>> Is there any way then to discover whether Emacs is displaying a prompt
>>> and waiting for input?
>>
>> Are you trying this on MS-Windows? If so, it seems to be a problem
>> there.
>
> Thanks Stephen. However it looks to me from what you write above like
> active-minibuffer-window does not return a window in this case on
> GNU/Linux either.
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"
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?
Steve Berman
next prev parent reply other threads:[~2010-08-30 13:48 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 [this message]
2010-08-30 13:57 ` Lennart Borgman
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=87sk1wjjo4.fsf@escher.home \
--to=stephen.berman@gmx.net \
--cc=6945@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
/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.