> One specific problem that killed it for me temporary is the lack of support for multiple vaults, to the point > that there is not even a truely centralized g

> One specific problem that killed it for me temporary is the lack of support for multiple vaults, to the point > that there is not even a truely centralized global configuation. Everything is saved in the vault itself, > including plugins. [...] Did this change in the meanwhile? You can invoke an overview, that lists the last five, or so, Vaults, you used. From there you can switch. But that is all. The configuration, and, yes, the plugins (yeez!), sadly, are still installed on a per Vault base. What I have done is to set up an empty Vault as a template, configure it the way, I would have my master preferences, and when I create a new Vault, I start by cloning that. It's not perfect, but better than nothing. Another thing I dislike is, that the Vault can not go into a (programming) project's folder as a sub folder, but considers the project folder as the Vault.