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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 35353 <at> debbugs.gnu.org, dgutov <at> yandex.ru
Subject: Re: bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major
 mode name
Date: Mon, 22 Apr 2019 16:05:09 +0300

> Date: Mon, 22 Apr 2019 05:23:17 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: dgutov <at> yandex.ru, 35353 <at> debbugs.gnu.org
> 
> > FWIW, I see no important reasons to set point in XREF buffers by
> > clicking the mouse.
> 
> It's always important to be able to set point by
> clicking the mouse.

I disagree.  And it's easy to disagree, because you didn't provide any
rationale, none at all.

> Do you think that buffer *xref* is different in this
> regard from Dired, compilation, or Occur buffers?
> How so?  These are buffers that are dense with links,
> making it important that users can use the mouse not
> only to follow links but also to set point.

There are no links in the XREF buffer, not really.  This buffer is an
aid to select on of several possible symbols, that's all.

Previous Next

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