# Org-roam development status, May 2025 **URL:** \ **Category:** Development\ **Created:** [May 31, 2025, 6:34pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810 "2025-05-31T18:34:53Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [May 31, 2025, 6:34pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/1 "2025-05-31T18:34:53Z")
Hi gang, I’ve taken on a member role in the org-roam organization to help shepard the project along. This year I was able to bring things up to speed with built-in SQLite support for Emacs 29 and later, and work through CI issues. We have started addressing what I think is the biggest class of issues: performance. A PR to improve `org-roam-node-find` performance was recently merged, and [v2.3](https://stable.melpa.org/#/org-roam) was released to melpa-stable (after 3 years since the last release). I won’t be doing the lion’s share of active development myself, but will support those who do — and there are a few eager folks working at it. There are a ton of open issues and PRs in GitHub and a lot of them are quite old and have gone stale. I’m going to set up a workflow to auto-close dormant issues after 6 months of inactivity with a 2 week warning comment. If you have an issue or PR that you’ve been following and would like to see attended to, please give it a ping in the comment thread. I love org-roam. I use it every day. I appreciate this community and look forward to giving back. ❤ ---
**Author:** ![real-or-random](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/real-or-random/32/514_2.png) [@real-or-random](https://org-roam.discourse.group/u/real-or-random)\ **Post date:** [June 1, 2025, 8:15am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/2 "2025-06-01T08:15:33Z")
> [@dustinfarris](#): > > We have started addressing what I think is the biggest class of issues: performance. It may be worth looking into [GitHub - meedstrom/org-node: A notetaking system like Roam using Emacs Org-mode](https://github.com/meedstrom/org-node) by @meedstrom1. It reimplements many org-roam features but with a different and more performant database backend. Perhaps some of these improvements can be brought back to org-roam. ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 1, 2025, 1:59pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/3 "2025-06-01T13:59:30Z")
Definitely. @meedstrom has been very helpful in the [Master Issue for Making Org-Roam Faster](https://github.com/org-roam/org-roam/issues/2474). ---
**Author:** ![meedstrom1](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@meedstrom1](https://org-roam.discourse.group/u/meedstrom1)\ **Post date:** [June 1, 2025, 5:13pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/4 "2025-06-01T17:13:33Z")
To see some perf fixes for the `*org-roam*` buffer, you can check out what [org-node-roam-accelerator-mode](https://github.com/meedstrom/org-node/blob/324e946c992207cd0839da1d55024b2155ef2da3/org-node.el#L2855) does! I meant to upstream at some point but, uh, life. Happy to answer any questions. ---
**Author:** ![nobiot](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/nobiot/32/159_2.png) [@nobiot](https://org-roam.discourse.group/u/nobiot)\ **Post date:** [June 1, 2025, 6:08pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/5 "2025-06-01T18:08:05Z")
@dustinfarris Thank you for all you do! Happy to see v2.3 published. You are doing herculean work. Perhaps I can join force with you, do my bits and try to update the documentation – I have been wanting to go back to [Zero-to-Emacs-and-Org-roam](https://github.com/nobiot/Zero-to-Emacs-and-Org-roam) guide – but instead (and additionally), I could send some PR for the official documentation to be in line with Emacs 29 with SQLite embedded… Not immediately. I am pacing myself, looking at the rest of year 2025. ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 2, 2025, 7:37pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/6 "2025-06-02T19:37:30Z")
> org-node-roam-accelerator-mode will definitely check this out — i’d very much like your work to be brought in. totally understand about “life”! 😂 ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 2, 2025, 7:40pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/7 "2025-06-02T19:40:53Z")
Thanks @nobiot — your past contributions and participation in the community are a big part of what makes org-roam great. No pressure to do all the things all at once. I would like to see the following done by EOY, somewhat in order of priority: 1. Bug fixes 2. Performance improvements 3. Better test coverage 4. Documentation updates And then start looking at new features. ---
**Author:** ![akashp](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/akashp/32/1383_2.png) [@akashp](https://org-roam.discourse.group/u/akashp)\ **Post date:** [June 4, 2025, 10:06am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/8 "2025-06-04T10:06:37Z")
\*\* Suggestions for temporary buffers Fixes, performance 1. Org roam mode ```auto (defmacro org-roam-with-temp-buffer (file &rest body) "Execute BODY within a temp buffer. Like `with-temp-buffer', but propagates `org-roam-directory'. If FILE, set `default-directory' to FILE's directory and insert its contents." (declare (indent 1) (debug t)) (let ((current-org-roam-directory (make-symbol "current-org-roam-directory"))) `(let ((,current-org-roam-directory org-roam-directory)) (with-temp-buffer (let ((org-roam-directory ,current-org-roam-directory) ;; HHHH--------------------------------------------------- (org-inhibit-startup t)) ;; HHHH--------------------------------------------------- (delay-mode-hooks (org-mode)) (when ,file (insert-file-contents ,file) (setq-local default-directory (file-name-directory ,file))) ,@body))))) ``` Simple cache design > [@A way to cache the contents of the roam buffer?](https://org-roam.discourse.group/t/a-way-to-cache-the-contents-of-the-roam-buffer/3745/8): > > @bradmont Not, really but update the code then, I am giving you a more streamlined code block, replace the previous one with this (defvar org-roam-buffer-last-node nil "Stores the last visited Org-roam node for delayed redisplay.") (defun org-roam-buffer--scheduled-redisplay-h () (and (get-buffer-window org-roam-buffer) (org-roam-buffer--scheduled-fn))) (defun org-roam-buffer--scheduled-fn () (when-let ((node (org-roam-node-at-point))) (unless (equal node org-roam-buffer-las… 1. Wrap org-mode inside delay-mode-hooks otherplace ```auto (defun modified/org-roam-fontify-like-in-org-mode (s) (with-temp-buffer (insert s) (let ((org-ref-buffer-hacked t)) ;; (org-mode) (delay-mode-hooks (org-mode)) (setq-local org-fold-core-style 'overlays) (font-lock-ensure) (buffer-string)))) (advice-add 'org-roam-fontify-like-in-org-mode :override #'modified/org-roam-fontify-like-in-org-mode) ``` Please consider. Thanks. ---
**Author:** ![akashp](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/akashp/32/1383_2.png) [@akashp](https://org-roam.discourse.group/u/akashp)\ **Post date:** [June 4, 2025, 10:08am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/9 "2025-06-04T10:08:28Z")
My suggestions should close > > > \### Description > > I have two large files that I have added to org-roam. > > \- Fi…le 1: 93K lines, 3.8 MB > \- File 2: 10K lines, 0.5 MB > > Displaying the org-roam buffer on nodes which have backlinks in these files is very slow. The culprit is \`org-startup-indented\`. > > Below are 3 examples with \`org-startup-indented\` set to \`t\`or \`nil\`. Timings are determined with the following function: > > \`\`\`emacs-lisp > (benchmark-run 5 (org-roam-buffer-display-dedicated (org-roam-node-at-point))) > \`\`\` > > \#### Node 1 with 5 backlinks: > > \- 1 backlink in File 1 (93K lines) > \- 3 backlinks in File 2 (10K lines) > \- 1 additional backlink in very small node file > > Timings: > > \- t: (9.701741 86 5.583931) > \- nil: (0.33617 2 0.09160900000000005) > > \#### Node with 1 backlink in File 1 (93K lines) > > Timings: > > \- t: (5.49469 46 3.1563150000000064) > \- nil: (0.138881 0 0.0) > > \#### Node with backlink into small node files > > Timings: > > \- t: (0.038591 0 0.0) > \- nil: (0.022707 0 0.0) > > \#### Workaround > > I use the following advice to temporarily disable \`org-indented-startup\` around \`org-roam-buffer-render-contents\`. > > \`\`\`emacs-lisp > (defun vr/org-roam-buffer-render-contents-advice (orig-fun &rest args) > (let ((org-startup-indented nil)) > (apply orig-fun args))) > (advice-add 'org-roam-buffer-render-contents :around #'vr/org-roam-buffer-render-contents-advice) > \`\`\` > > This fixes the slowdown. Maybe it should be added to \`org-roam-buffer-render-contents\`? > > > \#### Steps to Reproduce > > Unfortunately, I cannot share the files. > > \#### Backtrace > > Backtrace without the advice on Node 1 with 5 backlinks: > > \`\`\` > 2801 50% - ... > 2801 50% Automatic GC > 2736 49% - command-execute > 2619 47% - funcall-interactively > 2613 47% - org-ctrl-c-ctrl-c > 2612 47% - org-babel-execute-src-block > 2611 47% - org-babel-execute:emacs-lisp > 2611 47% - progn > 2611 47% - benchmark-run > 2611 47% - benchmark-call > 2611 47% - #\ > 2611 47% - org-roam-buffer-display-dedicated > 2605 46% - org-roam-buffer-render-contents > 2605 46% - apply > 2605 46% - org-roam-backlinks-section > 2596 46% - org-roam-node-insert-section > 2523 45% - org-roam-preview-get-contents > 2156 38% - org-indent-refresh-maybe > 2086 37% - org-indent-add-properties > 1284 23% - org-at-item-p > 1245 22% - org-list-in-valid-context-p > 1186 21% - org-in-block-p > 168 3% - org-between-regexps-p > 130 2% org-in-regexp > 8 0% #\ > 2 0% #\ > 25 0% org-indent-set-line-properties > 277 4% - org-fold-core--fix-folded-region > 265 4% - org-fold-core-next-folding-state-change > 265 4% #\ > 60 1% - org-roam-preview-default-function > 60 1% - org-roam-end-of-meta-data > 59 1% - org-back-to-heading-or-point-min > 59 1% - org-before-first-heading-p > 59 1% - org-element-at-point > 59 1% - org-element--parse-to > 43 0% + org-element-org-data-parser > 8 0% + org-element--current-element > 16 0% + org-mode > 9 0% + set-auto-coding > 1 0% + org-roam-strip-comments > 1 0% + org-element--cache-after-change > 1 0% #\ > 25 0% + org-roam-fontify-like-in-org-mode > 1 0% + magit-section-ident > 8 0% + org-roam-backlinks-get > 5 0% + org-roam-node-at-point > 1 0% org-roam-buffer--dedicated-name > 1 0% + org-babel-get-src-block-info > 5 0% + execute-extended-command > 117 2% - byte-code > 117 2% - read-extended-command > 117 2% - read-extended-command-1 > 57 1% - completing-read-default > 14 0% + minibuffer-error-function > 2 0% + timer-event-handler > 6 0% + timer-event-handler > \`\`\` > > \#### Expected Results > > See above. > > \#### Actual Results > > See above. > > \### Environment > > \`\`\` > Copy info below this line into issue: > \- Emacs: GNU Emacs 29.1 (build 2, aarch64-apple-darwin21.6.0, NS appkit-2113.60 Version 12.7.1 (Build 21G920)) > of 2023-11-03 > \- Framework: Own configuration > \- Org: Org mode version 9.6.6 (release\_9.6.6 @ /opt/homebrew/Cellar/emacs-plus@29/29.1/share/emacs/29.1/lisp/org/) > \- Org-roam: 2.2.2- sqlite-connector: sqlite-builtin > \`\`\` And > > > \###### Motivation for this change > This pull request is aimed to fix the issue w…hen the preview sections of the backlinks inside an org roam buffer are not displayed where they should. > > Steps to reproduce: > 1. tested only on Spacemacs distro > 2. page-break-lines-mode, global-page-break-lines-mode, display-line-numbers-mode and global-display-line-numbers-mode are enabled in org mode buffer > 3. invoke org-roam-buffer-toggle to show up an org roam buffer > > Result: > \ > Also hitting RET on any section inside such buffer would result in the following error message: > \`\`\` > There is no thing at point that could be visited > \`\`\` > > Result if the fix is applied: > \ > > What is also interesting is that even without this fix, if we navigated to org roam buffer and called org-roam-buffer-refresh, the buffer would redraw just fine. But if we then navigated back to the original org mode buffer and triggered org roam buffer refresh (by, say, pointing to another node that has it's own backlinks), the problem would occur once again. > > I have no clear idea of why this happens, but here is a line that actually caused this issue: > \`\`\` > (defun org-roam-fontify-like-in-org-mode (s) > "..." > (with-temp-buffer > (insert s) > (let ((org-ref-buffer-hacked t)) > (org-mode) ;; after this call, the point inside the org roam buffer is set to 1 for some reason. this is why all the previews are displayed at the top of the buffer > (setq-local org-fold-core-style 'overlays) > (font-lock-ensure) > (buffer-string)))) > \`\`\` > > This fix is expected to close these issues: > https://github.com/org-roam/org-roam/issues/1732 > https://github.com/syl20bnr/spacemacs/issues/14969 ---
**Author:** ![dmg](https://avatars.discourse-cdn.com/v4/letter/d/5e9695/32.png) [@dmg](https://org-roam.discourse.group/u/dmg)\ **Post date:** [June 6, 2025, 9:24pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/10 "2025-06-06T21:24:32Z")
Thank you very much for helping with the development of org-roam. I do too: ❤ I love org-roam. I use it every day. I appreciate this community and look forward to giving back. " ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 7, 2025, 4:42am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/11 "2025-06-07T04:42:30Z")
Thanks @akashp . I’m looking these over. ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 7, 2025, 5:27am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/12 "2025-06-07T05:27:46Z")
@akashp would you mind approving this? > The difference is incredible. 😍 ---
**Author:** ![meedstrom1](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@meedstrom1](https://org-roam.discourse.group/u/meedstrom1)\ **Post date:** [June 12, 2025, 6:09am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/13 "2025-06-12T06:09:49Z")
You might be surprised to find it gets even faster if you also let-bind `org-agenda-files` to nil before enabling `org-mode`. And `org-element-cache-persistent` - as it’s a temp buffer, it just causes unnecessary work as far as I’ve understood. Perhaps that should be considered an upstream bug. So to make a proper org temp buffer: ```elisp (let ((org-inhibit-startup t) (org-agenda-files nil) (org-element-cache-persistent nil)) (delay-mode-hooks (org-mode)) (setq-local org-element-cache-persistent nil)) ``` Here I’ve set `org-element-cache-persistent` twice because enabling any major mode kills all local variables previously present. ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 14, 2025, 4:31pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/14 "2025-06-14T16:31:11Z")
Very cool! I’ll take a swing at this later today. ---
**Author:** ![liam](https://avatars.discourse-cdn.com/v4/letter/l/b9e5f3/32.png) [@liam](https://org-roam.discourse.group/u/liam)\ **Post date:** [June 28, 2025, 7:11pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/15 "2025-06-28T19:11:01Z")
Hi Dustin, Thanks a lot for picking up maintenance. I happened to revisit an old issue and noticed the stale bot. I went ahead and commented on a few issues that got closed that I think are still relevant (I’m hpfr on GitHub). Given the dormant period, I think attempting a reset on the open issues is reasonable. But can we maybe not lock them? Unless there is a big pattern of users commenting on old unrelated issues (doesn’t seem like it), it helps avoid needlessly fragmenting issues when the stale bot closes one prematurely and forces people to open a new duplicate. Feel free to add me to the repo to help triage issues if you want. I also have an old PR I should revisit… ---
**Author:** ![dustinfarris](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/dustinfarris/32/1055_2.png) [@dustinfarris](https://org-roam.discourse.group/u/dustinfarris)\ **Post date:** [June 28, 2025, 10:56pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/16 "2025-06-28T22:56:01Z")
Hey @Liam! Thanks for sifting through the closed issues, and thanks for voicing your thoughts on the issue lock automation. You’re right, it is heavy-handed. I went ahead and [disabled it](https://github.com/org-roam/org-roam/commit/1958e035fc185e45f2f0855093ae2ff57e1a510e). I’ve added you to the repo with write access. Feel free to reach out to me if you want to discuss anything one-on-one — my email is on my GitHub profile. I would like to say here in this forum that I don’t plan on unilaterally adding any future collaborators to the repo. For my part, if someone else wants to be added, I’ll seek consensus from the active collaborators. Thanks again! ---
**Author:** ![liam](https://avatars.discourse-cdn.com/v4/letter/l/b9e5f3/32.png) [@liam](https://org-roam.discourse.group/u/liam)\ **Post date:** [June 29, 2025, 6:52pm UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/17 "2025-06-29T18:52:29Z")
Thanks Dustin. I took a look at the most upvoted issues closed as stale to provide better resolutions where possible. I also opened a PR to clean up the docs build so we don’t need ox-texinfo+ anymore: > > > Jethro wrote the original docs build based on Magit’s docs build. Jonas has upda…ted it in the half-decade since. He deprecated ox-texinfo+ since Org 9.6 includes enough of its features. > > Org-roam is simpler than Magit and has less available maintainers. Remove some of the unused features inherited from Magit: > \- remove AUTHORS.md which was not kept updated past the initial implementation > \- remove epub and pdf targets which were not deployed > \- remove Elisp-related variables since Org-roam uses Eldev > > The result is simple enough to consolidate default.mk into doc/Makefile. ---
**Author:** ![liam](https://avatars.discourse-cdn.com/v4/letter/l/b9e5f3/32.png) [@liam](https://org-roam.discourse.group/u/liam)\ **Post date:** [July 2, 2025, 2:48am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/18 "2025-07-02T02:48:11Z")
I went through a ton of stale issues and reopened a bunch I believe are relevant. There’s still a ton of cruft the bot cleared out, thankfully. I set up a [milestone for 2.4.0](https://github.com/org-roam/org-roam/milestone/13) based on fix PRs that have been open for a long time plus some other cleanup. I am pretty much on board with Dustin’s priorities in [#7](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/7) (you got lucky with your unilateral addition 😛). I am somewhat concerned about the capture-related issues; upstream Org capture is really convoluted and Org-roam’s additions don’t exactly help the situation. My thinking is to do those last and maybe set up a branch with the fixes for power users to test. If anyone has (or wants) experience there, your assistance is most welcome. Once the bugs are under control I agree performance needs some attention. In the issues it looks like @akashp and @dmg (and @meedstrom1 before he seceded 😛) have some good threads to pull on. ---
**Author:** ![gcoladon](https://yyz2.discourse-cdn.com/free1/user_avatar/org-roam.discourse.group/gcoladon/32/976_2.png) [@gcoladon](https://org-roam.discourse.group/u/gcoladon)\ **Post date:** [July 17, 2025, 9:09am UTC](https://org-roam.discourse.group/t/org-roam-development-status-may-2025/3810/19 "2025-07-17T09:09:28Z")
Thank you for all your efforts to keep this project alive! I use org-roam almost all day long now, and of course could continue to use it for at least a while if support ended, but would hope to be part of the ongoing long term support of it instead.