From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 75219@debbugs.gnu.org, visuweshm@gmail.com
Subject: bug#75219: 31.0.50; mouse-2 mode-line binding overridden by mouse-1-click-follows-link
Date: Sun, 05 Jan 2025 20:51:36 +0200 [thread overview]
Message-ID: <86ikqt6qmf.fsf@gnu.org> (raw)
In-Reply-To: <jwvy0zpgmlz.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 05 Jan 2025 13:10:45 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Visuwesh <visuweshm@gmail.com>, 75219@debbugs.gnu.org
> Date: Sun, 05 Jan 2025 13:10:45 -0500
>
> > So if POSITION is a mouse click event, click_position will always
> > return the position of point.
>
> Yeah, we pay attention to the "window" part of the posn but not the
> rest. 🙁
>
> > Stefan, any ideas or suggestions?
>
> Maybe something like the patch below, but maybe we should call
> `posn-point` instead?
It shouldn't be hard to find a solution along these lines, but what
bothers me is how many Lisp code out there relies on this strange
"fallback"?
Also, for clicks on mode line there will be no buffer position in the
event, and then it sounds like your patch will again fall back on
returning point? I thought that clicks on the mode line should
examine local keymaps only on the mode-line's string at the click,
don't you agree?
next prev parent reply other threads:[~2025-01-05 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 5:37 bug#75219: 31.0.50; mouse-2 mode-line binding overridden by mouse-1-click-follows-link Visuwesh
2025-01-05 15:17 ` Eli Zaretskii
2025-01-05 18:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 18:51 ` Eli Zaretskii [this message]
2025-01-05 21:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-07 18:57 ` Eli Zaretskii
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=86ikqt6qmf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75219@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=visuweshm@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.