Allow users to customize the path of override config folder

[ariehen]

Global Settings / Same settings, themes, and plugins across multiple vaults

Current problem Most users have spent hours highly customizing Obsidian to meet our needs and preferences via settings, themes, CSS snippets, plugins, etc. But whenever we add a new vault—or want to temporarily designate a folder as a vault to use Obsidian on the files inside it—that’s all left behind, as if we’re opening Obsidian for the very first time. The only workaround (see below) is cumbersome. Proposed solution Option 1: Add the option to store the .obsidian configuration folder as …