unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
	Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Why are <next> and <prior> not called <page down> and <page up>?
Date: Thu, 31 Aug 2006 18:09:42 +0100	[thread overview]
Message-ID: <44F717D6.2010604@gnu.org> (raw)
In-Reply-To: <jwvmz9kam0s.fsf-monnier+emacs@gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]

Stefan Monnier wrote:
>> Why does not key-description use the names <page down> and <page up>?
>>     
>
> 'Cause X11 calls them `prior' and `next'?
>   
As does MS Windows at the API level, but these messages are intended for 
end users, not programmers, so it is better to follow how the keys are 
labelled on the majority of modern keyboards than the names used in the 
header files.

Personally, the last time I saw these keys labelled Next and Prior was 
in 1992. Since then, every keyboard I have used has labelled them Page 
Up/Page Down or PgUp/PgDn or some other abbreviation.

But I wouldn't suggest changing this until after the release, as it 
probably affects lots of documentation, even if we keep the old names as 
aliases for backwards compatibility.


[-- Attachment #1.2: Type: text/html, Size: 1183 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2006-08-31 17:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 15:57 Why are <next> and <prior> not called <page down> and <page up>? Lennart Borgman
2006-08-31 16:49 ` Stefan Monnier
2006-08-31 17:09   ` Jason Rumney [this message]
2006-08-31 18:55     ` Lennart Borgman
2006-08-31 20:34       ` Drew Adams
2006-08-31 20:45         ` Lennart Borgman
2006-08-31 21:10           ` Drew Adams
2006-08-31 21:31             ` Lennart Borgman
2006-08-31 22:00               ` Drew Adams
2006-08-31 22:19                 ` Lennart Borgman
2006-09-01  2:06                   ` Stefan Monnier
2006-09-01  5:08                     ` Lennart Borgman
2006-09-01  6:29                       ` Lennart Borgman
2006-09-01 17:00                       ` Stefan Monnier
2006-09-01  0:47         ` David Abrahams
2006-09-01  9:12       ` Eli Zaretskii
2006-09-01 21:57         ` Lennart Borgman
2006-09-01 22:31           ` Drew Adams
2006-09-02  7:05             ` David Kastrup
2006-09-02  7:53               ` Lennart Borgman
2006-09-02 13:46                 ` Drew Adams
2006-09-03 14:53                   ` Lennart Borgman
2006-09-03 15:49                     ` Drew Adams
2006-09-02 21:49           ` Jason Rumney
2006-09-03 14:52             ` Lennart Borgman
2006-09-05 20:06               ` Kevin Rodgers

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=44F717D6.2010604@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    /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).