3 ms·
Thank you. But it does not solve the issue. The custom URI concept is too complex and alien in the Windows world. A Windows user would much better prefer to ha
by garganzol 4y ago
Thank you. But it does not solve the issue. The custom URI concept is too complex and alien in the Windows world.
A Windows user would much better prefer to have a special anchor file in Obsidian vault folder that could be double-clicked and treated by the standard and observable means.
This is why .txt files are so popular. A double-click and they work. The specialized tools may be 100 times better, but they often miss one important detail: frictionless entry. If something causes friction, especially at the start, then it gradually becomes a burden a user doesn't want to deal with.
However, you advice solves the issue for me because I'm a technical user and you have kindly presented the information. But just imagine how many of those who would totally miss that.
- criddell 4y agoThis is a great opportunity for you! This is a problem you know lots of people have and since you are a technical user, you could probably solve this for yourself and others in the same situation. Write a small application and register a file extension for it (maybe .obsidian). When you double click on sql.obsidian (for example), your app would launch read that file then launch Obsidian via the obsidian:\\ protocol. Your launcher app could also handle the creating of .obsidian files or (even better), write a plugin for obsidian to export a .obsidian file.