-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Close dirty editors: Provide fast action to save all or revert all #8009
Comments
Not trivial with our current model of handling dirty editors. |
@sandy081 @alexandrudima ping, since you reported this and similar issue. I decided to change the way our "Close All Editors" action work and instead of asking for individual files to confirm saving, show the combined confirmation dialog (the same you get on shutdown without hot exit enabled). I am not 100% sure this is the best fix because some people might expect our current behaviour and would want a separate action for it. Though I find it elegant to show the combined confirmation when you actually invoke the "Close All Editors" action. Note that this does not change the behaviour of the "Close All Editors in Group" action, nor the other close related actions (e.g. "Close Others"). /cc @Tyriar since this is for a better hot exit experience |
I like it, if people need to discard some at this point they can cancel and discard. |
|
Works great 👍 @bpasero the message box may look better if the list of files is in the description part of the message box rather than the title? |
Yeah good point, I can look into that. Might only have a visual difference on macOS though. |
Unfortunately this still doesn't fix the desired use for the vim plugin q! should quit no matter what is dirty or not dirty Do you have any reccomendations for this? |
@bpasero Any ideas on how I can do this and skip the prompt entirely? |
@xconverge that should work as long as hot exit is enabled in settings |
But I want the feature of hotexit + revert all changes so that's why I don't think hot exit is the solution. In vim q! Is quit no matter what, if documents aren't saved then they are reverted and closed automatically |
@xconverge I see, you want a command that quits the application after reverting all dirty changes? |
Yes and quits silently. In vim you can do quit and have it prompt you to save dirty editors OR you can do a force quit which just closes everything silently and does not remember any of the unsaved changes at all. |
@xconverge ok this sounds like a new feature request that should get a separate issue, can you create one with a good description? |
Sure, this was the issue that was referenced before you guys implemented hotexit, you can see the VSCodeVim ticket referenced in October up above. I can create a new ticket though |
It seems to me this issue has nothing to do with the VIM use case (hence all my questions). |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: