search

bmpenuelas / systemverilog-formatter-vscode

Beautify SystemVerilog code in VSCode through Verible
MIT License
17 stars 4 forks source link

Incorrect shell used #19

Open civec opened 1 year ago

civec commented 1 year ago

I have Verible binaries in the PATH and they are accessible in my BASH terminal. VS Code is trying to run Verible with /bin/sh even though BASH is set in VS Code terminal.integrated.shell.linux

2023-06-07 12:16:02.708 [error] [bmpenuelas.systemverilog-formatter-vscode] provider FAILED 2023-06-07 12:16:02.708 [error] Error: Command failed: verible-verilog-format - /bin/sh: verible-verilog-format: command not found

Could you please help me with this issue?

bmpenuelas commented 1 year ago

Of course! I have created a new version that uses terminal.integrated.shell (if present) to set the shell to be used.

I have just published it as pre-release. You need to find the extension inside VSCode, click the drop-down and select it (for more info see https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_63.md#pre-release-extensions )

Can you please try it and let me know how it goes?

the-moog commented 1 year ago

Similar issue here (using the prerelease) despite setting the path to 'none', it appears to be still trying to use the packaged binary (and then for the wrong os/kernel) (note: running external binaries is unacceptable here) I've put a build from official source version is in my local user bin folder which is in the path and it does not find it. The debug logging is a little light so I can't say more than 'permission denied'.