all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 35353@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major mode name
Date: Mon, 22 Apr 2019 05:23:17 -0700 (PDT)	[thread overview]
Message-ID: <c1e7f520-7dff-41e0-ba01-9828b87cb703@default> (raw)
In-Reply-To: <<83r29u70cy.fsf@gnu.org>>

> > > FWIW, I don't see that as a serious issue in this case.  Feel free to
> > > close as wontfix, if you want.
> >
> > Seriously?  Mouse-2 was the original way to follow
> > links.  And ubiquitously in Emacs users need to be
> > able to set point.  They should be able to do so
> > using `mouse-1'.
> 
> 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.

That's the reason why even when `mouse-1' follows
a link we let users instead set point using `mouse-1'
by just holding it pressed longer before releasing it.

And it's the reason we have option
`mouse-1-click-follows-link': to let users not have
`mouse-1' follow links with a non-slow click.

And it's the reason the manual establishes the
convention.  As it says (quoted more extensively
earlier):

 Many special major modes, like Dired, Info, Compilation,
 and Occur, are designed to handle read-only text that
 contains "hyper-links".

It is precisely in these contexts - of which buffer
*xref* is one, that it is important to respect option
`mouse-1-click-follows-link'.

That's the point of that passage.  Users need to be
able to follow links, but they also need to be able
to set point.  How they do one or the other is
decided by their individual preference, using option
`mouse-1-click-follows-link'.

And I pointed out in the original report specifically
how the bug is a problem for users with the option nil:

It's impossible to click `mouse-1' anywhere inside the
window to select it, set point, and focus its frame
(unless you can find and click the file line preceding
a boatload of links - and that line might even be
outside the window, in which case you're completely
out of luck).

> > Not to mention that this violates the explicit Emacs
> > convention (cited earlier).
> 
> It doesn't, your citation is not necessarily relevant to the issue at
> hand.

Why do you think so?  I think it is exactly relevant -
see above.

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.





  parent reply	other threads:[~2019-04-22 12:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21  2:50 bug#35353: 26.2; Buffer *xref*: (1) hard-coded mouse-1, (2) major mode name Drew Adams
2019-04-21 13:27 ` 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 [this message]
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

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

  git send-email \
    --in-reply-to=c1e7f520-7dff-41e0-ba01-9828b87cb703@default \
    --to=drew.adams@oracle.com \
    --cc=35353@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@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 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.