πŸ“š node [[problem with org roam s file level graphing]]
Welcome! Nobody has contributed anything to 'problem with org roam s file level graphing' yet. You can:
  • Write something in the document below!
    • There is at least one public document in every node in the Agora. Whatever you write in it will be integrated and made available for the next visitor to read and edit.
  • Write to the Agora from social media.
    • If you follow Agora bot on a supported platform and include the wikilink [[problem with org roam s file level graphing]] in a post, the Agora will link it here and optionally integrate your writing.
  • Sign up as a full Agora user.
    • As a full user you will be able to contribute your personal notes and resources directly to this knowledge commons. Some setup required :)
β₯… related node [[problem with org roams file level graphing]]
β₯… node [[problem-with-org-roams-file-level-graphing]] pulled by Agora

Problem with org-roam's file-level graphing

Slight problem at the mo being that org-roam's file-level graphing doesn't exclude the nodes in your exclude matcher. I started a thread to ask about that.

First thing that I tried was putting ~ ,@(org-roam-graph–expand-matcher 'file t)~ in org-roam-graph--build-connected-component. That didn't work, because

(files (or (if (and max-distance (>= max-distance 0))
	       (org-roam-db--links-with-max-distance file max-distance)
	     (org-roam-db--connected-component file))
	   (list file)))

already includes everything in files, so saying 'and not these other files' after the fact doesn't help. So next I've just simply hacked the SQL in org-roam-db--links-with-max-distance. Literally changes the raw SQL query. Obviously not sustainable, but gets me through what I want to do for today, and something to return to.

πŸ“– stoas
β₯± context