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
On Fri, Aug 10, 2018 at 4:45 PM, Bram Moolenaar wrote:
>
> Hello Vimmers,
>
> I have visited Vim's charity project in June. I finally had time to
> finish writing my report and organise the pictures. You can find it
> here: http://www.iccf.nl/news.html
>
> It has links to the photo album and a sh
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
Em quinta-feira, 9 de agosto de 2018 16:19:48 UTC-3, Bram Moolenaar escreveu:
> Renato Fabbri wrote:
>
> > (set printoptions=header:0)
> > :hardcopy > something.pdf
> >
> > :'o(
> >
> > I don't have a Windows OS here to give you the names,
> > but I guess Adobe and Foxit were unable to read the
May not be related to your problem, BUT you also need to tell vim that
you are
using bash, as it shares syntax with 'sh'.
In my ~/.vimrc, I have
let g:is_bash=1
let b:is_bash=1
kamaraju kusumanchi wrote:
On Sun, Jul 29, 2018 at 7:37 AM, John Little wrote:
With the vim 8.1.0224 from g
Hello Vimmers,
I have visited Vim's charity project in June. I finally had time to
finish writing my report and organise the pictures. You can find it
here: http://www.iccf.nl/news.html
It has links to the photo album and a short video.
--
hundred-and-one symptoms of being an internet addict
