obsidian-alfred
obsidian-alfred copied to clipboard
hauselin
Can I bypass vault selection if I only have 1 vault?
I only have one vault so would like to skip the step of having to choose the vault when it comes to creating a new empty note, for example. Is this possible?
That's not possible right not. I'll consider implementing it in a future release.
Understood, thanks for your reply. Yes please do consider it for a future release if you can. I believe that a lot of people in the Obsidian community are moving to having a single vault even when they have a very large and diverse portfolio of notes, so I think its usefulness would be wide.
On 22 Jul 2021, at 17:13, Hause Lin @.***> wrote:
That's not possible right not. I'll consider implementing it in a future release.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhauselin%2Fobsidian-alfred%2Fissues%2F35%23issuecomment-884946449&data=04%7C01%7C%7Cc3a7871423a940fb228108d94d1aebd8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637625600281431925%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ilpnVefM%2BWSG9a3VofeGIcoo5M2MhRpEt8x1fA%2BUyAY%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAULLIMMTSVHESJL5BVDXXQTTZARRVANCNFSM5AZP4RVA&data=04%7C01%7C%7Cc3a7871423a940fb228108d94d1aebd8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637625600281441882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=S7VNpIzFroReqEz%2BiLNGv55k54g31HPVx%2FUnK9wyULg%3D&reserved=0.
Hey @hauselin, can I try working on this? I would like to add some other features too, like option add a note directly via alfred. But this seems a good starting point.
@hauselin I looked at the workflow in detail, and I think the best way to provide this functionality would be the following. introduce two new variables - defaultVaultPath and defaultVaultName add a new input "oadddefaultvault" to change/add the default vault name and path. on addition of first new vault, it is automatically made the default vault as well (it can be changed via above input anytime later) current "on" keyword is remapped to "onv" (v=vault) "on" is now used to add directly to add to the default vault [Vault name shown in title by showing "Creating {query} in {defaultVaultName}]"
I have done a basic testing of above flow. Please let me know your thoughts.
@hauselin I looked at the workflow in detail, and I think the best way to provide this functionality would be the following. introduce two new variables - defaultVaultPath and defaultVaultName add a new input "oadddefaultvault" to change/add the default vault name and path. on addition of first new vault, it is automatically made the default vault as well (it can be changed via above input anytime later) current "on" keyword is remapped to "onv" (v=vault) "on" is now used to add directly to add to the default vault [Vault name shown in title by showing "Creating {query} in {defaultVaultName}]"
I have done a basic testing of above flow. Please let me know your thoughts.
I am basing above thought on the philosophy that many users will like to have a default vault at least even if they they don't just have a single vault. Users with single vault will directly be able to use the functionality without any configuration. Also we can use the default vault config to add other default functionalities as well, example search etc.