Tommy Kelly <tommy.ke...@verilab.com> writes: > C) entry (file+olp+datetree "test-datetree.org" "H1 "H2") ;; > filename plus heading and sub-heading > > Then I'd expect A) to use a datetree rooted at the file top level; B) > to use one underneath heading "* H1"; and C) to use one underneath ** > H2" (which itself is underneath "* H1"). > And in each case I'd expect it to create a new datetree at the > specified location if one didn't already exist. > > HOWEVER, it looks like that can break if there is already one or more > datetrees anywhere in the file AT A LEVEL BELOW THAT specified by the > template. > In that case, the position specified by the template is simply > ignored. Instead, the captured item is filed at first occurring > datetree of the above kind. > To be clear, that's even if there is also a pre-existing datetree at > the correct, template-specified location but further down the file.
Are you sure that what you describe is newly introduced? I'd expect this exact behavior since forever, judging from how `org-datetree--find-create' is implemented. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
