unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: follow-link in grep buffer
Date: Sat, 26 Feb 2005 14:53:00 +0100	[thread overview]
Message-ID: <v9vf8f2zsz.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: x5vf8g7mta.fsf@lola.goethe.zz

On Fri, Feb 25 2005, David Kastrup wrote:

> I would recommend not making any behavior by default dependent on the
> single-click length, nor on the focus situation: both approaches are
> completely obfuscate and confusing.
>
> So the change to 21.4 behavior would be the following:
>
> a) a double-click on a location that has no double-click binding, but
>    a local mouse-2 binding, will execute the mouse-2 binding.  This
>    will make double-clicks, where not overriden, follow links without
>    further code changes compared to 21.4
> b) setting an explicit link property will _additionally_ remap mouse-1
>    to mouse-2.  I would not by default make this dependent on anything
>    else.

I agree with David's arguments and his suggestions.

I also find the current behavior confusing in some modes.  After
several week, I still sometimes follow the link when I intended to
select the window or set the point.

Some examples: In Gnus Group buffer, I often want to put the cursor on
a certain group and then I intend to do `C-u a' (post to group under
point), `10 RET' (show 10 article in that group), M-g (Check for new
news in the current topic.).  In PCL-CVS, I often want to put the
point on a file name and then do `=' (cvs-mode-diff), `l'
(cvs-mode-log) ...

Because I followed the discussions on emacs-devel, I remembered why
mouse-1 behaves like this, but I think for ordinary users it is really
surprising.

In modes like info, mouse-1 to follow a link is a good default.

> So grep should not set the link property in my opinion in this scheme,
> and gnus should set it sparingly: on MIME buttons it generates itself,
> but not on header lines or things looking like a link in the article
> text.

It should not be set (by default) in the group and summary buffer.  As
for the MIME buttons and other links in the article buffer: AFAICS,
these are the same kind of all "buttons", so it might require some
work.

[...]
> Telling them "use mouse-2" has always been sort of embarrassing.
> Telling them "use mouse-1, but don't press it longer than 200
> milliseconds if you want to follow the link, and it won't work if you
> have not the focus" will kill the "Emacs is usable for common human"
> proposition dead.

ACK.  In Gnus group buffer, I often found myself clicking too short so
that the key presses intended for the group buffer were executed in
the summary buffer and thus triggered completely different actions.

> Telling people "double click to follow some possible cross
> connection" will make them feel at home.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

  reply	other threads:[~2005-02-26 13:53 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 21:08 follow-link in grep buffer Nick Roberts
2005-02-21 21:19 ` Stefan Monnier
2005-02-21 22:48   ` Nick Roberts
2005-02-22  0:08     ` Drew Adams
2005-02-22  9:48       ` Kim F. Storm
2005-02-22 13:41         ` Stefan Monnier
2005-02-22 14:24           ` Kim F. Storm
2005-02-22 14:25           ` Kim F. Storm
2005-02-22 17:33         ` Drew Adams
2005-02-22  0:48     ` Jason Rumney
2005-02-21 21:45 ` Drew Adams
2005-02-21 22:20   ` Luc Teirlinck
2005-02-21 22:36     ` Nick Roberts
2005-02-21 22:46     ` David Kastrup
2005-02-21 23:00       ` Luc Teirlinck
2005-02-21 23:05       ` Luc Teirlinck
2005-02-21 23:42         ` David Kastrup
2005-02-22  0:00           ` Drew Adams
2005-02-21 23:07       ` Luc Teirlinck
2005-02-22  0:44       ` Jason Rumney
2005-02-22  1:26         ` David Kastrup
2005-02-21 23:06     ` Drew Adams
2005-02-21 21:45 ` Lennart Borgman
2005-02-21 21:46 ` David Kastrup
2005-02-21 22:46   ` Kim F. Storm
2005-02-21 23:22     ` Luc Teirlinck
2005-02-22 18:11 ` Richard Stallman
2005-02-25  6:51   ` Nick Roberts
2005-02-25  9:46     ` David Kastrup
2005-02-25 11:12       ` Kim F. Storm
2005-02-25 12:55         ` Stefan Monnier
2005-02-25 13:25           ` Lennart Borgman
2005-02-25 13:40             ` Kim F. Storm
2005-02-25 14:20             ` Andreas Schwab
2005-02-25 13:37           ` Kim F. Storm
2005-02-25 14:10             ` David Kastrup
2005-02-26 13:53               ` Reiner Steib [this message]
2005-02-27  0:32               ` Richard Stallman
2005-02-25 16:33             ` Stefan Monnier
2005-02-25 16:47               ` David Kastrup
2005-02-25 16:59                 ` Stefan Monnier
2005-02-25 23:05                 ` Lennart Borgman
2005-02-25 16:37             ` Drew Adams
2005-02-25 18:09               ` David Kastrup
2005-02-25 19:44                 ` Drew Adams
2005-02-25 20:07                   ` Stefan Monnier
2005-02-25 20:32                     ` David Kastrup
2005-02-25 20:53                     ` Drew Adams
2005-02-25 20:27                   ` David Kastrup
2005-02-25 21:24                     ` Robert J. Chassell
2005-02-25 23:34                     ` Drew Adams
2005-02-26  0:44                       ` David Kastrup
2005-02-26  1:18                         ` Drew Adams
2005-02-25 23:35         ` Kim F. Storm
2005-02-26  2:28           ` Stefan Monnier
2005-02-26  2:50             ` David Kastrup
2005-02-26  3:32               ` Stefan Monnier
2005-02-26 22:24             ` Kim F. Storm
2005-02-27  2:00               ` Stefan Monnier
2005-02-27  8:26                 ` Lennart Borgman
2005-02-27 21:46                   ` Stefan Monnier
2005-02-27 22:09                     ` Kim F. Storm
2005-02-28  1:03                     ` Nick Roberts
2005-02-25 22:53       ` Richard Stallman
2005-02-26  0:16         ` David Kastrup
2005-02-26 22:44           ` Kim F. Storm
2005-02-25 22:52     ` Richard Stallman

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=v9vf8f2zsz.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).