an error will be reported when I create a new file
When I use vscode to open a Verilog file and instantiate it。I plan to Paste it into a new file,then double-click to create a new file like
with the mouse and an error will be reported

Could you check if you have the same problem in the beta version?
https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/V0.0.5
Could you check if you have the same problem in the beta version?
https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/V0.0.5
I have the same problem in the beta version
Could you explain the problem in more detail?
Could you check if you have the same problem in the beta version? https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/V0.0.5
I have the same problem in the beta version
This is the right link for the beta version: https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/latest Just in case you downloaded an older version...
Could you explain the problem in more detail?
when i use generate template to generate some template such as cocotb testbench etc,the template is on clipboard, so i want to creat new file , if i creat new file without any extension like .v(because i often creat new file through double-click with the mouse) , an error will be reported.
1

2

3 A few seconds later

Could you check if you have the same problem in the beta version? https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/V0.0.5
I have the same problem in the beta version
This is the right link for the beta version: https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/latest Just in case you downloaded an older version...
thank you ,I will try it right now
Could you check if you have the same problem in the beta version? https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/V0.0.5
I have the same problem in the beta version
This is the right link for the beta version: https://github.com/TerosTechnology/vscode-terosHDL/releases/tag/latest Just in case you downloaded an older version...
the new have the same problem
fixed on v5.0.0