-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Workspace Persistence #640
Comments
Do you mean, save this in the workspace folder, or in the user's config folder? |
I would rather save this at the top of the project directory. Just like VSCode and Sublime Text does. That way, I can save it in my repo, wipe and reinstall from the repo and still have the same configuration for editing the project. |
Usually that just ends up in the gitignore file since not everyone on the team uses the same settings or even editor. I like how atom does it which saves it somewhere in the config directory. |
Labeled |
…and window state (#1703) * add Filesystem.getStoreFolder * expose Filesystem.getOrCreateConfigFolder * add definition of Persistence "items" * add definitions for Global store * add store instantiation * add logic to write to file * trigger on state change * add Workspace store * persist workspace store on move and resize * remove cliOptions from StoreThread in favor of explicit arguments * move Cli from Core to bin_editor * fall back to persisted working directory if not specified on the command line * read store file on instantiation * add get function to retrieve an item from the store * make state.workspace non-optional * set window size and position initially based on persisted workspace settings * post-rebase fix * fix warning * add interface * refactor * special case hash for "global" * fix window positioning * add bool codec * persist maximized window state * cache store file path * use Luv for non-blocking I/O on persist * fall back to Documents instead of working directory * move Persistence infrastructure to Core * forward store infrastructure functions to builtin stores * refactor store API for great good * simplify builtin store API * fix tests * handle missing store path more gracefully * Switch to new Dir API * Use forked dir for now * Update lockfiles * Formatting Co-authored-by: bryphe <bryphe@outrunlabs.com>
I'd like to add the concept of a session to Onivim 2, which would include the following:
We'd save this information to a specific location in the user's folder, likely as JSON.
On load, we'd pick up this persisted info and restore the user's workspace / session.
Related:
The text was updated successfully, but these errors were encountered: