l.com schrieb am 22.02.2023 um 15:47:
> > On Tuesday, February 21, 2023 at 5:01:04 AM UTC-5 Dave McCooey wrote:
> >>
> >> Hello,
> >>
> >> I recently added the following autocommands to my _vimrc file:
> >>
> >> :hi
Hello,
I recently added the following autocommands to my _vimrc file:
:hi ExtraWhiteSpace ctermbg=58 " Orange4 = #5f5f00
autocmd BufWinEnter,InsertLeave * syntax match ExtraWhiteSpace /
\+\ze\t\|\t\zs \+\|^ \+\|\s\+$/ containedin=ALL
autocmd InsertEnter * syntax match ExtraWhiteSpace / \+\ze\t\|
Many vim users, myself included, learn about filetype plugins
and autocommands only in an effort to disable a filetype plugin's
behavior of overriding settings specified in _vimrc.
For example, my _vimrc contains the following autocmd:
autocmd FileType * setlocal iskeyword=@,48-57,_,192-255
More
On Mon, Sep 26, 2022 at 8:38 AM Christian Brabandt
wrote:
>
> On So, 25 Sep 2022, Dave McCooey wrote:
>
> > Hi Christian,
> >
> > The file with the problem is _vimrc itself, which is how I noticed it.
> >
> > Here is a line from my _vimrc that shows the
wrong,
because if I copy _vimrc to xxx.rc, then xxx.rc does not have the problem.
Best regards,
Dave McCooey
On Sun, Sep 25, 2022 at 10:37 AM Christian Brabandt
wrote:
>
> On So, 25 Sep 2022, Dave McCooey wrote:
>
> > Hello,
> >
> > There is a problem with synt
ult ones included in the distribution.
This problem is seen with vim version 8.2 (included patches 1-4372)
on Cygwin, and also with version 8.2 (included patches 1-2072) on Linux.
I have version 7.3 running on a Mac that does not have the problem.
Best regards,
Dave McCooey
--
--
You received t
