unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
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 13:00:05 -0400	[thread overview]
Message-ID: <jwvlkp37chq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <44F7C067.2070607@student.lu.se> (Lennart Borgman's message of "Fri, 01 Sep 2006 07:08:55 +0200")

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

Well, the question is: how should people figure out the piece of elisp code
they should add in their .emacs in order to bind something to "page up".
A common way to do it is C-h c <page-up> and the response will currently say
"<prior>" but your suggestion would replace it with "<page-up>", so then
we'd need to make sure that this can be passed to define-key, probably via
`kbd', so we'd have to adjust kbd as well, at least.  Also until now you
could do the translation by hand rather than use `kbd' and just pass [prior]
to define-key but [page-up] won't work, ...

It's not like it can't be done, but current expectations tend to make such
a thing into a special exception, which may generate at least as much
trouble as it's intended to solve.  Then again, maybe not, I don't
actually know.  I'm just pointing out that it's not nearly as simple as
it seems.


        Stefan

  parent reply	other threads:[~2006-09-01 17:00 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 [this message]
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=jwvlkp37chq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).