-
Notifications
You must be signed in to change notification settings - Fork 468
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
"Copy link to node" for external use [feature request] #2452
Comments
When I do not find a built in feature I look for workarounds. That is my approach. Research XML treeelement parsing in Python. I am using CherryTree as the hub of a number of processes. |
…e cherrytree document and hierarchical path to node (#2452)
Hello @jonathonmckay I added more information to the link to node (and to the link to anchor) when pasted to a non rich text node or outside of cherrytree. |
Excellent. This is exactly what I was hoping for. Thank you so much. |
I've been using CherryTree for a couple years now, and am completely loving it.
That said, there are a couple thing I'd like to see added some day to make it even better.
(I'll raise them separately. Apologies if there is already threads for them that I missed)
I find the "Copy link to node" super useful for cross referencing related notes.
However, occasionally it'd like to copy a link or path to a node for pasting into another application (A task tracker, email, documents, etc). However, all that gets pasted into the other application is something like "node: 07 Thu"
I'd like to see a menu / tool bar option to "Copy node path" or something like that, that could copy to the the clipboard something along the lines of "\path\to\CTfile - path / through / the / nodes", basically as displayed at the top of the editor window, with the path and file its from (optionally) tacked on the front.
Extra awesome (but not at all necessary): Make it paste as some kind of link, that would trigger CherryTree to open the correct file and navigate to the correct node. This would likely require registering some kind of URI handling with the OS, I would expect.
The text was updated successfully, but these errors were encountered: