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: Wed, 6 Jul 2016 13:37:08 +0600 [thread overview]
Message-ID: <CAP_d_8WZe7+E-iEcRgxxyxZPYy=69GFmSV9w19_YR7zDNUtuTg@mail.gmail.com> (raw)
In-Reply-To: <ca3e2266-62fb-4ee2-ae9a-9b1f50502ade@googlegroups.com>
On Wed, Jul 6, 2016 at 8:14 AM, Brandeis King <brandeis.a.king@gmail.com> wrote:
> To clarify, I'm experiencing this issue with xterm and gnome-terminal, both with and without tmux. And yes, I'm using z-shell.
When you press Page Down in xterm or gnome-terminal, it generates four
characters: ESC [ 6 ~. Upon receiving this sequence, Emacs should
translate it back to a [next] key vector.
In order for this to happen, Emacs has to know you’re using an
xterm-compatible terminal. It does that by looking at your TERM
variable.
Your symptoms suggest that the value of the TERM environment variable
does not match your terminal type.
To debug the problem further, you need to list, for each distinct case:
* the complete stack of terminal emulators;
* what the value of TERM is at each layer of that stack.
The shell you are using is mostly irrelevant; the only thing it will
affect is whether and how you set the TERM variable.
For xterm and gnome-terminal, the expected result is:
$ echo $TERM
xterm
or a variation thereof (e.g. xterm-256color).
When you use tmux with xterm or gnome-terminal, TERM should be "xterm"
(or xterm-*) before you start tmux, and "screen" (or screen-*) within
tmux.
(Newer systems, e.g. Ubuntu 16.04, also support a separate "tmux" (and
tmux-*) terminal type. As far as I can tell, Emacs does not yet have
such support.)
next prev parent reply other threads:[~2016-07-06 7:37 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 [this message]
[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
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_8WZe7+E-iEcRgxxyxZPYy=69GFmSV9w19_YR7zDNUtuTg@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).