Folks,
After almost two years, I may have stumbled onto the root cause of this vi
display corruption problem.
It looks to be related to the character encoding difference between the Linux
system that uses UTF-8, and macOS (XQuartz) (X11) which apparently uses
something else.
I solved this p
Bram,
Thanks for your help.
The macOS xterm version is:
XTerm(326)
The macOS XQuartz version is:
XQuartz 2.7.11 (xorg-server 1.18.4)
The v:termresponse value is:
v:termresponse ^[[>41;326;0c
--
Dick Riegner
--
>
> Dick Riegner wrote:
>
>> I consistently see text display corruptio
Elijah,
Thanks for the help and insight.
I guess it is good to know that I am not the only one seeing these kinds
of problems with vim and XQuartz.
Norm Wood found that you can also work-around this problem if you reset
your vim term variable to xterm after starting the edit session:
set term=x
Richard Riegner wrote:
> I run an xterm window on macOS and ssh into a
> remote Linux machine. The edit session is
> displayed back to an XQuartz server running on
> the same macOS.
I have seen lots of problems with that sort of setup:
local Mac with XQuartz and xterm used to
remote ssh t
Dick Riegner wrote:
> I consistently see text display corruption when
> editing a file on a remote Linux system with vim.
>
> I run an xterm window on macOS and ssh into a
> remote Linux machine. The edit session is
> displayed back to an XQuartz server running on
> the same macOS.
>
> I have
I consistently see text display corruption when
editing a file on a remote Linux system with vim.
I run an xterm window on macOS and ssh into a
remote Linux machine. The edit session is
displayed back to an XQuartz server running on
the same macOS.
I have only seen this problem when displaying
