David Barnett
David Barnett
You can patch #12 locally to get tests running for now if we decide not to merge the workaround changes.
Eh, it's a kinda specialized tool and not made to be depended on by other python projects. It's not hard to upload but benefit seems small. Was there some advantage...
I kinda prefer having it explicit over the small convenience of not having to type `.`. Might be worth giving a better error with a usage hint when plugin path...
Turned out argparse didn't make it as easy as I'd expected to add a custom error for that case like "Did you mean to run 'vimdoc .'?" But I have...
What's the filename? Is this a .vim file in the directory root, not under a subdir like plugin/, autoload/, etc?
Agreed, the error message there sucks and should be fixed. Probably it should just skip that file, maybe with a warning that it's not included in the processing.
I agree it'd be a shame and didn't realize it affected OSX, too. I'll wait and see what happens on vim/vim#1340. Re keeping the case-insensitive behavior in this plugin, in...
Yeah, reasonable to change it to `set ft=` instead of `setf`. No point merging that change into vim since the builtin version has control over precedence. BTW, I remember that...
Cool, looks like this is still up-to-date, just waiting on another round of review before helix can support editorconfig files?
Thanks for the heads up! Looks reasonable.