From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 1b71c995da: Avoid binding mouse-1 in xref when mouse-1 doesn't follow links
Date: Fri, 29 Apr 2022 15:34:15 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488024A804FB9FBC1615768F3FC9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87fslwdo88.fsf@gnus.org>
> > Hmm... this won't adjust if `mouse-1-click-follows-link` is changed
> > later on. Why do we need this `mouse-1` binding?
>
> Dmitry seems to like the two different actions (which only differ in
> whether the other buffer is selected or not). I'd be fine with
> removing the mouse-1 binding.
Bug #35353:
I use `mouse-1-click-follows-link' = nil.
(I use `mouse-2', not `mouse-1', to follow
clicked links, buttons, etc.) But this
setting seems to have no effect in buffer `*xref*'.
Except by clicking on a file line (it seems),
I find it impossible to click `mouse-1' without
having Emacs follow a link; impossible to set
point in the buffer using `mouse-1'; no way to
just click buffer text to select its frame.
What's that all about?
For which you've said:
Lars>> we don't honor mouse-1-click-follows-link.
Eli> FWIW, I don't see that as a serious issue in
this case. Feel free to close as wontfix,
if you want.
But you said today that you fixed (this part of)
the reported bug, for Emacs 29. I hope so.
next prev parent reply other threads:[~2022-04-29 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165123369667.6415.4605821518748112960@vcs2.savannah.gnu.org>
[not found] ` <20220429120137.0F053C06322@vcs2.savannah.gnu.org>
2022-04-29 13:00 ` master 1b71c995da: Avoid binding mouse-1 in xref when mouse-1 doesn't follow links Stefan Monnier
2022-04-29 13:16 ` Lars Ingebrigtsen
2022-04-29 15:34 ` Drew Adams [this message]
2022-04-29 16:16 ` Dmitry Gutov
2022-04-30 11:39 ` Lars Ingebrigtsen
2022-05-01 12:14 ` Dmitry Gutov
2022-05-02 8:02 ` Lars Ingebrigtsen
2022-04-29 17:17 ` 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=SJ0PR10MB5488024A804FB9FBC1615768F3FC9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.