-
Notifications
You must be signed in to change notification settings - Fork 56
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
Vscode instructions don't work on OSX #67
Comments
@Carreau could you look at this issue – is there an incompatibility or a mistake in our instructions? Maybe |
I noticed this issue as well… but only for files that you open "directly". If you open a folder, then open a file it works. Forgive me as I'm not a VS Code user but I just wanted to report that it does indeed 1/2 work. I examined the output of Another thing: I noticed that (somewhat obviously perhaps?) that it only formats after the file is saved? For me:
|
@shangxiao if I create a branch which changes Darker to report absolute paths, would you be willing to test it with VS Code? |
@shangxiao I tried |
@shangxiao other differences between Black and Darker
Those I could also try enabling in a branch so they could be tested with VS Code. |
@virtuald @shangxiao @Carreau you could try whether #84 makes any difference for VS Code. |
I wonder if this is the same issue as #104, and whether it still happens with Darker 1.3.0. |
I'll assign this to the 1.4.2 release, but since there haven't been more complaints about this since the 1.3.0 release, I think by end of February I'll conclude this isn't an issue anymore and close the issue. |
Workspace settings:
In the output section it does look like it's running darker, but nothing happens (and there's an extra diff -- I tried removing it and it didn't fix it):
Changing the formatter to the original black executable does formatting as one would expect.
The text was updated successfully, but these errors were encountered: