all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 35376@debbugs.gnu.org
Subject: bug#35376: 26.2; (emacs) `Xref Commands' - no mention of `mouse-1'
Date: Tue, 09 Jul 2019 16:13:06 +0200	[thread overview]
Message-ID: <87zhlnthxp.fsf@mouse.gnus.org> (raw)
In-Reply-To: <2c45c976-8bf9-401c-8cb6-b60316909722@default> (Drew Adams's message of "Mon, 22 Apr 2019 05:49:51 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> In bug #35353 Dmitry talks about a "show location bug don't switch
> windows" action.  Dunno what this is, so I went to the manual to find
> out.  Presumably, from the #35353 thread it has something to do with
> `mouse-1'.  And in any case `mouse-1' is the default way to access
> references using the mouse, no?  I would expect this node to say
> something about `mouse-1'.

The mouse bindings are a bit confusing:

(defvar xref--button-map
  (let ((map (make-sparse-keymap)))
    (define-key map [mouse-1] #'xref-goto-xref)
    (define-key map [mouse-2] #'xref--mouse-2)
    map))

Why is the command called xref--mouse-2?  That's a very non-descriptive
command name.  And...  don't these two really kinda do the same thing?
mouse-1 sets the point first and then goes to the xref, and mouse-2
... does the same, only in a different way?

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





  reply	other threads:[~2019-07-09 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 12:49 bug#35376: 26.2; (emacs) `Xref Commands' - no mention of `mouse-1' Drew Adams
2019-07-09 14:13 ` Lars Ingebrigtsen [this message]
2019-07-30 14:08   ` Dmitry Gutov
2019-07-31 18:47     ` Lars Ingebrigtsen
2019-12-23 16:28       ` Dmitry Gutov
2021-08-31  2:50     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhlnthxp.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=35376@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.