From: Yuri Khan <yuri.v.khan@gmail.com>
To: Brandeis King <brandeis.a.king@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Page Up/Down Issues With Emacs in Terminal
Date: Thu, 7 Jul 2016 10:47:47 +0600 [thread overview]
Message-ID: <CAP_d_8UpFu+6VNq=7_7=09dWZe_ryZpE0GNfX755LD8WKSZktw@mail.gmail.com> (raw)
In-Reply-To: <37ca21a2-8218-41c0-acd4-98696c7f8746@googlegroups.com>
On Thu, Jul 7, 2016 at 1:40 AM, Brandeis King <brandeis.a.king@gmail.com> wrote:
> I tried "emacs -Q -nw" again today, and the page up/down buttons do work as expected.
So then the problem is in most probably in your init file.
> In answer to previously asked questions, term is "screen-256color" -- this is set in my Xresources file
That’s a bad idea. You are lying to tmux that its underlying terminal
is screen-like, while it is in fact xterm-like. Additionally, other
programs, if you run them outside tmux, will misbehave.
Normally, tmux sets the TERM variable for processes running within its
session. It uses "screen" by default, but you can control it with this
line in your .tmux.conf:
set -g default-terminal "screen-256color"
> Input-Decode Map variable holds:
> Value: (keymap
> (27 keymap
[…]
> (91 keymap
> (53 keymap
> (126 .
> [prior]))
> (54 keymap
> (126 .
> [next]))
These are the decoding sequences for Page Up and Page Down. When you
start Emacs with your customizations, you can look for these. If they
are not there, find what deletes them.
Also, see if you are binding M-[ or ESC [ to anything. If you do, many
function keys, including Page Up and Page Down, will probably stop
working.
next prev parent reply other threads:[~2016-07-07 4:47 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
2016-07-07 4:47 ` Yuri Khan [this message]
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='CAP_d_8UpFu+6VNq=7_7=09dWZe_ryZpE0GNfX755LD8WKSZktw@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=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).