From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
Date: Tue, 9 Jun 2009 09:39:48 -0700 [thread overview]
Message-ID: <D3B8803CFA1246AE9AEA0868FD37F46B@us.oracle.com> (raw)
emacs -Q
C-h r
C-s pageup C-s C-s...
Nodes Notation Used
---- -------------
Moving Point, Completion Commands `<PageUp>'
Minibuffer Edit `M-<PAGEUP>'
Scrolling `<PAGEUP>', <PageUp> (both)
Insert in Picture `C-c <PAGEUP>'
Key Index PAGEUP
Likewise, for pagedown. These two key names should be mentioned only
once, as synonyms for `<next>' and `<prior>', which are preferable
because the Emacs-Lisp symbols used for these function keys are `next'
and `prior'. In any case, we should not use one term (e.g. `<next>')
in some places and in other places use another term (e.g.
`<PAGEDOWN>'). That is confusing and impedes learning.
Also, sometimes we write `<prior>', sometimes (e.g. nodes `Scrolling',
`Completion Commands') we write `<PRIOR>'. We should be consistent.
We should always use `<prior>', both for readability and to reflect
the Emacs-Lisp function-key symbol, which aids learning.
Also, in node `Moving Point', `M-v' is written also as <M-v>. This is
non-standard, AFAIK.
next reply other threads:[~2009-06-09 16:39 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 ` Drew Adams [this message]
2009-06-09 17:18 ` bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP> Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D3B8803CFA1246AE9AEA0868FD37F46B@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.