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

IDEA: directory replication of each .org file on harddisk, then adding for each friend link a symbolic link to that directory #373

Open
michaelsjackson opened this issue Sep 19, 2021 · 4 comments

Comments

@michaelsjackson
Copy link

michaelsjackson commented Sep 19, 2021

Had following idea for linux mainly, and how it might be useful. I was thinking could there be a way of replicating an org-brain network on the harddisk as a directory structure. It seems this could be done via symbolic links for friend links.

Example: I have 3 org documents. A.org B.org C.org all in a main directory.

What should the new feature do?
For each .org file it should generate a directory with same name as the .org file, thus in above example it would generate the three directories: A B C under main directory.

Now if I add from A to B a friend link in org-brain. This feature would do following: creating inside directory A a symbolic link to directory B. Same in the other directory in the other direction.

When removing the friend link, this symbolic links should be removed as well.

What would be the gain? You would have replicated your entire org-brain network structure, at least the friend link structure as symbolic links. It would help profiting from your generated network structure also in the form of directories where you could add some extra files, documentation.

Any ideas, comments are welcome.

@pmnerfed
Copy link

or I was thinking that org-brain could have the functionality of marking two headings/nodes/files as a representative of the same thing or duplicate of the same thing.
What I mean by that is we may have two different headings that represent(or duplicate of) the same entity.

If that is possible. I think we can mark the kind of copy you are talking about as a duplicate
PS: I realize there might be a lot of complications that arise from this feature that might need to be addressed.

@Kungsgeten
Copy link
Owner

To me this is beyond the feature set of org-brain. It seems more suitable as a separate package if someone requires this. I'd like to point out that you can attach files to entries with the attach feature.

@pmnerfed What kind of use case do you envision where you need several nodes for the same concept? Wouldn't it be enough to link the two+ entries with each other, if you needed something like this?

@michaelsjackson
Copy link
Author

michaelsjackson commented Dec 25, 2021

Attach feature I never use. Usually any file: links are shown as resources in org-brain anyway. So this feature works automatically already, which is great. My idea is just making symbolic links more useful, in the context of org-brain. And any other tools which can use symbolic links nicely, like eagle mode. http://eaglemode.sourceforge.net/

org-brain <---> directory structure <---> eagle mode
all inter operating, thanks to symbolic links.

Do all your work in org-brain, but profit from this also in directories and eagle mode. That was the idea. I am sure there should be more tools which can make use of symbolic links.

@michaelsjackson
Copy link
Author

or I was thinking that org-brain could have the functionality of marking two headings/nodes/files as a representative of the same thing or duplicate of the same thing. What I mean by that is we may have two different headings that represent(or duplicate of) the same entity.

If that is possible. I think we can mark the kind of copy you are talking about as a duplicate PS: I realize there might be a lot of complications that arise from this feature that might need to be addressed.

Duplications are not good, did you try org-transclusion which is like duplication, but without duplication. Symbolic links are best way of duplication in my opinion. Make 1000 copies, without wasting any space but gaining the advantages of all the linked content.

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

No branches or pull requests

3 participants