Adam Porter

> If you have activity auto-saving on (which is the default), an activity will pretty much always have a "last" state, even if it's only lightly modified from the default...

> One oddity I've found: when I `revert` an activity (which I use instead of kill), I'd expect its last state to be removed. It isn't, and sometimes as a...

Thanks for the screenshot. > Couple things I think still need a bit of thought: > > 1. Active activities get saved automatically, which always updates their `time`. I guess...

> Have you ever seen the persist file disappear? It's happened to me twice in the past few days while hacking on this. I note that persist removes the file...

I have a lot going on right now, so it may be a while before I can review this further. I appreciate your patience.

> Gentle ping on this one. Been in active use for quite some time without any issues on my end. Thanks. My to-do list is quite long and my time...

> > Forgive the additional round of review and comments. If you don't have enough "steam" to make some of the stylistic changes, I can make them myself before merging....

I don't think this is necessary, or even necessarily beneficial. * If a user calls `activities-revert` and then wishes he hadn't, he could, e.g. kill the frame/tab before its state...

> Wow. I have been having lots of friction and thought I was going crazy using activities. I believe this is why. Please be specific about the problematic behavior you...

> One possibility to preserve both behaviors and retain the possibility of your "undo" trick (though IMO it's of questionable value) is not to delete `last` or save, but instead...