unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [NEW PATCH] mouse-1 click follows link
Date: Fri, 17 Dec 2004 19:20:00 -0500	[thread overview]
Message-ID: <E1CfSKG-00082m-O7@fencepost.gnu.org> (raw)
In-Reply-To: <m3pt1aqntt.fsf@kfs-l.imdomain.dk> (storm@cua.dk)

    > It is not just historical reasons.  Mouse-2 fits in better with the
    > usual Emacs mouse bindings than Mouse-1.  We've decided to give higher
    > priority to compatibility with other programs, at the cost of fitting
    > in not quite as well.

    Should I mention that in the manual?

There's no need for the manual to concern itself with previous
versions of Emacs except in the Antinews section.  However, explaining
briefly the motivation for what the current version does is useful
when it is interesting to the reader.  So if you see a reason/occasion
to do that, please try it.

    > I suggest you grep for Mouse-2 and for Mouse-1, and change the places
    > that need changing.

    What should I change them to?

That question has no general answer.  How to change the text depends, in
each case, on the details of the situation.

    Should I mention both Mouse-1 and Mouse-2?

Probably in most cases only Mouse-1.  But it partly depends
on what reads well and what would be interesting to the reader.

    Should I mention mouse-1-click-follows-link (every time)?

It would be boring and wasteful to repeat it in each of these places
where Mouse-1 gets a brief mention.  Rather, find one central place to
talk about this option.  Perhaps the section that explains the basic
general mouse commands could also talk about the convention for mouse
link following and the options that affect it.

    Should I mention that a long mouse-1 click still sets point
    (depending on the setting of mouse-1-click-follows-link)?

Try to put that in the one general explanation and see if it works.

  reply	other threads:[~2004-12-18  0:20 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 [this message]
2004-12-18 13:50                     ` Robert J. Chassell
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=E1CfSKG-00082m-O7@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).