Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Iverilog linting doesn't work #139

Open
doee-hc opened this issue Feb 19, 2021 · 5 comments
Open

[BUG] Iverilog linting doesn't work #139

doee-hc opened this issue Feb 19, 2021 · 5 comments
Labels

Comments

@doee-hc
Copy link

doee-hc commented Feb 19, 2021

Describe the bug
Thank you for supporting such a powerful extension!
I have installed iverilog and add it into the PATH,it works well in "cmd" and "power shell"
Then I set iverilog as the linter from the VScode setting page.
It doesn't work when saving the .v file (no red underline and no output).
I have seen the similiar issuess, but these solutions doesn't work.
I have tried some old versions of this extension and iverilog,but the problem wasn't resolved.

Environment (please complete the following information):

  • OS: Windows 10 1909 build 18363.1379
  • VS Code version 1.53.2
  • Extension version 1.4.2
  • Iverilog version v11-20201123-x64
@doee-hc doee-hc added the bug label Feb 19, 2021
@doee-hc doee-hc changed the title [BUG]iverilog linting doesn't work [BUG] Iverilog linting doesn't work Feb 24, 2021
@yizhanchengyan
Copy link

被编辑的文本的路径不能有中文

@kkwangyu
Copy link

kkwangyu commented Apr 4, 2023

The path of the edited file cannot contain Chinese and spaces。

@furai
Copy link

furai commented May 1, 2023

Hey, I'm getting this bug in the current version of the extension. No linter works if the path to the file includes spaces. The fix would be to pass the path to the linter quoted.

@mshr-h
Copy link
Owner

mshr-h commented Jun 2, 2023

Released v1.11.5 with the fix.
Please give it a try.

@furai
Copy link

furai commented Jun 15, 2023

Seems it still dosn't work. I think that VerilogSymbol fails now as it gets split path and no warnings or errors show up. It gets linted properly though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants