Clarify documentation on `ltex.enabled`

[haoadoreorange]

Nothing too serious, there's a line in the doc of ltex.enabled

The activation events are unaffected by this setting.

Reading this I thought that I could remove html from the list (it doesn't parse well html templates :cry:) and use the command Activate Extension to activate ltex per file regardless of ltex.enabled. Find out that's not the case at all.

[valentjn]

Isn't the behavior you describe exactly what the line says? It says, regardless of how you change this setting, LT_EX will always be activated (meaning initialized by VS Code) for the default file types. It's just that once it has been activated checking will be enabled or, in your case, disabled for the specified/not specified languages, meaning that it will check/not check documents in those languages.

Do you have a concrete suggestion for how to make the line clearer (while still being concise)?

[haoadoreorange]

Oh wait, so I din't even understand well what it does in the first place... Well I guess we should really clarify activate vs enable, because I thought it was synonymous.

It's just that once it has been activated checking will be enabled or, in your case, disabled for the specified/not specified languages, meaning that it will check/not check documents in those languages.

May be we should add this line to the doc ?

[laclouis5]

I stumbled on this small issue too. The documentation is quite clear but I still find surprising that LTeX starts out as soon as I open a compatible file (say a markdown one) while I disabled LTeX checking for it.

[Tatsh]

I have the opposite issue. I added "python", to the list and LTex will not activate automatically when I open a Python file.