From: Yuri Khan <yurivkhan@gmail.com>
To: ambjlon@gmail.com
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: emacs display garbled
Date: Fri, 16 Nov 2018 17:27:01 +0700 [thread overview]
Message-ID: <CAP_d_8WHPuakZrKMzJF1TL9PhVTKRbyLtRPyfH92rNPP7P2JpQ@mail.gmail.com> (raw)
In-Reply-To: <3a33ebf8-cb1b-449a-99f8-07acb95c16a2@googlegroups.com>
On Fri, Nov 16, 2018 at 5:05 PM Jianglong Chen <ambjlon@gmail.com> wrote:
> > $ infocmp -x
> >
> > What does it say?
>
> # Reconstructed via infocmp from file: /usr/share/terminfo/x/xterm-256color
> xterm-256color|xterm with 256 colors,
[…]
Hm, at first glance, your terminfo seems to be sane. Sorry, maybe
someone who knows iTerm2 better can help.
Just to have an additional data point, how does Emacs behave if you
set TERM to xterm?
$ TERM=xterm emacs
next prev parent reply other threads:[~2018-11-16 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 9:30 emacs display garbled Jianglong Chen
2018-11-15 12:38 ` 조성빈
2018-11-15 14:53 ` Eli Zaretskii
2018-11-15 15:18 ` Yuri Khan
[not found] ` <mailman.4087.1542289042.1284.help-gnu-emacs@gnu.org>
2018-11-16 9:13 ` Jianglong Chen
2018-11-21 22:28 ` Van L
[not found] ` <mailman.4095.1542295136.1284.help-gnu-emacs@gnu.org>
2018-11-16 9:20 ` Jianglong Chen
2018-11-16 9:58 ` Yuri Khan
[not found] ` <mailman.4130.1542362338.1284.help-gnu-emacs@gnu.org>
2018-11-16 10:03 ` Jianglong Chen
2018-11-16 10:27 ` Yuri Khan [this message]
[not found] ` <mailman.4131.1542364037.1284.help-gnu-emacs@gnu.org>
2018-11-16 10:32 ` Jianglong Chen
[not found] ` <mailman.4090.1542293603.1284.help-gnu-emacs@gnu.org>
2018-11-16 9:24 ` Jianglong Chen
2018-11-16 9:25 ` Jianglong Chen
2018-11-16 9:40 ` Eli Zaretskii
2018-11-16 9:43 ` 조성빈
2018-11-16 10:35 ` Eli Zaretskii
[not found] ` <mailman.4132.1542364563.1284.help-gnu-emacs@gnu.org>
2018-11-16 11:00 ` Jianglong Chen
2018-11-16 14:43 ` Eli Zaretskii
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=CAP_d_8WHPuakZrKMzJF1TL9PhVTKRbyLtRPyfH92rNPP7P2JpQ@mail.gmail.com \
--to=yurivkhan@gmail.com \
--cc=ambjlon@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.
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.