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
- Fix org-roam-capture--adjust-point-for-capture-type to properly handle
cases where point is positioned after head content but not at a heading
- Remove redundant location-type logic that incorrectly assumed point > 1
means we're at a heading (file+head can position point after keywords)
- Restore call to adjust-point-for-capture-type that was removed in ed94524
- Add comprehensive tests for plain capture ordering and assertion error fix
- Refactor adjust-point-for-capture-type for better readability
Amend: ed94524964Fix: #2540
* (fix)capture: fill-template preserve whitespace content
Preserve the whitespace content given in the capture template, by
caching it and then appending it to the output template. For
Org-capture's purposes, we need to separately ensure that a newline is
present. Adds tests to the various helper functions to illustrate changes.
Addresses #2115
