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

the vscode extension is now sensitive to the working directory of vscode itself #929

Closed
ahicks92 opened this issue Nov 26, 2024 · 3 comments

Comments

@ahicks92
Copy link

On 1.7.1 using Stylua 2.0. I found #915 but this doesn't seem to be the same thing. If I open vscode from the Windows start menu (which pulls up your last open workspace) stylua.toml is ignored. If I open it with code . in the working directory of the project, it works fine.

@JohnnyMorganz
Copy link
Owner

Sorry for the delay in responding here. I wasn't able to reproduce this particular problem.

If you open the "Output" tab for StyLua, and switch it to view Debug logs, it should print out the commands that are getting run. Is the 'stdin-filepath' that gets provided correct? My only other thought is the CWD is not correct when running

@ahicks92
Copy link
Author

ahicks92 commented Jan 5, 2025

I will get back to you in the next couple of days on that. I switched projects for a while.

@ahicks92
Copy link
Author

A quick attempt at a repro says I can no longer repro. Closing for the obvious reasons. I'll open something with more info if this shows up again and I can reproduce it. Sort of half guessing either major human error, or VSCode fixing something on their side.

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

No branches or pull requests

2 participants