unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Glenn Morris <rgm@gnu.org>, 13692@debbugs.gnu.org
Subject: bug#13692: mouse clicks in vc-dir buffers accidentally changing marks
Date: Sat, 23 Jan 2021 20:02:57 +0100	[thread overview]
Message-ID: <875z3nv5lq.fsf@gnus.org> (raw)
In-Reply-To: <927a3c2e-bd77-df54-303c-e9c098f5d244@yandex.ru> (Dmitry Gutov's message of "Sat, 23 Jan 2021 03:43:19 +0200")

Dmitry Gutov <dgutov@yandex.ru> writes:

> We're talking about slightly different things.
>
> When I hear "mouse-2 binding", I think the global bidning in
> vc-dir-mode-map, which affects how mouse-2 works also when clicking
> outside of any buttons (on whitespace beside the buttons). And I think
> that behavior is relatively weird and could be removed.

I didn't even notice that `mouse-2' did stuff when outside the
"buttons".  And what it does is quite odd...  hm, no, if you click after
the final line, it'll mark the last line, and before the first, it'll
mark the first, so perhaps that's logical?

> But we also have the behavior of mouse-1 and mouse-2 clicks on the
> "status" button. Which seem fairly sensible to me, but might be the
> cause of Glenn's annoyance in this report because it's relatively easy
> to click mouse-1 anywhere in the buffer by mistake.

Yes, I think he was complaining about the "status" button.

> Right. But if that is what is at issue here, I think the question
> becomes whether to remove the "buttons" from that column (and keep the
> mouse-2 binding globally) or whether to remove the mouse-2 binding,
> but set up the buttons to continue working. Or make mouse-1 stop
> working on the buttons but keep mouse-2 working everywhere (except the
> file names, I guess?).

I think removing the global mouse bindings and only having them on the
"buttons" would be least surprising -- that's how most modes work.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-01-23 19:02 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 [this message]
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
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=875z3nv5lq.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=13692@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).