unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
@ 2009-06-09 16:39 ` Drew Adams
  2009-06-09 17:18   ` Drew Adams
  2009-06-10 15:25   ` bug#3517: marked as done (23.0.94; Emacs manual: <PageUp>, <PAGEUP>) Emacs bug Tracking System
  0 siblings, 2 replies; 3+ messages in thread
From: Drew Adams @ 2009-06-09 16:39 UTC (permalink / raw)
  To: emacs-pretest-bug

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.
 
 
 






^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
  2009-06-09 16:39 ` bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP> Drew Adams
@ 2009-06-09 17:18   ` Drew Adams
  2009-06-10 15:25   ` bug#3517: marked as done (23.0.94; Emacs manual: <PageUp>, <PAGEUP>) Emacs bug Tracking System
  1 sibling, 0 replies; 3+ messages in thread
From: Drew Adams @ 2009-06-09 17:18 UTC (permalink / raw)
  To: 3517, emacs-pretest-bug

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.






^ permalink raw reply	[flat|nested] 3+ messages in thread

* bug#3517: marked as done (23.0.94; Emacs manual: <PageUp>, <PAGEUP>)
  2009-06-09 16:39 ` bug#3517: 23.0.94; Emacs manual: <PageUp>, <PAGEUP> Drew Adams
  2009-06-09 17:18   ` Drew Adams
@ 2009-06-10 15:25   ` Emacs bug Tracking System
  1 sibling, 0 replies; 3+ messages in thread
From: Emacs bug Tracking System @ 2009-06-10 15:25 UTC (permalink / raw)
  To: Chong Yidong

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]


Your message dated Wed, 10 Jun 2009 11:17:27 -0400
with message-id <87y6s0ce48.fsf@cyd.mit.edu>
and subject line Re: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
has caused the Emacs bug report #3517,
regarding 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
3517: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3517
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3834 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-pretest-bug@gnu.org>
Subject: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
Date: Tue, 9 Jun 2009 09:39:48 -0700
Message-ID: <D3B8803CFA1246AE9AEA0868FD37F46B@us.oracle.com>

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.
 
 
 



[-- Attachment #3: Type: message/rfc822, Size: 1090 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 3517-done@emacsbugs.donarmstrong.com
Subject: Re: 23.0.94; Emacs manual: <PageUp>, <PAGEUP>
Date: Wed, 10 Jun 2009 11:17:27 -0400
Message-ID: <87y6s0ce48.fsf@cyd.mit.edu>

Fixed, thanks.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-06-10 15:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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
2009-06-10 15:25   ` bug#3517: marked as done (23.0.94; Emacs manual: <PageUp>, <PAGEUP>) Emacs bug Tracking System

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).