Tim Pope

Maybe it's getting hung up overwriting the existing file? Maybe try adding a `delete(g:this_obsession)` before it? (Although that kind of defeats the purpose of the change.)

The file in `g:this_obsession` shouldn't be open at that point, no.

I am going to give this some bake time in my personal config before evaluating merging it in. It does have the potential to confuse/annoy people into uninstalling the plugin.

When I call Vim with `-S`, and I also have that autocmd, and the session in question changes the current directory, I get an error. Here's my fix: ``` autocmd...

I favor squashes, but a merge isn't on the table in the short term so feel free to leave it for now.

What happens if I have a bunch of files open and then I `:cd` to a directory that has a session file? Does it blow away all my existing tabs...

You want to make `:cd` prompt? Are you out of your mind? Make a new command!

Was `~/.config/nvim/sessions/test` originally created by Obsession?

If you call `:Obsession` to pause, it stops saving *future* changes, but the current state is still saved. Does that explain things?

I'm not keen on the comment highlighting. (`Comment` is pretty much the only group that always means what it says.) Got any other ideas? I'd be okay with doubling up...