👍

Nice!

I hope to see this working very soon!

It looks like this is mostly ready to go, even. Atom already keeps track of what was last open, and dumps it to JSON in ~/.atom/storage/ The next step is loading these state files at startup.

This feature is also in Brackets, the text editor I used to use.

I was missing that option to!! finally I found package that do just that :) https://atom.io/packages/open-last-project

+1

+1

+1

Isn't there a package which would just support switching between ~/.atom/storage/editor-* sessions? Hell, those JSONs even contain a project field, it should be extremely easy to write one for someone who's already written a package for Atom. I don't understand why the framework doesn't have a GUI and is only accessible via $ atom <path>. Or am I wrong?

Is this issue in a milestone somewhere? +1

+1

+1

As far as I found there is no solution yet when having multiple projects open. Very important aspect IMO: re-opening unsaved documents in the state they were in before the restart, so no work is lost.

+1

@Mil0dV +1, reopening unsaved files (i.e. saving their state into a temp folder) is very important to me, as well.

+1

Still experiencing it on 1.2.4. I guess I'll make an issue.

On Fri, Dec 4, 2015 at 12:21 PM Wliu notifications@github.com wrote:
Please fix this

This has already been fixed. Please make sure you're running a recent version of
Atom (1.2.x should be fine). If you're still experiencing this even on 1.2.x,
please file a new bug.

—
Reply to this email directly or view it on GitHub .

@50Wliu It is not fixed. It has never been fixed on OS X. Never. I have tested it in every single version since 1.0.4. Pretending it's fixed and asking others to open new bugs helps no one. To replicate:

1. Open Atom 1.3.2 on OS X 10.11.1.
2. Add a project folder, leave some tabs open, and close Atom.
   • Repeat Step 2 multiple times for extra fail
3. Reopen Atom by double-clicking a file associated with it, outside any project.
4. Atom completely forgets what was last open, and launches with a single window open to double-clicked file's folder, with single tab for the double-clicked file.

Pretending it's fixed and asking others to open new bugs helps no one

There are multiple people on Mac who report this working for them, so I repeat: please make a new issue, and include the information asked for in the debugging guide and CONTRIBUTING.md.

EDIT: I notice you already have - thanks :)

If it is then determined that this functionality has completely regressed, this issue will be re-opened.

Experiencing this on 1.3.2 and OSX 10.11.2

I think I have fixed this by doing

rm -rf ~/.atom/compile-cache

I was experiencing related symptoms on Ubuntu - a session from months ago was recreated on every restart of atom.

rm -rf ~/.atom/compile-cache

seems to have fixed the problem here as well - @snario thanks - first time I saw that suggestion.

Thank you to @snario -- that worked for me on Mac OSX 10.11.3, Atom 1.5.3. I'm using Atom-Project-Manager and it restored my last open project finally.

How did you figure that fix out and why did that fix it? Thanks again.

@snario Thank you! This worked for me as well.

For reference, issue #10044 tracks the "multiple window" bug in the implementation of this issue.

So is this issue fixed? Atom on 1.7.2 still doesn't remember to keep project folders in the sidebar.

+1，Atom 1.7.2 in my macos 10.11.4 doesn't keep my project

CoWinkKeyDinkInc @netfishx Please open new issues and provide all relevant information necessary to help track down your bugs.

+1，Atom 1.7.3 in my macos 10.11.4 doesn't keep my project

@KeinborgMichael Please open a new issue.

dear god why was this not implemented as a plugin and is instead baked right into the core editor? Can't the atom devs adhere by their own philosophies?

+1 Mac v10.11 and Atom 1.8.0 isn't keeping my state between relaunches of Atom

@niij Please open a new issue.

OSX Fix from old thread:

Unbelievable. Finally got it working.

Problem: On a mac, if you close using the red X button in the window, the Atom will still be running. So (now obviously) this is the state it saves, an empty atom.

So, you have to close it using Cmd + Q. Then it will restore correctly the next time.

PS: There should be an option in the settings to close the app completely with the X button.

Referenced in #6605, and hopefully implemented in Atom 1.8.0-beta0 via #11324.

Other temporary fixes include:

• Clearing the cache
  rm -rf ~/.atom/compile-cache
• And using the atom-project manager:
  apm install atom-project-manager

@Vvkmnn Thank you! Using CTRL-Q instead of the Red X works for me.

Note that this behavior is the default behavior of apps on OS X. An app can
be running, and it can optionally have windows.

On Mon, Jun 13, 2016 at 4:29 PM Brandon Annin notifications@github.com
wrote:

@Vvkmnn https://github.com/Vvkmnn Thank you! Using CTRL-Q instead of
the Red X works for me.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1603 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AADWlkXiD0pkHjLS00cFDOl_csXasE8Bks5qLWlBgaJpZM4Blkyg
.

Wout.
(typed on mobile, excuse terseness)

I have tried removing complile-cache and installing atom-project-manager. still not restoring my previous project on OS X, even if I close it with cmd-Q

怎么下载

@Leader138 请您用英文，所以别的人可以明白您在说什么呢。谢谢！您要下载什么？

Please use English, so that others can understand what you're saying. Thanks! What are you trying to download?

like @eliotsykes suggested on #10044 , Instead of opening my project folder with a symlink, I used the full path , and now when I exit atom with cmd+Q the project restores succesfully. however, if I just close atom clicking the red close button then It restores empty, so it seems like there are two separate problems, one with symlinks and one with atom saving a blank project on mac

I m using Atom 1.8.0 on Ubuntu16.04LTS x64, and it not reopen the files I opened last time.

@x13945 please open a new issue.

+1 mac not restoring the tree view if you close using the red x

@bb-git Please open a issue for this, if there isn't one already.

Since this was implemented a long, long time ago, I'm going to lock this to keep noise levels down. If you run into issues with Atom not restoring UI state correctly, please see the Contributing guide first, then open a new issue for it if there isn't one already.