all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Why are <next> and <prior> not called <page down> and <page up>?
Date: Thu, 31 Aug 2006 13:34:46 -0700	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMMEPJCKAA.drew.adams@oracle.com> (raw)
In-Reply-To: <44F730BD.9000403@student.lu.se>

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

    I suggest changing them at once. 14 years is a long wait. I think
    changing this makes it much easier for new users.

    Would it be terribly difficult to try to change it in the documentation?

Sorry to disagree, but I don't think this is a good idea. I share the desire
to make things more user-friendly, and I agree that it would be good to
somehow indicate that the keys involved might be labeled Page Up and Page
Down (or PgUp and PgDn or...) on your keyboard, but <prior> and <next> are
standard names, which means that users can find things out about them (e.g.
Google).

What might help would be to explain in the doc (if this is not already done)
that <prior> and <next> often correspond to keys labeled Page Up and Page
Down. Beyond that, I think it's better for users to learn to recognize the
(standard) names of these keys.

A standard, however poorly named it might be, is an entry to lots of help on
the Internet. If you hide the standard name from users, then you hide that
key from users, leaving them locked out of useful information.

Also, this is not something that affects only the documentation; the UI
refers to these keys by their standard names - as it should, IMO.

Finally, "next" and "prior" are _not_ bad names for these keys, especially
for Emacs. The most common action associated with them (unmodified) is "next
_page_" and "prior _page_", but different Emacs buffers and functions can
give these next and prior keys different associations. The abstract notion
of "next" and "prior" (or previous or preceding) is what is important.

This is similar to the case for `up' and `down' (and `left' and `right').
Those keys are often labeled with arrows, but imagine if they, like Page Up,
were labeled Line Up and Line Down. The more generic names `up', `down',
`next', and `prior' are superior, precisely because they are more generic.
Add a modifier key, and Page Up might no longer mean "page up"; it might
mean "paragraph up" or something else. Or change Emacs modes, and Page Up
might mean "prior buffer" instead of prior line. You get the idea: it is
Page Down, not Next, that is, in fact, a bad name. Of course, we can't
change how keys are labeled...

  reply	other threads:[~2006-08-31 20:34 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
2006-08-31 18:55     ` Lennart Borgman
2006-08-31 20:34       ` Drew Adams [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EIENLHALHGIMHGDOLMIMMEPJCKAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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.