unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62157@debbugs.gnu.org, Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: bug#62157: More control over the mouse behaviour in eglot
Date: Mon, 13 Mar 2023 17:36:58 +0100	[thread overview]
Message-ID: <87h6uovc9h.fsf@gmail.com> (raw)
In-Reply-To: <CALDnm510C+8TVhLpa20jvQ6Qt2WrxeOuZua9+xOtecZcoBiy1w@mail.gmail.com> ("João Távora"'s message of "Mon, 13 Mar 2023 16:09:59 +0000")

>>>>> On Mon, 13 Mar 2023 16:09:59 +0000, João Távora <joaotavora@gmail.com> said:
    >> In any case, this doesnʼt make the binding easily changable, you have
    >> to manually unset/set the `eglot-code-actions-at-mouse' binding. My
    >> attempt to fix this descended into a circular dependency spiral
    >> between the keymap and the key defcustom, so Iʼm hoping you know a
    >> good way to do it :-)

    João> A key defcustom isn't needed IMO.  You may even want multiple
    João> bindings there.  99% percent of users will like the default
    João> bindings, the others can

OK. We can always add it if people ask for it.

    João>   (define-key eglot-diagnostics-map [mouse-2] nil)

    João> or

    João>   (unbind-key [mouse-1] eglot-diagnostics-map)

    João> which I don't know if exists in older Emacsen.

I think itʼs an emacs-29 thing. Although it does look kind of
redundant with `keymap-unset' (which is also new in emacs-29) :-)

Robert
-- 





  reply	other threads:[~2023-03-13 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  7:20 bug#62157: More control over the mouse behaviour in eglot Pedro Andres Aranda Gutierrez
2023-03-13 15:47 ` João Távora
2023-03-13 15:59   ` Robert Pluim
2023-03-13 16:09     ` João Távora
2023-03-13 16:36       ` Robert Pluim [this message]
2023-09-12  0:22   ` Stefan Kangas
2023-09-12  5:23     ` Pedro Andres Aranda Gutierrez
2023-09-12  7:07     ` João Távora
2023-09-13 16:12       ` Stefan Kangas

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=87h6uovc9h.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=62157@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=paaguti@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 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).