Skip to content
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

Add links to anchor or node in other cherrytree file #2609

Open
cas-ady opened this issue Nov 19, 2024 · 2 comments
Open

Add links to anchor or node in other cherrytree file #2609

cas-ady opened this issue Nov 19, 2024 · 2 comments

Comments

@cas-ady
Copy link

cas-ady commented Nov 19, 2024

Add link for a cherrytree file and add the node or anchor in the link.

link my_file.ctx -anchor anchor_name -> open the file my_file.ctx and go directly to the anchor named "anchor_name"
link my_file.cth -node node_name -> open the file my_file.ctx and go directly to the node "node_name"

Describe the solution you'd like
A clear and concise description of what you want to happen.

@cas-ady
Copy link
Author

cas-ady commented Nov 19, 2024

In the below menu
image
add another bullet named external Cherrytree file. Select the file cherrytree file and add a reference (cherrytree node or anchor) the reference (in a text field)

@gitvectors
Copy link

gitvectors commented Nov 22, 2024

As an experimenter I often browse these feature requests. And often find "workarounds" to apply to my own workflow.
But this feature request sparked some new ideas. For which I thank you.
In my case there is a need to interconnect many CT documents on my desktop. Mostly *.ctd extension.
The protocol you suggest does not meet my requirements.
But rather than write it up here (where it might be lost) I intend to create a workflow. Indeed it might be configured into a CherryTree container as a routing node. Broadly there is a need to build a "satellite view" of CT objects which are realised as a "vector database". There can be multiple connections to multiple CherryTree documents. I don't see any forum which expands beyond "issues" and feature requests" into "CherryTree ideas box".

In your case I would exploit the CherryTree command line features and create a link which opens remote CT via command line. For a deeper understansing of my own thinking, install Recoll, index your entire desktop, then apply queries such as "ext:ctd" (list all files with extension *.ctd). My workflow centres on using Recoll as the indexer of every CT document in my desktop. Your connection can then be via recoll command line. Such as recollq ext:ctd. You will then see a list of every *.ctd document in CT command console. But extracting that Recoll raw index data to engineer a vector database is the next step I will develop further. An orchard of CherryTrees.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants