From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: [NEW PATCH] mouse-1 click follows link
Date: Fri, 17 Dec 2004 16:48:55 +0100 [thread overview]
Message-ID: <m3mzwd7wns.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1Ceugl-00036t-8G@fencepost.gnu.org> (Richard Stallman's message of "Thu, 16 Dec 2004 07:24:59 -0500")
Richard Stallman <rms@gnu.org> writes:
> Should I install these changes (with proper doc string)?
>
> Yes, please do.
Done.
I also added some text to NEWS -- please review.
>
> But what about the Emacs manual? Would a it suffice to put a generic
> mentioning like this somewhere (I would add this to NEWS as well):
>
> I suggest you grep for Mouse-2 and for Mouse-1, and change the places
> that need changing.
I will work on updating the manuals over the next few days.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
prev parent reply other threads:[~2004-12-17 15:48 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
2004-12-17 15:48 ` Kim F. Storm [this message]
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=m3mzwd7wns.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).