Settings Sync #6569
Replies: 7 comments 5 replies
-
VS Code's setting sync has worked out pretty well for me, really smooth, completely forget that it's there, but I never liked that my settings were stored somewhere privately; I liked my settings being stored in a location I had control over. That might be a bit biased since I came from Atom prior and having to sync my settings with a GitHub Gist. |
Beta Was this translation helpful? Give feedback.
-
What I'd like to see: Sync Settings has four commands: backup to remote, restore from remote, create profile, and switch profile. They all look at a git repository in any code host (github/gitlab/bitbucket, etc) Sync Settings prompts you for that repository's URL on first launch, and automatically gets/sets up an access token if needed (if the repo is private). Then it downloads that repo and uses it to set up the editor. Inside the repo is plaintext settings files in folders. Each folder is a complete configuration setup (settings + keybinds + extensions/packages + whatever else) and the folder name is the name of a profile (e.g. work, writing, rust, etc.). If exactly one folder exists, it is treated as the default for all operations. The default is otherwise the folder named If you have multiple profiles, you can relaunch the editor with a different profile using the switch profile command. |
Beta Was this translation helpful? Give feedback.
-
I really like the "settings repository" plugin for CLion. I point it to a git repo and it does the rest. I appreciate the simplicity of the VScode sync, but it's also a bit shady isn't it. (Yes, I'm aware of the JetBrains sync plugin that works similarly to VSCode as well). The reason I prefer settings sync that's sort of built-in vs a third party is two parts, the first part is trust, the second part is support. By trust I mean, I'm perhaps a paying customer of Zed and I can trust that the feature is implemented by the company and I'm trusting a single entity in this situation (I don't have to worry about a rogue update to the extension that starts to siphon off secrets from my computer). By support I mean, since it's a tier 1 product feature and so will support sync'ing all relevant settings, extensions, and themes. I don't have to worry about it getting abandoned (like I worry about most of the Sublime ecosystem). |
Beta Was this translation helpful? Give feedback.
-
I would be happy even to be able to change the location of the settings json file to a shared folder (dropbox or google drive or apple cloud or whatever) to be able to keep the settings in sync between my two machines. If we adopted this for my team at work, it would be great to have the option of sharing settings with the whole team (with the choice of using the team shared settings or not). |
Beta Was this translation helpful? Give feedback.
-
is there any reason why settings sync couldn't happen via source control, like other dotfiles? |
Beta Was this translation helpful? Give feedback.
-
settings and keymap. |
Beta Was this translation helpful? Give feedback.
-
whats the latest update in syncing your settings, extensions, etc across multiple devices right now? Thank you! |
Beta Was this translation helpful? Give feedback.
-
We've had a few issues come up asking us to add a settings sync feature to Zed:
While this is not currently on our roadmap, and it will likely not be added anytime soon, I'm interested to hear what all users would want from this sort of a feature. What all would you want synced and restored between different computers running Zed?
Beta Was this translation helpful? Give feedback.
All reactions