From: "Drew Adams" <drew.adams@oracle.com>
To: <3517@emacsbugs.donarmstrong.com>, <emacs-pretest-bug@gnu.org>
Subject: bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
Date: Tue, 9 Jun 2009 10:18:47 -0700 [thread overview]
Message-ID: <93F64197B7034F649088B05DA04B1C1A@us.oracle.com> (raw)
In-Reply-To: <D3B8803CFA1246AE9AEA0868FD37F46B@us.oracle.com>
Likewise, the manual uses sometimes `Mouse-1', sometimes `mouse-1' (likewise,
-2, -3).
The latter is preferable, again because it is more readable and better reflects
the Emacs-Lisp terminology.
next prev parent reply other threads:[~2009-06-09 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y6s0ce48.fsf@cyd.mit.edu>
2009-06-09 16:39 ` bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP> Drew Adams
2009-06-09 17:18 ` Drew Adams [this message]
2009-06-10 15:25 ` bug#3517: marked as done (23.0.94; Emacs manual: <PageUp>, <PAGEUP>) Emacs bug Tracking System
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=93F64197B7034F649088B05DA04B1C1A@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3517@emacsbugs.donarmstrong.com \
--cc=emacs-pretest-bug@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).