From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, martin rudalics <rudalics@gmx.at>
Cc: 21643@debbugs.gnu.org
Subject: bug#21643: 25.0.50; Error "<nil> <down-mouse-1> is undefined"
Date: Thu, 08 Oct 2015 22:32:11 +0300 [thread overview]
Message-ID: <83oag9cg1w.fsf@gnu.org> (raw)
In-Reply-To: <59204c8a-71b5-4a2a-b6c6-394e932def02@default>
> Date: Thu, 8 Oct 2015 11:39:44 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 21643@debbugs.gnu.org
>
> 1. Start Emacs with an MS Windows shortcut that has this target:
> runemacs.exe -Q --debug-init -l "onetest4.el" -f "1on1-emacs" "onetest4.el"
>
> 2. Click the title bar of the minibuffer frame (not needed, but
> just to make sure the frame is selected.
>
> 3. C-h k
>
> 4. Click mouse-1 somewhere in the second line of the minibuffer frame.
>
> You see this message:
> <nil> <down-mouse-1> (translated from <down-mouse-1>) at that spot is undefined
Thanks. There's clearly some display bug that shows in the minibuffer
frame: look carefully and you will see that the fringes and the scroll
bar only extend for a single line there. The second line is some kind
of "no-man's land", which explains the "nil" part in the mouse event.
If you drag the lower edge of the minibuffer frame by even a single
pixel, then return it back to its original (or even smaller) height,
the problem with the fringes goes away, and so does the problem with
the mouse click.
I will take a look.
Martin, this looks somewhat similar to the problem you solved the
other day, whereby "M-x" echo would not be visible. So maybe you
could look into this as well, if you have time.
next prev parent reply other threads:[~2015-10-08 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<3f16785a-2105-4715-b6ab-b7b2298dc3ca@default>
[not found] ` <<83vbahcs6z.fsf@gnu.org>
2015-10-08 18:39 ` bug#21643: 25.0.50; Error "<nil> <down-mouse-1> is undefined" Drew Adams
2015-10-08 19:32 ` Eli Zaretskii [this message]
2015-10-09 10:06 ` martin rudalics
2015-10-09 12:56 ` Eli Zaretskii
[not found] ` <<59204c8a-71b5-4a2a-b6c6-394e932def02@default>
[not found] ` <<83oag9cg1w.fsf@gnu.org>
2015-10-08 20:40 ` Drew Adams
2015-10-08 21:03 ` Drew Adams
[not found] ` <<561791C3.90806@gmx.at>
[not found] ` <<83wpuwtd3f.fsf@gnu.org>
2015-10-09 13:05 ` Drew Adams
2015-10-07 22:15 Drew Adams
2015-10-08 15:09 ` Eli Zaretskii
2019-09-29 22:13 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oag9cg1w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21643@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).