this post was submitted on 27 Oct 2023
1 points (100.0% liked)

Emacs

314 readers
2 users here now

A community for the timeless and infinitely powerful editor. Want to see what Emacs is capable of?!

Get Emacs

Rules

  1. Posts should be emacs related
  2. Be kind please
  3. Yes, we already know: Google results for "emacs" and "vi" link to each other. We good.

Emacs Resources

Emacs Tutorials

Useful Emacs configuration files and distributions

Quick pain-saver tip

founded 1 year ago
MODERATORS
rglullis
raphael
1
How to create a personal wiki in emacs? (alien.top)
submitted 1 year ago by Far-Anywhere2876@alien.top to c/emacs
9 comments fedilink hide all child comments
 

I know this question has been asked before and I know about org-roam, I am just not sure if org-roam is the right solution for me. Right now, I use one big org file to take notes which I export to pdf. This works nicely, but it would be nice to also have access to the concepts in the larger org file at a granular level (ie. bite-sized notes which reference one another and are organized based on their subject matter). I would also like to tag information that is not in org format, if possible. I was thinking that org-roam & org-transclusion could be used to make main subject files, while org-roam could be used to make a link to an embedded pdf that comes from the concept I am referencing, when I don't need to explicitly review the material in whatever notes I am taking. Has anybody done anything like this? Any tips are appreciated. Thanks.

you are viewing a single comment's thread
view the rest of the comments
[–] Far-Anywhere2876@alien.top 1 points 1 year ago (1 children)

What about if I want to capture multiple pieces of information as different nodes under the same headline?

[–] Lantre@alien.top 1 points 1 year ago

A node id is a property under the file or org-headline so I don't think you can add multiple nodes to a single headline. Maybe if you explain your use case a bit, there might be a better suggestion?

If the bits of info are different enough then the best bet would be to have them as separate sub-headings. If bits of into are mostly related then you could consider either using aliases or tags.