A way to have Vale show the whole line that triggered a rule?

[emteelb]

While using Vale to lint large AsciiDoc files, I sometimes run into cases where the line number that Vale reports as triggering a rule, does not correspond accurately to the actual .adoc file.

I have tried a general search here for some keywords such as occurrence, line number, context, et. al. but haven't found any results where this is discussed. I think I have an understanding that Vale lints generated HTML from the AsciiDoc file, rather than the .adoc file itself. That might account for some weirdness. But most of the time, the line numbers that Vale reports correspond accurately to occurrences in the .adoc files.

Is it possible, maybe in a command line argument that I'm not seeing in --help, for Vale to print the whole line, rather than just what the [%](message: Use '%s' rather than '%s'.) in the rule, for example, picks out? Is there anything like a hidden debug or verbose mode that would do this?

Here's an example of some linting where the line number reported doesn't match the contents of the line number for a given file.

Linting a file, linstor-kubernetes.adoc that has 2869 lines, Vale (with the Red Hat style package added) reports:

[...]
1982:91   error  Use 'Kubernetes' rather than    RedHat.CaseSensitiveTerms
                 'kubernetes'.                                            
[...]

If I then use a sed command to print that line number, it shows that there isn't an occurrence of "kubernetes".

$ sed -n 1982p linstor-kubernetes.adoc 
Before you can add snapshot support, you need to meet the following environment prerequisites:

I can sometimes go into the file and poke around near the reported line and find the corresponding offense that triggered a rule, but for large files and for many occurrences, this gets tedious. Looking for a way to make this process faster.

Thanks in advance for any help.

[veshivas]

If you are linting a large no. of files using vale, I suggest using a multi-threaded python script to call vale on each file separately. We do something like this.

[emteelb]

Thanks for the reply. A large number of files isn't my issue here. Usually only linting one at a time.