Charles Campbell wrote the following on 14.10.2011 17:27
Hello Charles,
-- --
> So, netrw may be
> removed from your list; you might want to change your greps to
> accomodate setlocal.
Indeed 'autoload/netrw.vim' is cpo save. Thank you!
> Regards,
> Chip Campbell
Regards,
--
bye Thilo
40
Danek Duvall wrote:
Thilo Six wrote:
attached is full list of affected files. Those files below /doc can be ignored i
assume. I would like to see the rest fixed, too. Can we join forces?
...snip...
I used
comm -13 =(grep -l "set cpo" **/*.vim) =(grep -l "^[[:space:]]*"
**/*.vim)
Danek Duvall wrote the following on 12.10.2011 23:40
-- --
> I used
>
> comm -13 =(grep -l "set cpo" **/*.vim) =(grep -l "^[[:space:]]*"
> **/*.vim)
>
> to generate mine (with some zsh-isms). That gives 73 files to check out
> once you ignore the keymap files.
-- --
funily my upd
Danek Duvall wrote the following on 12.10.2011 23:40
Hello Danek,
-- --
> If you want, we can split them up, but the trick will be to weed out
> maintainers that already got the message by way of the syntax file missive
> I sent out and to make sure we don't duplicate each other. I think it's
Thilo Six wrote:
> attached is full list of affected files. Those files below /doc can be
> ignored i
> assume. I would like to see the rest fixed, too. Can we join forces?
Well, I sent out a missive to the maintainers of the syntax files (some of
whom also own some of the other runtime files),
Danek Duvall wrote the following on 11.10.2011 22:13
Hello Danek
Thanks for your affort.
> There are a handful of syntax files that use backslash continuation
> characters without ensuring that cpoptions is missing C, so when running
> vim in vi compatibility mode (such as when there's no .vimrc
Thilo Six wrote the following on 12.10.2011 20:25
-- --
> attached is full list of affected files. ...
PS. I know the search pattern I used produces false positives. So i rephrase the
above to 'files need to be checked'.
--
bye Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0
Danek Duvall wrote:
> There are a handful of syntax files that use backslash continuation
> characters without ensuring that cpoptions is missing C, so when running
> vim in vi compatibility mode (such as when there's no .vimrc), you'll get
> errors like
>
> Error detected while processing /
