Sublime Forum

Save buffer in project

#1

Is it possible to have unsaved, open buffers stored in a project? For example, if I terminate Sublime with open buffers, they’ll restore when I re-open sublime. I’d like this to also happen when swapping projects. I was sure this is how it worked on Windows, once upon a time, but it’s definitely not the case here on my Mac. Did I misplace a setting? Am I mis-remembering?

I know, I could save the files … but that’s not what I’m trying to accomplish here. :slightly_smiling:

0 Likes

#2

If it was working on windows, but not on Mac OS, try Reverting to a clean state (backup your data).

If not work also, search the Core Issue Tracker for an issue like this for Mac. If not found you could open a new one.

  1. https://github.com/SublimeTextIssues/Core/issues
0 Likes

#3

I’m not confident it was working on windows, I could be mis-remembering. I can’t test/confirm myself, so I’m asking if this is the intended behavior, or if it can be done.

0 Likes

#4

I think it is. But I am not sure if I understand correctly so, I recorded an animation, it is like this you want to?

0 Likes

#5

That’s exactly what I’m talking about, @addons_zz – is there a setting for that I’ve accidentally tweaked somewhere?

0 Likes

#6

May be this setting. Other than this I do not know, but I just set it to false and it was kept working.

First, try to reproduce it on a clean Sublime Text install. So if not, see if there is a bug request for it on the core:

  1. https://github.com/SublimeTextIssues/Core/issues
  2. Reverting to a clean state (backup your data)
    //
    // Application Behavior Settings
    //

    // Exiting the application with hot_exit enabled will cause it to close
    // immediately without prompting. Unsaved modifications and open files will
    // be preserved and restored when next starting.
    //
    // Closing a window with an associated project will also close the window
    // without prompting, preserving unsaved changes in the workspace file
    // alongside the project.
    "hot_exit": true,
0 Likes

#7

Explicitly setting it to true in my settings seems to have fixed it. Strange that I had to add that setting, though – true is supposed to be the default behavior. Thanks for helping me sort this out!

0 Likes