From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: [NEW PATCH] mouse-1 click follows link
Date: Sat, 18 Dec 2004 13:50:31 +0000 (UTC) [thread overview]
Message-ID: <m1Cfeyd-0004QXC@rattlesnake.com> (raw)
In-Reply-To: <E1CfSKG-00082m-O7@fencepost.gnu.org> (message from Richard Stallman on Fri, 17 Dec 2004 19:20:00 -0500)
When you write new documentation for `mouse-1 click follows link',
please remember to tell people about
Mouse-1 between the first character of a link and the previous,
Mouse-3 between the last character of a link and the next,
and Mouse-3 to paste the link
i.e.,
mouse-set-point
mouse-save-then-kill
mouse-yank-at-click
This is long established and useful since it works when a drag tends
to bring in extranous characters. And copying links is common.
As far as I can see, a problem sometimes occurs when people are
confused by the position of point: with some cursors, novices think it
is `on' a character rather than before it.
In particular, people are occasionally confused by a `box' cursor
shape that looks as if they are putting point `on the character'
rather than between that character and the previous character.
(After you learn what a `box' signifies, it becomes a good text cursor
since it remains visible, but not irritating so long as it does not
blink. On the other hand, a `bar' does not have the positioning
problem, but is less visible unless it blinks, in which case, it
becomes too visible for many. Setting a non-blinking bar cursor to
another color fails on a black and white display, so that is not an
option. As far as I can see, good documentation is the best
solution.)
Thank you.
--
Robert J. Chassell
bob@rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.rattlesnake.com http://www.teak.cc
next prev parent reply other threads:[~2004-12-18 13:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 13:04 [PATCH] mouse-1 click follows link Kim F. Storm
2004-10-29 23:54 ` Luc Teirlinck
2004-10-30 22:04 ` Kim F. Storm
2004-10-31 0:09 ` Luc Teirlinck
2004-10-31 12:49 ` Kim F. Storm
2004-11-01 7:24 ` Richard Stallman
2004-10-31 0:34 ` Luc Teirlinck
2004-10-31 12:53 ` Kim F. Storm
2004-10-31 15:24 ` Luc Teirlinck
2004-10-31 18:37 ` David Kastrup
2004-10-31 20:03 ` Luc Teirlinck
2004-10-31 20:13 ` David Kastrup
2004-10-31 21:40 ` Stefan
2004-10-31 23:39 ` Kim F. Storm
2004-11-01 0:33 ` Stefan
2004-11-27 0:44 ` [NEW PATCH] " Kim F. Storm
[not found] ` <E1CYJ5T-0002qS-UR@fencepost.gnu.org>
2004-12-14 15:15 ` Kim F. Storm
2004-12-14 20:13 ` Robert J. Chassell
2004-12-14 23:33 ` Kim F. Storm
2004-12-16 23:08 ` Kevin Rodgers
2004-12-17 9:57 ` Kim F. Storm
2004-12-17 10:20 ` Alex Schroeder
2004-12-15 8:46 ` Richard Stallman
2004-12-16 12:24 ` Richard Stallman
2004-12-16 15:12 ` Kim F. Storm
2004-12-18 0:20 ` Richard Stallman
2004-12-18 13:50 ` Robert J. Chassell [this message]
2004-12-17 15:48 ` Kim F. Storm
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=m1Cfeyd-0004QXC@rattlesnake.com \
--to=bob@rattlesnake.com \
/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).