Compiler vlty: respect Vim variable fileencoding

[matze-dd]

This relates to issue #1829.

• vlty.vim: According to the doc, fileencoding may be empty. Then encoding is used.
• options.vim: added default for encoding
• vimtex.txt:
  • As in the previous PR, I'm undecided about the order of the options. Please feel free to change that ;-)
  • I have wrapped some lines that were longer than 80 characters.

[lervag]

Thanks! I think this is good enough for an immediate merge (I just had to fix a minor typo).

As in the previous PR, I'm undecided about the order of the options. Please feel free to change that ;-)

The option description comes in a consistent order compared to the default dict, which is nice. In many cases, the order is irrelevant, and I often try to use e.g. alphabetic order. However, in some cases it feels right to put the important things on top. This does result in some things being in semi random order. I don't think it's a problem, but if anyone does I'm glad to discuss it.

I have wrapped some lines that were longer than 80 characters.

I've often tried to keep things wrapped to 79 or 80 characters on the visual columns. E.g., in lines that have a lot of concealed characters, I tend to allow more than 80 characters. But then I guess there's some/many who don't have conceals enabled at all, so perhaps that's a bad idea.

[matze-dd]

Thanks for merging!

I've often tried to keep things wrapped to 79 or 80 characters on the visual columns. E.g., in lines that have a lot of concealed characters, I tend to allow more than 80 characters. But then I guess there's some/many who don't have conceals enabled at all, so perhaps that's a bad idea.

Ah, I see. For instance, there was a line with 81 characters:

  This option is used to configure the `vlty` grammar checker. It is a dictionary 

With my simple configuration, in :help, the backticks around vlty are displayed, so that the line is wrapped in an 80-column terminal.

[lervag]

Yes, that makes sense. I'll revert my silly practice of considering the visual columns in future updates to the docs. :)