From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 17633@debbugs.gnu.org
Subject: bug#17633: 24.3.91; mouse-drag-line: Symbol's function definition is void: mouse--remap-link-click-p
Date: Sun, 01 Jun 2014 17:57:47 +0300 [thread overview]
Message-ID: <83oaycbrtg.fsf@gnu.org> (raw)
In-Reply-To: <jwvy4xgg1f4.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 17633@debbugs.gnu.org
> Date: Sun, 01 Jun 2014 10:18:57 -0400
>
> >> > But why does it hurt to include the window's point in the click?
> >> Because mouse-posn-property then checks the text-property at point.
> > It shouldn't do that. This sounds like a problem with
> > mouse-posn-property rather than with make_lispy_position.
>
> In the case of fringe clicks, I agree that these events's
> buffer-position info is worthwhile and that mouse-posn-property should
> ignore it, but in the case of mode-line clicks, the click is completely
> unrelated to the particular position of point at that moment, os
> including that info is just asking for trouble,
It's not necessarily unrelated. Imagine some feature that wants to
change the effect of such a click depending on point. There's nothing
especially hilarious about that.
next prev parent reply other threads:[~2014-06-01 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 17:45 bug#17633: 24.3.91; mouse-drag-line: Symbol's function definition is void: mouse--remap-link-click-p Christopher Schmidt
2014-05-29 18:48 ` Stefan Monnier
2014-05-29 19:06 ` Christopher Schmidt
2014-05-29 20:32 ` Stefan Monnier
2014-05-29 20:47 ` Christopher Schmidt
2014-05-31 12:34 ` Stefan Monnier
2014-05-31 12:55 ` Christopher Schmidt
2014-05-31 13:00 ` Eli Zaretskii
2014-05-31 14:55 ` Stefan Monnier
2014-05-31 16:44 ` Eli Zaretskii
2014-05-31 20:11 ` Stefan Monnier
2014-06-01 2:41 ` Eli Zaretskii
2014-06-01 14:18 ` Stefan Monnier
2014-06-01 14:57 ` Eli Zaretskii [this message]
2014-06-01 21:13 ` Stefan Monnier
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=83oaycbrtg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17633@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.