-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feature request: show the entire folder path instead of the folder name #11
Comments
Currently it shows "parent folder - folder", or just the folder name if it's a topmost element. Not sure about those "IBM" elements. Are they stored in the bookmark toolbar? |
You are right! Actually, I did not remark the "Parent folder - Folder" feature, because I already use this type of naming in my folders (as in "Hardware - Tools - IBM servers")... |
I support this idea. I have the exact same problem, i.e. having several folders with the same name but in different parts of my whole folder tree. e.g. reference/php as syldub69 suggests, change the hint from having hyphens '-' to '/' (or '') indicating different folders. Another cool feature would be to also highlight the matching text, and even match children folders based on a matching parent name, (i.e. not only match final folders, but any level) utils Then I could choose among all those, and not just the utils parent folder. IMO it would make the add-on MUCH more useful. |
I would like this feature too. I would probably like the entire folder path to be shown below each entry in a smaller font, or as a pop-up tooltip when you hover over a given folder. |
Would it be possible to have an options to show the entire folder path instead of the folder name?
I often have the same folder name in many different locations (because I use the same structure of folders in the Bookmarks Toolbars and in the Bookmarks Menu).
And I have a lot of nested folders, it is not easy to know which one is the accurate one for storing the bookmark if I only see the folder name.
The text was updated successfully, but these errors were encountered: