-
Notifications
You must be signed in to change notification settings - Fork 3
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
v0.1.0 does not work "Error: spawnSync undefined ENOENT" #2
Comments
The Rusty Code extension has formatting and language support build in. Can also optionally turn on format on save and check on save
|
@Steve-Himself I'm using that extension, but it doesn't seem like hitting |
@masaeedu are you on Windows? It never worked for me, but it's fine on Linux. |
@lnicola Yes. It looks like there was an incompatibility introduced in a PR with the latest version of |
Hi, looks like saviorisdead/RustyCode#173 was merged. What's the status of this issue? |
@kkimdev works for me |
Is there a way to see what this is trying to spawn? A log with actual values for the spawn/fork call? I just ran into the same issue, on Arch Linux. rustfmt is availabe (0.6.3 atm, available on the path), but I see that very same spawnSync error message. rustfmt works if I launch it manually and - as stated before - is available everywhere/on the path.. |
Same issue with me here on Windows 10 using VS Code. I'm trying to learn rust, so I thought I'd make myself a nice environment to play in, using rustycode, rustfmt, rustsym and so forth. Got pretty much everything working within VS Code except for the constant error message telling me "Error: spawnSync undefined ENOENT" every time I edit a line or save a file. Because simply pressing enter to add a blank line generates this, I suspected rustfmt not being configured correctly, but because I can find no log for VS code telling me what the hell it's trying to spawn/open I'm a bit stuck.
Is it actually possible to encourage VS Code to produce a log, or to view the logging produced by an extension? |
I've found that in some cases the default config for rustfmt.bin is not there in vscode and the plugin only uses the default rustfmt bin if the config is an empty string - however being undefined it's not handled and the spawn will get an empty path (hence the ENOENT). This pull request is fixing that scenario: #3 Update: forgot to mention, putting |
@itarato I've tried to add the path to my settings file but the only setting to change is |
@alessio-b-zak If I remember correctly the setting key ( |
@itarato found it in the global settings.json you can edit from edit->preferences or something like that. Will try your fix out. Thanks. |
I uninstalled |
@malcolmgreaves this sure worked for me! |
tks, i have remove vsc-rustfmt plugin |
run "Format with rustfmt"
tips:
"Error: spawnSync undefined ENOENT"
The text was updated successfully, but these errors were encountered: