On 2019-04-18, Chris White wrote:
> • In cxw42/editorconfig-vim@e885c43 I have added :EditorConfigDisable and
> :EditorConfigEnable. If this plugin were to be enabled by default, you
> could disable it with EditorConfigDisable in your vimrc.
Plugins are not sourced until after vimrc is
On 2017-11-04, 19:43 GMT, Bram Moolenaar wrote:
> - It requires Python. It appears just because an existing
> parser existed in Python. Using an external Python program
> seems clumsy and slow.
I have strictly no position on whole idea, but just let me tell
that there are zillions of pars
On 2017-11-04, 16:02 GMT, K.Takata wrote:
> I also use editorconfig-vim, and I *personally* think it is
> useful. However, the most important thing is that we need
> explicit permission from the author.
My problem is that it covers too narrow set of variables (for
example I would love to have a
