Not sure if I should file this here or at org-mem.
Started a few months back, these behaviours:
On a fresh start-up, I have some custom-defined functions that don't work:
(defun org-node-goto-today ()
(interactive)
;; (org-node-cache-ensure) ;; [[mu4e:msgid:meedstrom/org-node/issues/100/2897734113@github.com][Re: [meedstrom/org-node] Dailies capture via org-roam templates in 3.0 (Issue #100)]]
(let ((org-node-file-timestamp-format "")
(org-node-file-slug-fn #'org-node-slugify-for-web))
(progn
(org-node-seq-goto "d" (format-time-string "%F"))
(goto-char (point-min))
(bms/add-other-auto-props-to-org-roam-properties)
(goto-char (point-max)))))
(defun org-node-goto-next-day ()
(interactive nil org-mode)
(let ((org-node-file-timestamp-format "")
(org-node-file-slug-fn #'org-node-slugify-for-web))
(org-node-seq--goto-next "d"))
;; (org-node-series-dispatch-dailies)
)
(defun org-node-goto-prev-day ()
(interactive nil org-mode)
(let ((org-node-file-timestamp-format "")
(org-node-file-slug-fn #'org-node-slugify-for-web))
(org-node-seq--goto-previous "d"))
;; (org-node-series-dispatch-dailies)
)
-
If I run org-node-goto-today on initial start of Emacs, I get the message, "No seq for key "d", maybe do M-x org-mem-reset?".
-
If I run org-node-find, I generally see all of my nodes already present (at least if I've waited a bit after start-up), which makes me feel like org-mem-reset has already run. But, ok, so if I now run org-mem-reset and wait a bit, then org-node-goto-today works. I guess the seq's are initialised yet, but it seems like just jumping to today's date should require less machinery.
-
Relatedly, if I run org-node-goto-today and say that ends up creating a new file for today's daily, if I then go off and do something else and then call org-node-goto-today again, I get a message "Resetting cache because file seems to already have contents: /home/emacsomancer//org-roam/daily/2026-04-13.org", and indeed, the cache seems to be reset, as I subsequently get what I think of as the "I've started" message, i.e. "Some IDs share title, see M-x org-mem-list-title-collisions" (which mainly happens because some file-internal node have IDs and some of things are called the same thing, e.g. * journal :personal:).
Not sure if I should file this here or at org-mem.
Started a few months back, these behaviours:
On a fresh start-up, I have some custom-defined functions that don't work:
If I run
org-node-goto-todayon initial start of Emacs, I get the message,"No seq for key "d", maybe do M-x org-mem-reset?".If I run
org-node-find, I generally see all of my nodes already present (at least if I've waited a bit after start-up), which makes me feel likeorg-mem-resethas already run. But, ok, so if I now runorg-mem-resetand wait a bit, thenorg-node-goto-todayworks. I guess the seq's are initialised yet, but it seems like just jumping to today's date should require less machinery.Relatedly, if I run
org-node-goto-todayand say that ends up creating a new file for today's daily, if I then go off and do something else and then callorg-node-goto-todayagain, I get a message"Resetting cache because file seems to already have contents: /home/emacsomancer//org-roam/daily/2026-04-13.org", and indeed, the cache seems to be reset, as I subsequently get what I think of as the "I've started" message, i.e."Some IDs share title, see M-x org-mem-list-title-collisions"(which mainly happens because some file-internal node have IDs and some of things are called the same thing, e.g.* journal :personal:).