feat!(capture): add option to create entry ids

This un-breaks a breaking change where we addressed an issue that
prevented ids from being generated for 'entry' capture types.  While
this was a much-asked feature, the change also disrupted user workflows
that depend on the old behavior of entries creating org headings and
nothing more.

Users can now opt in to generating a heading id by passing
`:entry-node t` in their org-roam capture templates definition.

Amend: ed94524964
This commit is contained in:
Dustin Farris
2025-09-29 16:20:57 -07:00
parent 41f9a10be5
commit 0799985296
4 changed files with 99 additions and 41 deletions

View File

@@ -847,7 +847,9 @@ of the template are similar to ~org-capture~ templates.
automatically chooses this template for you.
2. The template is given a description of ~"default"~.
3. ~plain~ text is inserted. Other options include Org headings via
~entry~.
~entry~. Note that ~entry~ type captures create regular Org headings
without IDs by default. To create an Org-roam node with an ID, use
the ~:entry-node t~ option.
4. Notice that the ~target~ that's usually in Org-capture templates is missing
here.
5. ~"%?"~ is the template inserted on each call to ~org-roam-capture-~.
@@ -1221,6 +1223,10 @@ Here is a sane default configuration:
"#+title: %<%Y-%m-%d>\n"))))
#+end_src
Note: The ~entry~ type capture above creates a regular Org heading without an
ID. If you want each daily entry to be an Org-roam node with its own ID, add
~:entry-node t~ to the template.
See [[*The Templating System][The Templating System]] for creating new templates.
*** Usage