From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Why are <next> and <prior> not called <page down> and <page up>?
Date: Fri, 01 Sep 2006 00:19:39 +0200 [thread overview]
Message-ID: <44F7607B.6040902@student.lu.se> (raw)
In-Reply-To: <EIENLHALHGIMHGDOLMIMOEPKCKAA.drew.adams@oracle.com>
Drew Adams wrote:
> > > <prior> and <next> are standard names, which means that users
> > > can find things out about them (e.g. Google).
> >
> > Are you seriously saying that it is more simple to find
> > something about
> > the usage of these keys if you use "next" than "page down"?
> >
> > Well, I don't know whether it is easier to search for one or
> > the other. The point is that one is a standard name, so _if_
> > you can find doc on it then you have found doc about many things
> > (e.g. apps) involving that key.
>
> Can you please explain what standard you refer to?
>
> Didn't Stefan mention X11?
>
Thanks, but then we are talking about different levels. You refer to a
technical level. I am more interested in what the user sees, the
physical keyboard. I think it is easier to understand and remember for
users if we refer to the physical keyboard. This is also very standard
today.
> Are they not mostly called "left arrow" etc? Talking about them
> together as just "up, down, left, right" makes it rather easy to
> understand I guess. At least that was the case for me.
>
> And yet you had trouble getting from Page Down to Next?
>
Yes, absolutely.
> To be clear, we need to give them unique names. And since they already have
> unique names, from the standard, why not use those? And, then, why use those
> standard names in some cases but not in others?
>
Of course we should use good standard technical names internally. I
guess X11 is good for this since Stefan mentioned it. But for
communication with the users refering to the physical keyboard is in my
opinion better.
Having different names is a bit complex of course, but I do not believe
it can be more simple than that (and you have given good reasons for that).
> It's the signal sent by the physical key that's important, no? How can you
> even tell if your keyboard has an `prior' key - do you just look for a Page
> Up label? That might not be sufficient, depending on what that key is mapped
> to.
>
No problem on a standard pc I guess.
next prev parent reply other threads:[~2006-08-31 22:19 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 [this message]
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=44F7607B.6040902@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@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 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).