all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Drew Adams <drew.adams@oracle.com>, 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 07:08:55 +0200	[thread overview]
Message-ID: <44F7C067.2070607@student.lu.se> (raw)
In-Reply-To: <jwvirk88hpn.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
>> 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.
>>     
>
> But here you're bumping into a core design guideline of Emacs, which is to
> make things as transparent as possible: the internal names are generally
> both used internally (of course) and made visible to the end user.
> So changing the end user side will have impacts on the internal side as
> well, so it can't be changed as easily as you may think.
>
> Whether that's good or bad is up to you, but it's a bit late to change it,
>   
The principle to have things as transparent as possible is a good one, 
but so is to use understandable names for end users.

What is needed is a translation from the internal symbol names to 
physical keyboard key names in `single-key-description'. Such a 
translation should of course be possible to turn off.

Do you think this is a very big change? Does it disturb the transparency 
very much?

  reply	other threads:[~2006-09-01  5:08 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 [this message]
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=44F7C067.2070607@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=drew.adams@oracle.com \
    --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 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.