![]() Since this is already within Templater, it’s easy to then create the new files and applying templates to them. Maybe a little easier would be to write Templater execution commands to scan the vault directories for all files, and see which source files are present, and if the corresponding markdown files is present. This event is possible, with some coding experience, to handle and create a new file (if it doesn’t exist from before) with a corresponding template. I’ve not done too much of this, and this kind of belongs in a plugin, but events are sent by Obsidian when various stuff happen, and I reckon there is an event for when a new file is detected as coming into the vault. To create corresponding markdown files, I see three alternatives: Hook on to the event which detects new files in the vault, scan for all files and create corresponding markdown files, and externally use the make system of your coding environment create corresponding markdown if needed. Its documentation says: Show files with any extension even if Obsidian can’t open them natively, so that you can link to them and see them in File Explorer and Quick Switcher. Enable that in Settings > Files & Links > Detect all file extensions. md, I reckon that’s something you need to turn on. ![]() There is an option in Obsidian to show all file extensions, and not just. You’re talking about sharing the vault files in between various source files (and possibly binary files), so that could possibly become a little messy. I’m not sure if this can be handled by only tools within Obsidian or not.
0 Comments
Leave a Reply. |