-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: support dendron style flexible hierarchies #194
Comments
Interesting idea, I think the functional part of parsing the dendron would be relatively simple. |
Cool! Well I have all my notes as top level files in root, so if it is implemented so that we can select any folder including the root folder that would work for that usecase. I guess you want to avoid filtering all files for files that have more than one example: |
@h0uter I've introduced this in 2.9.0 :) |
Thanks for implementing this feature. However, I'm still not activate it successfully. This is what I did to activate structures with dendron-type notes
But nothing still happen as expected in the |
@andrey-jef that sounds right. |
Is there a way to just get a tree view of all the notes if I have them organized in the Dendron way instead of using graphs or the child/parent display which isn't really necessary with Dendron style organization? |
@emillienemann Hey there :) |
@SkepticMystic thank you so much! That works really well. Is there any way to pin the view inside of my sidebar and be able to indent certain categories in the hierarchy? |
Hi,
I would like to use your plugin to navigate hierarchies based on dot indexed filenames.
(and eventually see these hierachies in a hierarchichal graph view)
As inspired by dendron
To give a short example:
math.matrix.sparse
is a note about sparsity in the context of matrices.I also have a higher level
math.matrix
note and above that amath
note.Similarly I have a
math.signal.fourier-transform
note whose parent ismath.signal
.In this way a note can function both as a folder and a file.
Another plugin is also looking into this with from a different perspective obsidian-structure
cheers!
The text was updated successfully, but these errors were encountered: