unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: Bug in Info - can use mouse to click links (w32)
Date: Sat, 8 Jan 2005 20:05:21 +0100	[thread overview]
Message-ID: <001401c4f5b5$08482cd0$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 01c4f58c$Blat.v2.2.2$5b3764c0@zahav.net.il

----- Original Message ----- 
From: "Eli Zaretskii" <eliz@gnu.org>

> > Left-clicking with the mouse on a link in Info does not follow the link.
I
> > suppose they should so I consider this an error.
>
> FWIW, this is by design.  In Emacs, mouse-2 follows a link (any link,
> including those in Dired, *Help* and *Compilation* buffers, etc.).
>
> > The links at the top of the Info pages are an exception. Left-clicking
with
> > the mouse on those follows the links.
>
> Also by design.

Thanks, but I think this is confusing, both because the links behaves
differently and because it differs from what other GUI:s (web browsers) do.
I believe the documentation GUI should be as intuitive as possible if we
want to attract new users.

I did not follow the discussion previously all the way. I however got the
impression that the points above where important.

BTW is mouse-2 the middle button? As previously many have pointed out there
are no such button on very many pc:s.

  reply	other threads:[~2005-01-08 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 11:22 Bug in Info - can use mouse to click links (w32) Lennart Borgman
2005-01-08 14:13 ` Eli Zaretskii
2005-01-08 19:05   ` Lennart Borgman [this message]
2005-01-08 19:35     ` Vinicius Jose Latorre
2005-01-08 22:44       ` Eli Zaretskii
2005-01-08 20:04     ` Eli Zaretskii
2005-01-08 20:10     ` Kim F. Storm
2005-01-08 22:31       ` Eli Zaretskii
2005-01-08 23:34         ` Kim F. Storm
2005-01-08 23:42       ` Lennart Borgman
2005-01-09  3:22   ` 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='001401c4f5b5$08482cd0$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    --cc=emacs-devel@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).