We have a tree with folders and files and i really love it and prefer it over tags. My idea is about creating symbolic links which look like a single note (file) in the tree but it redirects to the note (or folder) somewhere else in the hierarchy.

When sb makes this kind of link in the root it's something similar to shortcuts on the Windows desktop which allow to run frequently used software/folders faster than by opening folders to find program (or a NOTE in our case).

I guess you are missing Edit -> Insert -> Hyperlink feature. It allows inserting hyperlinks to tree items.

That's not what i am talking about...I'm talking about creating symlinks inside tree, not inside a note so clicking on the symbolic link would result with jumping to different path. That's why i explained it's similar to what shortcuts on Windows do and what are they for and why are they so commonly used.

I'll give you an example what i want it for: i have a schedule with sth and it's divided into years and years divided into months. I would like to have a shortcut in the root for the currect month which i can remove every month and replace with new month. Of course i could copy that note from different location but it's not good solution because i can make some changes and i would have to do the same in both locations.

------------

Obviously there is small difference between symbolic link (mainly known from linux) and and shortcut (Windows).

Symbolic link would show a note from different location but it wouldn't redirect it in the tree, and your internal links (link://) could be referred to symlink path too.

Shortcut would only redirect to different location so it would just do what links do.

Every implementation would be better than nothing, however i'd recomend to do it as a symbolic link.

Additionally symlink can be a solution when sb wants to put a note in 2 categories (2 folders) in the same time.

"mx100" wrote:Symbolic link would show a note from different location but it wouldn't redirect it in the tree.

Thx for the reply!

Some further thoughts:

- When you modify a note inside symlink you modify source however when you delete symlink source note remains untouched.

- In operating system when the source path is unreachable it simply does nothing. It will happen when the path will be inside area which is protected by password... however you may want to ask for that password anyway.

Of course it will also happen when the source path doesn't exist. So then you might ask for deleting itself because source path doesn't exist. To prevent that situations you may register all related symlinks in source note when creating symlinks, unregister it when removing symlink, and ask for deleting all related symlinks automatically when deleting source note (only if there are any).

- What if you move source note? If all symlinks would be registered as above you may want to update their paths when moving source note or at least ask for it.

- You might extend it to external links (showing a note from another ddb file) - it would be cool too :)