Francisco Lopes

I just provided a comment because the wording that "it doesn't honor" isn't sensible. It's not a standard practice, so there's nothing to _honor_ there. It sure can be made...

I've hit this sometimes but I didn't expect to change plugin or standard, if a project provides a `.editorconfig` and its files are not following it, the project must fix...

I'm for improving vi-mode detection and have the section **ON** by default, if it's enabled. Right now I have section stuck in `[I]` mode (issue #157), which is sad.

If the section gets removed, I think _some_ form of indication, at least, would be good to have, like dual form of prompts, like the sorin prompt from Prezto.

> I don't use `vi_mode` section personally due to it's inaccuracy and most of the detection methods either depend on external tools or unreliable. I made my comment while I...

@adanilev thanks! I'm giving this a try again now and your tip fixed the issue.

Though I think reversed prompt is much more noticeable than `[I]` vs `[N]`. It's what both the sorin (`❯❯❯`, `❮❮❮`) and pure (`❯`, `❮`) prompts do.

Would be great if TeXtidote support was added, it even supports json results for easy parsing. Great wrapper for LanguageTool, would make this plugin work on LaTeX and Markdown.

Deal breaker for me, long time using it on RPi3....

Oh, really, sorry, I'm running RPi3 on ARM64... I just recalled 😅