Hi,
I've been using file+olp+datetree in my org-capture-templates and I
really appreciate the recent enhancements made to datetrees.
However, in my personal usage of fole+olp+datetree, I actually found the
default possible target specifications lacking. As per the docstring,
they are currently:
(file+olp+datetree "path/to/file" "Level 1 heading" ...)
(file+olp+datetree
"path/to/file" function-returning-list-of-strings)
(file+olp+datetree
"path/to/file" symbol-containing-list-of-strings)
Will create a heading in a date tree for today’s date.
If no heading is given, the tree will be on top level.
To prompt for date instead of using TODAY, use the
:time-prompt property. To create a week-tree, use the
:tree-type property.
For me, I have several templates that want to dynamically select (i.e.,
during the capture) not only the outline path (olp) of the target, which
I can do with
(file+olp+datetree
"path/to/file" function-returning-list-of-strings)
but also the target file.
Do we think it worthwhile to add a specification that accepts a function
for the file path, like the following?
(file+olp+datetree
function-returning-file-path function-returning-list-of-strings)
Alternatively, we have both the file and the outline path be a single
function that returns a list of strings whose car is the file and cdr is
the outline path, like
(file+olp+datetree
function-returning-file-path-and-outline-path-as-list-of-strings)
Right now, I get around the limitation by using the function target
specification
(function function-finding-location)
and having the function be variant of the datetree target selection
portion in org-capture-set-target-location that lets me choose which
file I'd like to capture to.
--
Best,
Kristoffer
