Now that I have more a more documents written in Joplin, because is a wonderful tool that I enjoy to use, I have a feature request that will make my life a bit easier, and potentially other people’s life too.
I’m talking about the search functionality, that works like a charm, but when you have a notebook structure like mine, is a bit of a mess:
Technologies
Java
Documentation
Examples
Python
Documentation
Examples
Work
Task
Documentation
If you see in the example above, there are multiple “Documentation” notebooks, and when I use the search box, it shows in the result that the selected note belongs to the “Documentation” notebook, but I don’t know which one is the root folder, so then I have to go through all the notebooks manually searching for it.
I think it should be quite easy to implement to show the whole notebook path like:
Technologies > Java > Documentation
I am affected by this as well. I have repeated notes in a similar way so that searches for those terms are very confusing exactly as described in this. I essentially just accepted it and never search for those terms which I admit is a terrible solution and I would much rather it display the full path like you suggest.
I like that it does show the direct folder it is in but if it showed the full path it would be much better for context checking.
That would be great. I’d really like Joplin to have a way of quickly getting to the notebook that holds a note found by searching. It’s a feature I often used in Evernote.
This has already been added to the code by @laurent and will be available in the next release.
It doesn’t show the full path though, but when you click on it the folder and note is opened.
This feature is now available but finding the full path can still be difficult in a many level tree. I suggest that this option also expand and/or move the tree in the notebook pane until the chosen sub-notebook is visable. Other options might be:
for another click on the same pad triggers the expansion
for another click to briefly open a "tooltip" with the full path
Well, the folder is selected, but for some reason the parent folders are not expanded. IMO this worked at one point. So this seems like a regression. Please open a gh issue to track this.
The tree should have been expanded at the first click.
@tessus Sorry... I'm a 73 y.o. newbie to this with limited idea what a "gh issue" is and how to open one. A quick search shows you are the only one on this forum that uses the term.
Ok, no worries. A lot of people in this forum also have a github id. That's why I've suggested it.
It seems you don't, so I'll open the ticket.
But IMO this is a bug, so it should be fixed - hopefully soon.
