You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest transcluding and embeding Notes, Sections and Blocks. In Obsidian, the said transclusion is as follows, with a ! mark before [[ for embeding:
[[source note]] or [[source note| aliases]]
[[source note # section]] or [[source note #section | aliases]]
[[source note #^ block]] or [[source note #block | aliases]]
As for transcluding notes (and for popview as an additional most-appreciated feature) suggested in #48 , @rockmanvnx6 has done great work.
As for the suggested features here-in, I am not sure whether or not they can be achieved in the following ways:
fetch the source note , as been done by @rockmanvnx6,
seach the section or block (or block ID) in the fetched note
merge the content of the said section or block and display it in the webpage.
Unfortunately, any programming skills are out of my reach. What I can do is nothing but suggesting the feature and expecting community members' contribution.
Thanks again!
The text was updated successfully, but these errors were encountered:
Thanks to peter and all other contributors.
I would like to suggest transcluding and embeding Notes, Sections and Blocks. In Obsidian, the said transclusion is as follows, with a
!
mark before[[
for embeding:[[source note]]
or
[[source note| aliases]][[source note # section]]
or
[[source note #section | aliases]][[source note #^ block]]
or
[[source note #block | aliases]]As for transcluding notes (and for popview as an additional most-appreciated feature) suggested in #48 , @rockmanvnx6 has done great work.
As for the suggested features here-in, I am not sure whether or not they can be achieved in the following ways:
Unfortunately, any programming skills are out of my reach. What I can do is nothing but suggesting the feature and expecting community members' contribution.
Thanks again!
The text was updated successfully, but these errors were encountered: