Uncaught Syntax Error: Unexpected token D about save-session HOT 18 CLOSED

I'm not sure. I don't see a syntax error there (I don't even see a capital D). I'm assuming you have restoring files per project off?

This is probably not it, but it could be an issue with the json? In that case, I just pushed an update that should solve that. But again, I don't think you'd get plain syntax error for that.

from save-session.

I installed the new atom .137 and save-session 8.9 and now it just doesn't work at all. There isn't a project json being created

from save-session.

Well, it seems to be having very odd behavior. Around the 5th time trying, it restored everything. It did miss some text I had input into an unsaved document, but got everything else. Upon closing and opening again it remembered the folder, but no files.

from save-session.

Ok, I figured out one of the issues. In one of my projects, I have a todo folder that is a symlink to dropbox. I like to be able to open different type todo lists inside of my projects and I use dropbox to sync them with todo.txt apps. If I have any files open from inside of that todo folder, it breaks opening all files.

from save-session.

Since there is no event for loading projects (that I've found), projects currently get saved when the window gains focus. That means that just opening a project that doesn't open a new window, it won't save the project right away. I'll bet that when it worked, you alt-tabbed away from and back to Atom.

As for symlinks, I haven't tested them, so I'm not sure if they will work or not, but it sounds like not.

from save-session.

Ok, I have stopped opening the symlinked items but now I can't get it to work properly.

It will work maybe 1 in 10 opens, but the rest just will not open the files. I am trying to troubleshoot it further now.

from save-session.

This makes me think my issues might not have been the symlink after all.

from save-session.

When i try to uninstall I get the following error:

Failed to delete save-session: ENOTEMPTY, directory not empty 'C:\Users\username.atom\packages\save-session\projects'

I will manually delete it and then try to uninstall and reinstall.

from save-session.

Ok, odd. The directory is empty.

In my previous comment, I accidentally deleted a "" and the path was correct.

from save-session.

Uninstalled that time. However, problem still remains.

I think I am going to get some lunch. I will try reinstalling atom when i get back.

from save-session.

Any update on this?

from save-session.

I tried reinstall and also tried updating to 138 and getting the same
result.
On Oct 17, 2014 5:39 PM, "Michael Peterson" [email protected]
wrote:

Any update on this?

—
Reply to this email directly or view it on GitHub
#24 (comment)
.

from save-session.

Still the syntax error? If you could answer a few questions, that may help figure out what's going on here.

1. What are your settings for Save Session
2. Can you list the packages you have installed apm list (just the user installed ones)
3. Is the ~/.atom/save-session/projects folder empty? Does it have directories in it? Does it have project.json files in the directories?
4. If you've tried, has it worked with a symlinked file yet (I haven't tested this yet)? edit: I have now tried them and they are working for me.

from save-session.

1. My settings have everything checked except "Restore Open Files Per Project"
2. For packages installed, I have the same results when I disable all user installed packages except save-session and themes/languages. I can try removing all langauges and themes as well, but didn't really see them having an impact on save-session.

I did find one very odd thing that I haven't been able to explain. I tried swapping back to the default atom black theme and ui and it started working, I have now swapped back to the themes I was using and it is still working. I am not quite sure why that would have caused issues and why it is working fine after swapping back.

1. The save-session folder is not empty. It partially restores. The only thing that doesn't get restored is the open files themselves. When opening new documents I can see the file grow and can even open it and see where it is adding new documents.
2. After swapping to default themes and swapping back to Seti and Monokai Black and White, the symlinked documents are opening just fine.

I am going to start gradually changing things to see if I can break it again and find the actual cause.

from save-session.

So does it completely work now or just partially? That is strange that your theme may have fixed it. I'm assuming that was a coincidence.

from save-session.

So far it is running fine, working perfect actually. It is the first time unsaved/untitled documents are being remembered as well. Even if I don't select another window first.

I don't get it either. I tried disabling all addons and plugins. None of it had an impact. Simply changing my theme back to a default Atom one and back has it working again. I am still using the same themes as I was prior to changing back. I've even enable all of my plugins back and disabled and enabled them back and forth after closing and opening the app and it still seems to be working.

Any other ideas of things I could do to try to break it again? I am trying to figure out just what was going on.

from save-session.

Yeah I have no idea, I messed around with your settings and couldn't get it to break at all. I'm glad it's working for you now though.

Anyway I'm going to close the issue. Feel free to reopen it (or a new one) if you figure anything out.

from save-session.

Will do. It is very strange. Today i have even been working on a custom
syntax and editing a language. I was back and forth between multiple
different themes/syntax dozens of times testing them out and I still have
not had that come back.

What makes it make even less sense, is I had totally uninstalled
save-session, atom, and even upgraded to a new version of atom through the
troubleshooting process. Disabling all plugins except themes didn't work.
It wasn't until swapping to the atom dark theme that it started to work.

On Tue, Oct 21, 2014 at 5:19 PM, Michael Peterson [email protected]
wrote:

Yeah I have no idea, I messed around with your settings and couldn't get
it to break at all. I'm glad it's working for you now though.

Anyway I'm going to close the issue. Feel free to reopen it (or a new one)
if you figure anything out.

—
Reply to this email directly or view it on GitHub
#24 (comment)
.

from save-session.