On 2026-10-24 07:10, Richard Lawrence wrote:
pinmacs <[email protected]> writes:
On 2026-10-20 08:06, Richard Lawrence wrote:
Looking more closely at how org-capture works, I see I can't expect to
put stuff into org-capture-plist myself, because that's overwritten by
the capture template entry at the beginning of org-capture. But there
are a variety of variables I can let-bind, e.g. org-capture-initial,
org-overriding-default-time, and org-capture-link-is-already-stored. So
that's probably the right approach...?
(...)
Thanks! So basically, you're binding your own variable (containing a
plist) around org-capture, and then using Elisp forms in your templates
to read that variable, right?
I confirm
That's more or less the approach I've settled on, with the addition that
I'm also binding org-capture-initial and org-overriding-default-time so
a simple template like "* %i %T" works.
Neither of these variables is documented, though -- I'm not sure if
that's just an oversight, or if it means "Please don't use this as a
public API".
Yes that looks more risky than defining our own vars, in any case, it
would be nice to document/agree on how to extend org-capture to do all
that tricks, that are nice for some of the users like ours, to guide
other users to achieve the same, if they want, and also, to
protect/preserve that functionality on future developments
Cheers,
pinmacs
