Discussion:
emacs display garbled
Jianglong Chen
2018-11-15 09:30:53 UTC
Permalink
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
조성빈
2018-11-15 12:38:56 UTC
Permalink
Maybe it is the terminal emulator problem? What kind of terminal emulator are you using?
Post by Jianglong Chen
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
Eli Zaretskii
2018-11-15 14:53:17 UTC
Permalink
Date: Thu, 15 Nov 2018 01:30:53 -0800 (PST)
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
My first suspect would be your display driver. If it has some
"acceleration" or "optimization" features, disable them and try again.
Yuri Khan
2018-11-15 15:18:26 UTC
Permalink
Post by Jianglong Chen
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
Looks very much like a mismatched terminfo configuration.

What terminal emulator are you using? What is the value of the TERM
environment variable in that terminal emulator immediately after you
start it?

Are you using any kind of terminal multiplexer (screen, tmux,
something else)? If so, what is the value of the TERM environment
variable once you’ve started that?

You mention using ssh. What is the value of $TERM after you connect?
If using a terminal multiplexer, are you starting ssh from a terminal
multiplexer tab, or starting a terminal multiplexer remotely?
Jianglong Chen
2018-11-16 09:13:56 UTC
Permalink
在 2018年11月15日星期四 UTC+8下午9:37:24,조성빈写道:
Post by 조성빈
Maybe it is the terminal emulator problem? What kind of terminal emulator are you using?
Post by Jianglong Chen
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
iTerm2 in mac os.
However, in other terminal emulator, this problem still exists
Van L
2018-11-21 22:28:23 UTC
Permalink
Post by Jianglong Chen
iTerm2 in mac os.
However, in other terminal emulator, this problem still exists
On Mac OS
I use XQuartz's xterm
$TERM is simply xterm

ssh-ing to netbsd-8
$TERM is wsvt25

I don’t experience garbled display.

Jianglong Chen
2018-11-16 09:20:54 UTC
Permalink
在 2018年11月15日星期四 UTC+8下午11:18:59,Yuri Khan写道:
Post by Yuri Khan
Post by Jianglong Chen
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
Looks very much like a mismatched terminfo configuration.
What terminal emulator are you using? What is the value of the TERM
environment variable in that terminal emulator immediately after you
start it?
Are you using any kind of terminal multiplexer (screen, tmux,
something else)? If so, what is the value of the TERM environment
variable once you’ve started that?
You mention using ssh. What is the value of $TERM after you connect?
If using a terminal multiplexer, are you starting ssh from a terminal
multiplexer tab, or starting a terminal multiplexer remotely?
The terminal emulator is iTerm2 and no any other terminal multiplexer were used.

$TERM=xterm-256color
Yuri Khan
2018-11-16 09:58:43 UTC
Permalink
Post by Jianglong Chen
The terminal emulator is iTerm2 and no any other terminal multiplexer were used.
$TERM=xterm-256color
Okay, next step, is the terminfo database in CentOS 6.3 recent enough
that it knows about xterm-256color and has the correct definitions for
it?

Start your terminal emulator, log onto your remote CentOS machine, and
issue the following command:

$ infocmp -x

What does it say?
Jianglong Chen
2018-11-16 10:03:14 UTC
Permalink
在 2018年11月16日星期五 UTC+8下午5:59:00,Yuri Khan写道:
Post by Yuri Khan
Post by Jianglong Chen
The terminal emulator is iTerm2 and no any other terminal multiplexer were used.
$TERM=xterm-256color
Okay, next step, is the terminfo database in CentOS 6.3 recent enough
that it knows about xterm-256color and has the correct definitions for
it?
Start your terminal emulator, log onto your remote CentOS machine, and
$ infocmp -x
What does it say?
# Reconstructed via infocmp from file: /usr/share/terminfo/x/xterm-256color
xterm-256color|xterm with 256 colors,
OTbs, am, bce, ccc, km, mc5i, mir, msgr, npc, xenl, AX,
colors#256, cols#80, it#8, lines#24, pairs#32767,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dl=\E[%p1%dM,
dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K, el1=\E[1K,
flash=\E[?5h$<100/>\E[?5l, home=\E[H, hpa=\E[%i%p1%dG,
ht=^I, hts=\EH, ich=\E[%p1%d@, il=\E[%p1%dL, il1=\E[L,
ind=^J, indn=\E[%p1%dS,
initc=\E]4;%p1%d;rgb\:%p2%{255}%*%{1000}%/%2.2X/%p3%{255}%*%{1000}%/%2.2X/%p4%{255}%*%{1000}%/%2.2X\E\\,
invis=\E[8m, is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~,
kEND=\E[1;2F, kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D,
kNXT=\E[6;2~, kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE,
kbs=\177, kcbt=\E[Z, kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC,
kcuu1=\EOA, kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP,
kf10=\E[21~, kf11=\E[23~, kf12=\E[24~, kf13=\E[1;2P,
kf14=\E[1;2Q, kf15=\E[1;2R, kf16=\E[1;2S, kf17=\E[15;2~,
kf18=\E[17;2~, kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~,
kf21=\E[20;2~, kf22=\E[21;2~, kf23=\E[23;2~,
kf24=\E[24;2~, kf25=\E[1;5P, kf26=\E[1;5Q, kf27=\E[1;5R,
kf28=\E[1;5S, kf29=\E[15;5~, kf3=\EOR, kf30=\E[17;5~,
kf31=\E[18;5~, kf32=\E[19;5~, kf33=\E[20;5~,
kf34=\E[21;5~, kf35=\E[23;5~, kf36=\E[24;5~,
kf37=\E[1;6P, kf38=\E[1;6Q, kf39=\E[1;6R, kf4=\EOS,
kf40=\E[1;6S, kf41=\E[15;6~, kf42=\E[17;6~,
kf43=\E[18;6~, kf44=\E[19;6~, kf45=\E[20;6~,
kf46=\E[21;6~, kf47=\E[23;6~, kf48=\E[24;6~,
kf49=\E[1;3P, kf5=\E[15~, kf50=\E[1;3Q, kf51=\E[1;3R,
kf52=\E[1;3S, kf53=\E[15;3~, kf54=\E[17;3~,
kf55=\E[18;3~, kf56=\E[19;3~, kf57=\E[20;3~,
kf58=\E[21;3~, kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~,
kf61=\E[1;4P, kf62=\E[1;4Q, kf63=\E[1;4R, kf7=\E[18~,
kf8=\E[19~, kf9=\E[20~, khome=\EOH, kich1=\E[2~,
kind=\E[1;2B, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
kri=\E[1;2A, mc0=\E[i, mc4=\E[4i, mc5=\E[5i, meml=\El,
memu=\Em, op=\E[39;49m, rc=\E8, rev=\E[7m, ri=\EM,
rin=\E[%p1%dT, rmacs=\E(B, rmam=\E[?7l, rmcup=\E[?1049l,
rmir=\E[4l, rmkx=\E[?1l\E>, rmm=\E[?1034l, rmso=\E[27m,
rmul=\E[24m, rs1=\Ec, rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7,
setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
sgr=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m,
sgr0=\E(B\E[m, smacs=\E(0, smam=\E[?7h, smcup=\E[?1049h,
smir=\E[4h, smkx=\E[?1h\E=, smm=\E[?1034h, smso=\E[7m,
smul=\E[4m, tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n,
u8=\E[?1;2c, u9=\E[c, vpa=\E[%i%p1%dd, kDC3=\E[3;3~,
kDC4=\E[3;4~, kDC5=\E[3;5~, kDC6=\E[3;6~, kDC7=\E[3;7~,
kDN=\E[1;2B, kDN3=\E[1;3B, kDN4=\E[1;4B, kDN5=\E[1;5B,
kDN6=\E[1;6B, kDN7=\E[1;7B, kEND3=\E[1;3F, kEND4=\E[1;4F,
kEND5=\E[1;5F, kEND6=\E[1;6F, kEND7=\E[1;7F,
kHOM3=\E[1;3H, kHOM4=\E[1;4H, kHOM5=\E[1;5H,
kHOM6=\E[1;6H, kHOM7=\E[1;7H, kIC3=\E[2;3~, kIC4=\E[2;4~,
kIC5=\E[2;5~, kIC6=\E[2;6~, kIC7=\E[2;7~, kLFT3=\E[1;3D,
kLFT4=\E[1;4D, kLFT5=\E[1;5D, kLFT6=\E[1;6D,
kLFT7=\E[1;7D, kNXT3=\E[6;3~, kNXT4=\E[6;4~,
kNXT5=\E[6;5~, kNXT6=\E[6;6~, kNXT7=\E[6;7~,
kPRV3=\E[5;3~, kPRV4=\E[5;4~, kPRV5=\E[5;5~,
kPRV6=\E[5;6~, kPRV7=\E[5;7~, kRIT3=\E[1;3C,
kRIT4=\E[1;4C, kRIT5=\E[1;5C, kRIT6=\E[1;6C,
kRIT7=\E[1;7C, kUP=\E[1;2A, kUP3=\E[1;3A, kUP4=\E[1;4A,
kUP5=\E[1;5A, kUP6=\E[1;6A, kUP7=\E[1;7A,
Yuri Khan
2018-11-16 10:27:01 UTC
Permalink
Post by Yuri Khan
$ 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
Jianglong Chen
2018-11-16 10:32:26 UTC
Permalink
在 2018年11月16日星期五 UTC+8下午6:27:19,Yuri Khan写道:
Post by Yuri Khan
Post by Yuri Khan
$ 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
Set $TERM=xterm and the problem exists still.
Jianglong Chen
2018-11-16 09:24:10 UTC
Permalink
在 2018年11月15日星期四 UTC+8下午10:53:25,Eli Zaretskii写道:
Post by Eli Zaretskii
Date: Thu, 15 Nov 2018 01:30:53 -0800 (PST)
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
My first suspect would be your display driver. If it has some
"acceleration" or "optimization" features, disable them and try again.
How to find if these features exist? I don't know any any display driver, sorry.
Jianglong Chen
2018-11-16 09:25:25 UTC
Permalink
在 2018年11月15日星期四 UTC+8下午10:53:25,Eli Zaretskii写道:
Post by Eli Zaretskii
Date: Thu, 15 Nov 2018 01:30:53 -0800 (PST)
https://stackoverflow.com/questions/51910830/emacs24-5-1-helm-project-find-files-display-broken
My first suspect would be your display driver. If it has some
"acceleration" or "optimization" features, disable them and try again.
How to find if these features exist? I don't know any about display driver, sorry.
Eli Zaretskii
2018-11-16 09:40:54 UTC
Permalink
Date: Fri, 16 Nov 2018 01:25:25 -0800 (PST)
Injection-Date: Fri, 16 Nov 2018 09:25:25 +0000
Post by Eli Zaretskii
My first suspect would be your display driver. If it has some
"acceleration" or "optimization" features, disable them and try again.
How to find if these features exist? I don't know any about display driver, sorry.
I don't know either, sorry, not for your type of system. Maybe
someone else here will chime in. (Does right-clicking on the desktop
bring a menu with something related to display properties?)
조성빈
2018-11-16 09:43:21 UTC
Permalink
I’m not sure about this, and I’m not an expert, but shouln’t it be in the iTerm settings?
Post by Eli Zaretskii
Date: Fri, 16 Nov 2018 01:25:25 -0800 (PST)
Injection-Date: Fri, 16 Nov 2018 09:25:25 +0000
Post by Eli Zaretskii
My first suspect would be your display driver. If it has some
"acceleration" or "optimization" features, disable them and try again.
How to find if these features exist? I don't know any about display driver, sorry.
I don't know either, sorry, not for your type of system. Maybe
someone else here will chime in. (Does right-clicking on the desktop
bring a menu with something related to display properties?)
Eli Zaretskii
2018-11-16 10:35:37 UTC
Permalink
Date: Fri, 16 Nov 2018 18:43:21 +0900
I’m not sure about this, and I’m not an expert, but shouln’t it be in the iTerm settings?
I don't think it's an iTerm problem, I think it's a problem with the
video hardware and its driver, according to what I see in the
screenshots.
Jianglong Chen
2018-11-16 11:00:52 UTC
Permalink
在 2018年11月16日星期五 UTC+8下午6:36:05,Eli Zaretskii写道:
Post by Eli Zaretskii
Date: Fri, 16 Nov 2018 18:43:21 +0900
I’m not sure about this, and I’m not an expert, but shouln’t it be in the iTerm settings?
I don't think it's an iTerm problem, I think it's a problem with the
video hardware and its driver, according to what I see in the
screenshots.
I think so
but how to debug and fix ...
Eli Zaretskii
2018-11-16 14:43:57 UTC
Permalink
Date: Fri, 16 Nov 2018 03:00:52 -0800 (PST)
Post by Eli Zaretskii
I don't think it's an iTerm problem, I think it's a problem with the
video hardware and its driver, according to what I see in the
screenshots.
I think so
but how to debug and fix ...
Unless someone here could tell you how to access the settings of your
video driver, I think you should find out what driver you have, and
read its documentation.
Loading...