Closed Benz0X closed 5 years ago
There was a bug that was causing the linter to run on non verilog/sv files. This has been fixed 1aaa969eeb4fc51b20732876030fcfdd41131440 and fixed with v1.0.2. Can you check if this is still happening?
On a side note, linter will be run on a file only when it is opened. If the file doesn't even exist, I am not sure how this is happening.
I started again from a clean install an wasn't able to reproduce the issue. My guess is that there was a conflict with the svn extension, that created a temporary file $filename.svn and for some reason the linter tried to run on the file.
Anyway, the problem seems solved/non reproductible so you may close the issue.
On a side note, I tried to use the tmLanguage from Sublime text plugin systemverilog by Clams and the syntax highlight was greatly improved. (It can be found here). I didn't see any licence restriction so it might be interesting to use it in your plugin. Another great feature from this plugin is the verilog/systemverilog indenter/beautifier, but I'm not sure it can be easily ported.
Thanks for your answer
@Benz0X I am glad the issue is solved.
As of v1.0.3, that was released a few days ago, we have shifted to the tmLanguage of the sublime text plugin you mentioned. I will see what can be done about the beautifier.
Happy to answer. You can close the issue yourself :)
When using modelsim linter on a project under SVN (and only with the johnstoncode.svn-scm extension enabled), the linter throw an error on a non existing file. Strangely, this doesn't impact the two other linters I can use (xvlog and verilator)
If i put syntax error in my file, the new error is shown, but the error on the non existing file is still thrown.
Workaround idea : check file existence before running the linter on the file ?
This is the error returned when copying from the PROBLEMS view :