From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 13692@debbugs.gnu.org
Subject: bug#13692: mouse clicks in vc-dir buffers accidentally changing marks
Date: Sat, 30 Jan 2021 16:05:05 +0200 [thread overview]
Message-ID: <86a50315-e3c4-1a6f-a92e-abcca84b81b3@yandex.ru> (raw)
In-Reply-To: <87o8h70wsx.fsf@gnus.org>
On 30.01.2021 08:21, Lars Ingebrigtsen wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>> Not sure if we should close this now.
>
> I think we should make the "*" area also clickable -- I think that's the
> most confusing part here now (that only clicking the status area toggles
> the "*", and clicking the "*" itself doesn't do anything).
I don't know if it's so confusing: after all, we have mouse-face to let
the user know which area can be interacted with mouse clicks. The
asterisk is not highlighted, so it's not clickable.
We can change that, but how? Extend highlighting to the asterisk column?
On all lines, whether the asterisk is there or not?
The way that the button currently starts where the text starts looks
tidy and nice, IMHO.
>> While we're on the subject of buttons, I think it's odd that mouse-1
>> and mouse-2 routinely do the same thing, here and in other cases
>> (e.g. links in Compilation buffers). But I suppose this is outside of
>> scope for this discussion.
>
> Yeah, the mouse thing is pretty confusing, but the
> `mouse-1-click-follows-link' variable can be set to change the
> behaviour.
All right.
And I guess (setq mouse-1-click-follows-link nil) can be a solution for
the original complaint here.
next prev parent reply other threads:[~2021-01-30 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 4:56 bug#13692: mouse clicks in vc-dir buffers accidentally changing marks Glenn Morris
2021-01-20 3:58 ` Lars Ingebrigtsen
2021-01-21 3:08 ` Dmitry Gutov
2021-01-21 14:46 ` Lars Ingebrigtsen
2021-01-23 1:43 ` Dmitry Gutov
2021-01-23 19:02 ` Lars Ingebrigtsen
2021-01-24 2:23 ` Dmitry Gutov
2021-01-25 23:59 ` Lars Ingebrigtsen
2021-01-26 0:36 ` Dmitry Gutov
2021-01-27 1:39 ` Lars Ingebrigtsen
2021-01-30 2:01 ` Dmitry Gutov
2021-01-30 6:21 ` Lars Ingebrigtsen
2021-01-30 14:05 ` Dmitry Gutov [this message]
2021-01-31 7:27 ` Lars Ingebrigtsen
2021-08-23 14:12 ` 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
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=86a50315-e3c4-1a6f-a92e-abcca84b81b3@yandex.ru \
--to=dgutov@yandex.ru \
--cc=13692@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
/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).