Hi Gary!
On Mi, 03 Feb 2016, Gary Johnson wrote:
> Thanks for looking into this. With your results as a guide, I
> reduced the environment needed to reproduce the issue even further.
> Now the vim command is simply this,
>
> $ vim -N -u NONE -o2 --cmd 'so colorschemetest.vim' --cmd 'au Colo
On 2016-02-03, Charles E Campbell wrote:
> Gary Johnson wrote:
> > I'm running Vim 7.4.1152 in an xterm on a Red Hat Enterprise Linux
> > 7.1 system and using Dr. Chip's AnsiEsc plugin (v13i) to make ANSI
> > color escape sequences in some files readable.
> >
> > I noticed some odd behavior and sim
Gary Johnson wrote:
> I'm running Vim 7.4.1152 in an xterm on a Red Hat Enterprise Linux
> 7.1 system and using Dr. Chip's AnsiEsc plugin (v13i) to make ANSI
> color escape sequences in some files readable.
>
> I noticed some odd behavior and simplified the conditions down to
> this (one line).
>
>
Hi Christian,
On 2016-02-03, Christian Brabandt wrote:
> Hi Gary!
>
> On Di, 02 Feb 2016, Gary Johnson wrote:
>
> > I'm running Vim 7.4.1152 in an xterm on a Red Hat Enterprise Linux
> > 7.1 system and using Dr. Chip's AnsiEsc plugin (v13i) to make ANSI
> > color escape sequences in some files r
Hi Gary!
On Di, 02 Feb 2016, Gary Johnson wrote:
> I'm running Vim 7.4.1152 in an xterm on a Red Hat Enterprise Linux
> 7.1 system and using Dr. Chip's AnsiEsc plugin (v13i) to make ANSI
> color escape sequences in some files readable.
>
> I noticed some odd behavior and simplified the condition
I'm running Vim 7.4.1152 in an xterm on a Red Hat Enterprise Linux
7.1 system and using Dr. Chip's AnsiEsc plugin (v13i) to make ANSI
color escape sequences in some files readable.
I noticed some odd behavior and simplified the conditions down to
this (one line).
$ vim -N -u NONE -o2 --cmd 's
