Add autocommands to notice linters

[n-p-e]

This change addresses #402 for linters that provide enable/disable commands.
I'm not very familiar with vimscript, so please check.

As mentioned in the #402, the best workaround so far is probably attach an autocommand to TextChanged and CursorMoved and manually check whether EasyMotion is active. This makes the process much simpler. Linter plugin authors can also easily support EasyMotion.

[haya14busa]

Can we save/restore eventignore instead to avoid the issue?

[n-p-e]

Can we save/restore eventignore instead to avoid the issue?

I tried so, but doing set eventignore+=TextChanged doesn't seem to stop coc.

[blayz3r]

This change is causing this weird warning

[haya14busa]

Thanks. I reverted the pr.

[smackesey]

I am using @jakelinzy's branch and I can't replicate this warning-- perhaps a difference between Vim and NeoVim (I'm on NeoVim)?

But in any case, pretty sure that the message is the result of a user having no autocommands defined for User EasyMotionPromptBegin and User EasyMotionPromptEnd when these events are emitted. The problem should be fixed by simply prepending silent to the doautocmd lines in the PR.

This PR introduced a really useful feature for dealing with the linter interference caused by easymotion, so I hope this gets remerged with the above change.

[n-p-e]

I am using @jakelinzy's branch and I can't replicate this warning-- perhaps a difference between Vim and NeoVim (I'm on NeoVim)?

You're right. I didn't notice this behaviour. My fault.

From Neovim :h vim_diff:

Commands:
:doautocmd does not warn about "No matching autocommands".

#440 Fixes this.