From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Why are <next> and <prior> not called <page down> and <page up>?
Date: Fri, 1 Sep 2006 15:31:43 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMIEACCLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <44F8ACC7.60906@student.lu.se>
May I then suggest a little smaller change for this instead? Could we
have a human readable table with translations from internal key names
like <paste>, <next> to standard keyboard names? Just those names that
differ should go into the table of course.
That's a good suggestion. It should be phrased in terms of "often used as
labels on many keyboards" etc., to avoid giving the impression that this is
standard; it is common among many keyboards, but it is by no means standard
(there is no standard for such labels AFAIK).
next prev parent reply other threads:[~2006-09-01 22:31 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
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 [this message]
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=EIENLHALHGIMHGDOLMIMIEACCLAA.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 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).