From: Brandeis King <brandeis.a.king@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Page Up/Down Issues With Emacs in Terminal
Date: Wed, 6 Jul 2016 12:40:58 -0700 (PDT) [thread overview]
Message-ID: <37ca21a2-8218-41c0-acd4-98696c7f8746@googlegroups.com> (raw)
In-Reply-To: <mailman.670.1467818895.26859.help-gnu-emacs@gnu.org>
On Wednesday, July 6, 2016 at 11:28:18 AM UTC-4, Yuri Khan wrote:
> Neither could I. Moreover, when I start "TERM=tmux emacs -Q -nw", the
> variable input-decode-map still contains a sequence for ESC [ 5 ~. I
> presumed it were added by xterm.el and that by setting a TERM which
> Emacs doesn’t know about would prevent that, but it seems at least one
> of those assumptions is false.
>
> @Brandeis: Please also show us what you get when you press Ctrl+V PgUp
> at the zsh prompt, and what you have in the input-decode-map variable
> in emacs -Q -nw.
I tried "emacs -Q -nw" again today, and the page up/down buttons do work as expected.
In answer to previously asked questions, term is "screen-256color" -- this is set in my Xresources file -- Ctrl+V PgUp prints ^[[5~
Input-Decode Map variable holds:
Value: (keymap
(27 keymap
(79 keymap
(83 .
[f4])
(82 .
[f3])
(81 .
[f2])
(80 .
[f1])
(66 .
[down])
(67 .
[right])
(65 .
[up])
(68 .
[left]))
(91 keymap
(53 keymap
(126 .
[prior]))
(54 keymap
(126 .
[next]))
(90 .
[backtab])
(51 keymap
(126 .
[deletechar]))
(50 keymap
(52 keymap
(126 .
[f12]))
(51 keymap
(126 .
[f11]))
(49 keymap
(126 .
[f10]))
(48 keymap
(126 .
[f9]))
(126 .
[insertchar]))
(52 keymap
(126 .
[end]))
(49 keymap
(57 keymap
(126 .
[f8]))
(56 keymap
(126 .
[f7]))
(55 keymap
(126 .
[f6]))
(53 keymap
(126 .
[f5]))
(126 .
[home])))))
next prev parent reply other threads:[~2016-07-06 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 20:57 Page Up/Down Issues With Emacs in Terminal Brandeis King
2016-07-05 21:44 ` Emanuel Berg
2016-07-06 2:14 ` Brandeis King
2016-07-06 2:59 ` Emanuel Berg
2016-07-06 7:37 ` Yuri Khan
[not found] ` <mailman.639.1467790653.26859.help-gnu-emacs@gnu.org>
2016-07-06 14:28 ` Emanuel Berg
2016-07-06 15:27 ` Yuri Khan
[not found] ` <mailman.670.1467818895.26859.help-gnu-emacs@gnu.org>
2016-07-06 19:40 ` Brandeis King [this message]
2016-07-07 4:47 ` Yuri Khan
2016-07-05 21:48 ` Emanuel Berg
2016-07-05 22:23 ` Dmitry Alexandrov
[not found] ` <mailman.627.1467757409.26859.help-gnu-emacs@gnu.org>
2016-07-05 22:39 ` Emanuel Berg
2016-07-05 22:56 ` Dmitry Alexandrov
[not found] ` <mailman.629.1467759414.26859.help-gnu-emacs@gnu.org>
2016-07-06 1:52 ` Emanuel Berg
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=37ca21a2-8218-41c0-acd4-98696c7f8746@googlegroups.com \
--to=brandeis.a.king@gmail.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.
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).