-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Auto-Formatting (autopep8, black, yapf) Doesn't Work On Unsaved Files #2268
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
Comments
I have met the same situation. |
@brettcannon Today we save the file temporarily and then format the file. |
@CoryOwens @weqopy This works for me as expected. |
@DonJayamanne - I just tried EDIT2: Screen capture with less graphical tearing. |
Ok, this is different. I tested this on a dirty document. |
@Nate-Wilkins - I just tested it, and this bug still appears to exist. The fix you referenced was merged back in February (whereas I reported this bug in July), and it appears to change how python finds the home directory, rather than how it handles formatting temp files. |
We decided that this is not currently a priority for us, but we would happily look at a PR to implement this if someone provided one. |
Environment data
Actual behavior
Working with Python code in an unsaved file, executing the command
editor.action.formatDocument
has no effect on the text. The status bar briefly flashes to say that the formatter was run.If you then save the document and run the same command, the formatter runs and edits the text as normal.
Expected behavior
Working with Python code in an unsaved file,
editor.action.formatDocument
will run the associated Python formatter (yapf, autopep8) and edit the text inline using default style settings.Steps to reproduce:
File->New
, orCtrl+N
by default.){0: 0, 1: 1, 2: 2, 3: 3, 4: 4, 5: 5, 6: 6, 7: 7, 8: 8, 9: 9, 10: 10, 11: 11, 12: 12, 13: 13, 14: 14, 15: 15, 16: 16, 17: 17, 18: 18, 19: 19, 20: 20, 21: 21, 22: 22, 23: 23, 24: 24, 25: 25, 26: 26, 27: 27, 28: 28, 29: 29, 30: 30, 31: 31, 32: 32, 33: 33, 34: 34, 35: 35, 36: 36, 37: 37, 38: 38, 39: 39, 40: 40, 41: 41, 42: 42, 43: 43, 44: 44, 45: 45, 46: 46, 47: 47, 48: 48, 49: 49, 50: 50, 51: 51, 52: 52, 53: 53, 54: 54, 55: 55, 56: 56, 57: 57, 58: 58, 59: 59, 60: 60, 61: 61, 62: 62, 63: 63, 64: 64, 65: 65, 66: 66, 67: 67, 68: 68, 69: 69, 70: 70, 71: 71, 72: 72, 73: 73, 74: 74, 75: 75, 76: 76, 77: 77, 78: 78, 79: 79, 80: 80, 81: 81, 82: 82, 83: 83, 84: 84, 85: 85, 86: 86, 87: 87, 88: 88, 89: 89, 90: 90, 91: 91, 92: 92, 93: 93, 94: 94, 95: 95, 96: 96, 97: 97, 98: 98, 99: 99}
Command Palette->Change Language Mode
, orCtrl+K M
* by default) and select Python.editor.action.formatDocument
command (Command Palette->Format Document
, orCtrl+Shift+I
by default)File->Save
, orCtrl+S
by default.)*: This default keybind doesn't actually work for me, instead launching a search in the Extensions Marketplace for
@recommended:keymaps
.Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)The text was updated successfully, but these errors were encountered: