GNU bug report logs - #35353
26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major mode name

Previous Next

Full log

Message #128 received at 35353 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 35353 <at> debbugs.gnu.org
Subject: Re: bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2)
 major mode name
Date: Fri, 29 Apr 2022 14:01:06 +0200

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

> 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? 

I've now fixed this in Emacs 29.

> 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.

That is pretty unusual naming for a major mode, but I don't think it's
worth changing at this point.

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.