-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add "Same for all" checkbox when closing unsaved tabs #2106
Comments
related, but for reloading externally modified files: #1666 |
This is still a huge problem. I've ran find'n'replace on a temporary folder, and now I'm stuck with 2000 tabs individually asking to save changes, and the whole application has become permanently is unusable. |
@kornelski I think you can also just delete "the" session file. On a Mac, it's located at
|
This also applies to the case where one wants to save all files in a “Close All Files” action. If one forgets to do “Save All” first, the user is forced to click “Save” for all open, unsaved files which could be many after a "Replace in files" for example. |
@ianrrees There is |
The implemented solution should differentiate between
|
On Linux, deleting |
As Keith Hall pointed out to me, there is a plugin that does this beautifully https://packagecontrol.io/packages/Close%20All%20without%20Confirmation |
1. Explain briefly what the enhancement is and why you think it would be useful.
When I open ST, I fairly frequently am presented with a set of several tabs open, which ST thinks have edits*. In that situation, I would like to close all the tabs, without saving any of them. Currently, this requires one dialog click per open file.
It would be nice if there were a checkbox that would apply that answer to subsequent files. Eg, when I do "close all files" and have 10 tabs open and edited, on the first one I would like to indicate "Do not save any of these".
*This comes about, due to a weird NFS mounted project situation, where the file server sometimes dies and there's doesn't seem to be a clear "right way" for ST to handle the situation.
2. Provide any other necessary or useful information regarding your issue, such as (code) examples or related links.
Environment
The text was updated successfully, but these errors were encountered: