From: Mirko <mvukovic@nycap.rr.com>
To: help-gnu-emacs@gnu.org
Subject: Re: trouble binding to <next> & <prior>
Date: Mon, 7 Jul 2008 10:32:03 -0700 (PDT) [thread overview]
Message-ID: <695c3ff5-6562-429b-a0b6-6c4e2a3ed040@z66g2000hsc.googlegroups.com> (raw)
In-Reply-To: 87r6a5tytp.fsf@hubble.informatimago.com
On Jul 7, 12:59 pm, p...@informatimago.com (Pascal J. Bourguignon)
wrote:
> Mirko <mvuko...@nycap.rr.com> writes:
> > Hello,
>
> > I have a following keybinding, parts of which do not work. In
> > particular I am trying to bind view-previous-entry to the page-up key
> > on the standard PC keyboard (using Emacs 22.1). I used both h-k and h-
> > l to determine that this key is identified with "<prior>" & <next>".
>
> > (defvar iop-alert-mode-map nil
> > "Keymap for IOP-alert mode")
> > (unless iop-alert-mode-map
> > (setq iop-alert-mode-map (copy-keymap text-mode-map))
> > (define-key iop-alert-mode-map (kbd "<prior>") 'view-previous-entry)
> > (define-key iop-alert-mode-map (kbd "<next>") 'view-next-entry)
> > (define-key iop-alert-mode-map (kbd "d") 'mark-entry-for-deletion)
> > (define-key iop-alert-mode-map "m" 'mark-entry-for-save))
>
> > When in a buffer with iop-alert mode, doing h-m gives me the following
> > output on keybindings:
> > ... stuff skipped
> > < n e Prefix Command
> > < p r Prefix Command
> > < n e x Prefix Command
> > < p r i Prefix Command
> > < n e x t Prefix Command
> > < p r i o Prefix Command
> > < n e x t > view-next-entry
> > < p r i o r Prefix Command
> > < p r i o r > view-previous-entry
>
> > It seems <prior> and <next> are bound to the character sequence
> > "<prior>" and "<next>". Pressing those characters will invoke the
> > commands. But pressing the Page-up/down keys will not.
>
> > Indeed, doing a h-k shows that page-up/down are still bound to scroll
> > up/down.
>
> > What am I doing wrong?
>
> emacs-version --> "22.2.1"
> (kbd "<prior>") --> [prior]
>
> if you don't get this vector with one symbol for (kbd "<prior>"),
> indeed you have a problem.
>
> --
> __Pascal Bourguignon__ http://www.informatimago.com/
>
> WARNING: This product warps space and time in its vicinity.
I tried that, and I get exactly as you suggested.
(kbd "<prior>") --> [prior]
Mirko
next prev parent reply other threads:[~2008-07-07 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 15:37 trouble binding to <next> & <prior> Mirko
2008-07-07 16:59 ` Pascal J. Bourguignon
2008-07-07 17:32 ` Mirko [this message]
2008-07-07 18:09 ` Lennart Borgman (gmail)
[not found] ` <mailman.14341.1215454191.18990.help-gnu-emacs@gnu.org>
2008-07-07 18:59 ` Mirko
2008-07-07 20:04 ` Lennart Borgman (gmail)
2008-07-08 2:00 ` Kevin Rodgers
2008-07-08 3:34 ` Xah
2008-07-09 16:32 ` Mirko
[not found] ` <mailman.14345.1215461048.18990.help-gnu-emacs@gnu.org>
2008-07-08 12:49 ` Mirko
2008-07-08 17:26 ` Lennart Borgman (gmail)
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=695c3ff5-6562-429b-a0b6-6c4e2a3ed040@z66g2000hsc.googlegroups.com \
--to=mvukovic@nycap.rr.com \
--cc=help-gnu-emacs@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.