Setting the markup language for a file not on stdin.

[rouilj]

Vale has an option --ext but it only applies (in theory) when parsing a file from stdin.

I have a bunch of ReStructured text documents with a .txt extension rather than .rst.
If I run vale doc/features.txt I get reports on:

 23:54  error  Did you really mean 'sqlite_'?  Vale.Spelling
...
 130:5  error  Did you really mean '_sqlite'?  Vale.Spelling

etc. This makes sense as these are hyperlink references in rst, but vale is not in rst mode.
If I run: vale --ext=.rst doc/feature.txt it appears to put vale in rst mode and I get the same output
by renaming feature.txt to feature.rst and running vale doc/feature.txt.

Is this intended? I hope so as it will make it more useful. I am using vale version 3.3.1.

Thanks for any thoughts.

[jdkato]

Yes, but this will only work from the command-line and with single-file or all rst input.

Another approach is to use the format association section:

[formats]
txt = rst

This will work everywhere (e.g., editor extensions) and with multi-format input.

[rouilj]

Thanks, it works nicely.

Have a great day.

[JanWielemaker]

[formats]
txt = rst

I just tried that after extending vale (and go-tree-sitter) with support for Prolog. The most common extension is .pl, but this is a heavily overloaded extension that vale binds to .r. Processing .prolog files now works just fine. After a [formats] pl = prolog though, vale still seems to process the file as .r. Using the --ext option works fine, but is not usable through vale-ls.

After changing format.go to rebind .pl as ``.(?:pl|prolog)$: {".prolog", "code"},, all functions correct. So, it seems you cannot overrule existing extension to format bindings in `.vale.ini`?