Skip to content

disable recall after first window #13

Closed
wants to merge 1 commit into from

2 participants

@cldwalker

When I open a second window, my files that were already recalled in the first window are recalled again. I'd like to disable this since I like a new window to start out as a clean state for a new workspace. Would you like this behavior? If not, could we add it as an option? Fwiw, the first window is 0, second is 1, etc.

Thanks for the plugin!

@joshuafcole
Owner

I think this is probably a good idea, but I'm not sure whether this is the best way to go about it.

The longterm plan (I've been swamped at work lately, but it's slowing finally) is to tie recall's persistence to the built in workspaces system of LT. That way, a given set of files will be opened for the current workspace on startup. Then, we'd simply open new LT windows with a fresh workspace and recall wouldn't recall anything.

Most of the piping is in place to do that already (using string workspace identifiers, pulling in files based on workspace name, etc). What remains to be wired up is:

  1. Get a unique identifier for the current workspace from LT (bonus points if it's human readable and can be slugified uniquely to a valid POSIX file name).

  2. Set up save and restore to use the current workspace name.

  3. Ensure recall doesn't try to remember files for the scratch (empty) workspace.

  4. Ensure LT opens new windows with a scratch workspace.

Of the 4, only #1 seems nontrivial. Do you think you can tackle those (or a subset of those?). If this is an important feature to you but you're not sure if you can tackle all of it, we can divvy up the work or I can just slap it together by the end of the weekend.

Cheers,
Josh

@cldwalker

I agree tying into workspaces is the more robust solution. I don't personally need this yet but if I do I'll pipe up to contribute.

@cldwalker cldwalker closed this Sep 24, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.