Closed oatmealm closed 2 years ago
Hi! No, there's no such functionality at the moment. It would be interesting to hear about the use case.
I have something implemented this way, so far. It's based on the idea that a document I'm working on is placed in it's own directory somewhere.
Where the document has this local variables set for the document. It's generic, so can be used in a template I guess.
* Meta :nobrain:
# Local Variables:
# eval: (setq org-brain-path default-directory)
# End:
Seems to work. Plus if the document's sub-directory is placed in the global org-brain-path, then I could link to this document, but clearly not the other way around, which I'm thinking, might be useful. The idea is to reduce noise. If I'm "mapping" a document I'm analyzing, I'm mostly interested in creating links between parts of the document itself (and sometimes reference something outside of it - though for my use-case it's not a priority).
Also, maybe I should explain that this is NOT a zettelkasten pattern, clearly. I wanted to use `org-brain's visualized buffer to navigate a large corpuse of text I'm analyzing for my self, or want to present, and actually use as an overview, while being able to show connection between parts of the text.
Okay, I see. I think you could simply put the document in its own (sub)folder and use M-x org-brain-switch-brain
to choose that folder. I haven't used multiple brains much myself though, and it was quite some time since I implemented the feature.
Oh, OK, I missed that :) I'll give it a try. Is there a mechanism to link two "brains" as well?
You could use the brainswitch link in the body of an entry. Search for it in the README :)
I know this is not the intended use-case, but I'm wondering if it's possible to restrict
org-brain
to only work on the currently active document? i.e. all available actions will only query heading in the document from which they're invoked...