Hey guys, I think I get the basic idea, but I have a few questions…

  1. How do I just open up a note to check it out? I can see just opening the file regularly, but having each file start with a long sting of numbers leads me to think there’s some nicer, easier way.

  2. How do I go about having multiple “networks” one for work and one for home, etc. Do I just use folders?

Thanks guys!

  • Beteigeuze@feddit.de
    link
    fedilink
    arrow-up
    5
    ·
    1 year ago
    1. You can use org-roam-node-find which (maybe depending on your default completion framework, I use doom emacs btw. so some things are preset) let you type substrings of the actual title of the node to find it.
    2. This is a bit complicated, because there is no built-in way for having distinct buckets in Org-roam. But you can set directory-local variables in .dir-locals.el to achieve this.

    For example, put this inside the file /home/username/work/.dir-locals.el:

    ;; -*- mode: emacs-lisp; -*-
    
    ((nil . ((org-roam-directory . "/home/username/work")
             (org-roam-db-location . "/home/username/work/org-roam.db"))))
    

    Whenever Emacs opens a file inside the work directory, it will load and apply any variables in this file. Therefore you first must open a file inside the folder to access this files; open a file outside the directory to access the default ones.

    • 🅱🅴🅿🅿🅸OP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Thanks for the help! Would I be better off just having all work and other stuff together then? Or is it worth the hassle to use a work dir?

      • ggg@lemy.lol
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Check this out: https://codeberg.org/tekakutli/neuralnomicon

        I came across this guy who came up with a way to share some of his org-roam notes, and the strategy he uses could apply to your work situation. He keeps everything in one org-roam database, but for the notes he’s sharing with the general public:

        1. He stores them in a separate directory neuralnomicon/nodes.
        2. He tags them as neuralnomicon.