Like, optionally using the user config dir as a default for vault settings.
19 Likes
One use case:
Iād like to have my hotkeys across vaults, but not necessarily keep the same theme per vault. Iām the same user, using the same app, it is just that the content has been changed. Now I have to manually move my config file and I realize that the moment my muscle memory fires, but there is no response from the app.
Also having some plug-ins on and off for certain vaults would be useful.
So, to elaborateāsome parts of the settings should be per vault, others should be āper userā.
13 Likes
This is huge! I have to manually set the same shortcut keys and preferences over and over again for each vault. No fun! 
I would also like to see Global Settings. Now that v0.76 has separate config and workspace files, could the workspace one be made into a centralized/global/default settings that applies to all vaults, or at the very least applies to new vaults?
1 Like
Yeah, if the settings include editer,plugings,hotkeys and so on can be export or import, can reduce a lot time to reset in other vaults.
+1 - I got bit by this in my first walk-through - I was going through the Obsidian Help vault and playing with things, and I added some keyboard shortcuts and tweaked a few settings. Then I went to my own vault and it was all gone; took me a bit to find where the Help vault was stored in my file system, so I could just grab the config file from there!
Is there any update regarding this feature? It is kind of redundant to copy configs from vault to vault.
1 Like
I second this feature request.
Manually checking and copying the same settings to every new vault I create is time consuming and kind of frustratingā¦
Edit: Oh, I just realized that simply copying the .obsidian/config file works just fine.
In other words, there is no need to navigate across every single config option as I had been doing (doh!)ā¦ Simply copy the .obsidian/config file from an old vault to a new one and, voila, you now have the same configs.
1 Like
Is there any issue with copying the cache and workspace files from one vault to another? Just making sure there wonāt be any complications later on.
Enjoying Obsidian so far, thank you (and all the best too !)
I ended up making two vaults (I usually end up with at least two namespaces in all my tools, at the very least I always have a ālife vs workā separation (or I try to, lol)).
I wanted to add a hot-key for āTodayās notesā and it was super-easy to do this, really like how straightforward it was.
However, I then had to go add it for the other vault too, after wondering āwhy isnāt this keyboard shortcut working anymore?ā for a while.
And ā¦ this made me wonder, should hotkeys be global or vault-scoped?.
I can see the case for keeping it the way it is: (1) there might be hotkeys that only make sense for a specific vault, or (2) it allows the app to not have any global state.
On the other hand, hotkeys are usually for the app as a whole; the way I imagine them, I add or change hotkeys when I want to change āthe way I use the appā.
So: not a complaint, just a thought, thanks again for a great product.
6 Likes
One idea would be to support configuration on different levels (e.g. per user, per vault) similar to how it is done in Git where you can overwrite the user configuration per repository. In Obsidian, the per-vault configuration would overwrite the per-user configuration.
2 Likes
This would be great, ideally itād be great to have one dotfile generated only for the hotkeys, this file could easily be shared accross vaults and to other people.
Currently, what I do to share my hotkeys accross vaults is to copy the .obsidian file (a hidden file in the vault)
this not only copies hotkeys, but also all settings, such as plugins and editor settings.
This is a workaround and Iām still not sure if Iām missing downsides to this approach.
In mac, for showing this hidden file in finder, go to your folder of the vault that has the shorcuts and press
Cmd + Shift + .
now you can copy this file to your other vault.
If you are in Windows or linux just search āhow to show hidden files or dotfilesā
hope that helps, Iād love to know if thereās a better approach
1 Like
afaics each vault is a separate instance. I donāt think thereās much thatās āglobalā.
Yes, but as I suggested above, Obsidian could e.g. support a per user hotkey configuration in ~user/.obsidian in addition to vault/.obsidian. Each vaultās instance would first lookup the per user configuration and then merge in the configuration from its vault. Of course, global configurations could also be stored under /etc or in the Windows registry.
2 Likes
Hi all! I just installed Obsidian today by the recommendation from a colleague. So far it looks great but Iāve ran across a few annoyances, this being one. I spent a considerable amount of getting the shortcuts right for me. I was quite surprised to find the shortcuts didnāt work in the āhelp vaultā.
As already suggested, it would be great if one could define global settings under ~/.obsidian or ~/.config/obsidian which could then be overriden by the vault specific settings. Then again this complicates things as it wouldnāt then be straightforward to edit global/default settings vs. vault specific. It would require something like VSCodeās settings management.
For me the keyboard shortcuts matter the most. It would already help if the keyboard shortcuts would be defined in a separate file from config. This way you could create a symlink to this file between projects (as a workaround).
1 Like
I agree, @ristomatti specially with what you said on making the shortcuts a separate config file. This way it can easily be shared with others (and across vaults) without having to copy the whole .obsidian directory.
And like you said, from there symlinks could be created without any issues.
1 Like
Is there any solution to restore default setting for hotkeys?
Came here looking for a solution for global settings, saw this thread. +1 to this feature. 
1 Like
Same here, Iām starting out and only have 2 vaults and the frustration of āwhy isnāt this working I already changed the hotkey (or some other editor setting)ā has already bitten me.
A home directory to store the global settings that are overridable by each vault setting sounds great to me.
1 Like
Iād like to expand this to include Plugins, CSS etcā¦ It seems to me that all of this should be stored in a global obsidian repository, and then vault-level preferences select/apply what is wanted/needed. If Iām not mistaken, VS Code is basically like this - Extensions, Themes, Settings etcā¦ get applied per Workspace.
As it stands, I have different plugin versions installed in different vaults, when youād think that updates would be applied globally (along with being able to select which plugins are turned on for each vault, and how their settings are configured in each as well)