From: Drew Adams <drew.adams@oracle.com>
To: 35353@debbugs.gnu.org
Subject: bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major mode name
Date: Sat, 20 Apr 2019 19:50:38 -0700 (PDT) [thread overview]
Message-ID: <96cafba3-7ba2-4e87-8f9d-e53825fd1dde@default> (raw)
Never bothered to use Xref (`dired-do-find-regexp' etc.) until now.
I'm already surprised at what I see within the first 3 minutes.
1. 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?
2. I try `C-h m' or `C-h v major-mode' to find out more about what's
going on, and I learn that the major mode is called
`xref--xref-buffer-mode'. Seriously? Why? It seems very wrong
and unEmacsy to give a major mode an "internal" name. Users
examine major modes. That's part of the usual help system for
even casual users.
Please respect `mouse-1-click-follows-link'. And please name the
major mode without an "internal-function" name. Thx.
In GNU Emacs 26.2 (build 1, x86_64-w64-mingw32)
of 2019-04-13
Repository revision: fd1b34bfba8f3f6298df47c8e10b61530426f749
Windowing system distributor `Microsoft Corp.', version 10.0.17134
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2019-04-21 2:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 2:50 Drew Adams [this message]
2019-04-21 13:27 ` bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major mode name Drew Adams
2019-04-22 9:24 ` Dmitry Gutov
2019-04-22 9:42 ` Eli Zaretskii
2019-04-22 9:48 ` Dmitry Gutov
2019-04-22 10:09 ` Eli Zaretskii
2019-04-22 10:18 ` Dmitry Gutov
2019-04-22 10:21 ` Eli Zaretskii
2019-04-22 10:52 ` Dmitry Gutov
2019-04-22 10:57 ` Dmitry Gutov
2019-04-22 11:42 ` Phil Sainty
2019-04-22 13:08 ` Drew Adams
2019-05-02 22:35 ` Dmitry Gutov
2019-05-02 23:22 ` Drew Adams
2019-05-02 23:31 ` Dmitry Gutov
2019-05-03 0:27 ` Drew Adams
2019-05-04 21:21 ` Richard Stallman
2019-05-04 22:25 ` Drew Adams
2019-05-05 22:50 ` Richard Stallman
2019-05-06 0:40 ` Drew Adams
2019-05-06 8:45 ` Dmitry Gutov
2019-05-06 13:29 ` Drew Adams
2019-05-02 22:48 ` Dmitry Gutov
2019-05-02 23:22 ` Drew Adams
2019-05-02 23:34 ` Dmitry Gutov
2019-05-03 0:27 ` Drew Adams
2019-04-22 11:07 ` Drew Adams
2019-04-22 11:18 ` Eli Zaretskii
2019-04-22 11:30 ` Dmitry Gutov
2019-04-22 11:34 ` Eli Zaretskii
2019-05-02 22:49 ` Dmitry Gutov
2019-05-03 6:38 ` Eli Zaretskii
2020-08-22 14:41 ` Lars Ingebrigtsen
2020-08-22 17:46 ` Drew Adams
[not found] ` <<83v9z6732b.fsf@gnu.org>
2019-04-22 11:07 ` Drew Adams
2019-04-22 11:20 ` Eli Zaretskii
[not found] ` <<<83v9z6732b.fsf@gnu.org>
[not found] ` <<376d5335-eb80-4272-8847-e764242a02b7@default>
[not found] ` <<83r29u70cy.fsf@gnu.org>
2019-04-22 12:23 ` Drew Adams
2019-04-22 13:05 ` Eli Zaretskii
[not found] ` <<<<83v9z6732b.fsf@gnu.org>
[not found] ` <<<376d5335-eb80-4272-8847-e764242a02b7@default>
[not found] ` <<<83r29u70cy.fsf@gnu.org>
[not found] ` <<c1e7f520-7dff-41e0-ba01-9828b87cb703@default>
[not found] ` <<83imv66vi2.fsf@gnu.org>
2019-04-22 13:23 ` Drew Adams
2019-04-22 13:33 ` Eli Zaretskii
[not found] ` <<83y34273mu.fsf@gnu.org>
2019-04-22 10:58 ` Drew Adams
2022-04-29 12:01 ` Lars Ingebrigtsen
2022-04-29 17:13 ` Juri Linkov
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=96cafba3-7ba2-4e87-8f9d-e53825fd1dde@default \
--to=drew.adams@oracle.com \
--cc=35353@debbugs.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).