From a7ae9951fa515dc9e3e3a43753ec54a47ad81f27 Mon Sep 17 00:00:00 2001 From: plantarum Date: Mon, 25 Jan 2021 20:59:51 -0500 Subject: [PATCH] Documented icalendar capture templates It's not documented in gnus-icalendar, so the explanation comes straight from my reading of the code. --- mu4e/mu4e.texi | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 464557c6..5856be9e 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -3414,6 +3414,34 @@ To enable optional iCalendar→Org sync functionality, add the following: Both the capture file and the headline(s) inside it must already exist. +By default, @code{gnus-icalendar-org-setup} adds a temporary capture +template to the variable @code{org-capture-templates}, with the +description ``used by gnus-icalendar-org'', and the shortcut key ``#''. +If you want to use your own template, create it using the same key +and description. This will prevent the temporary one from being +installed next time you @code{gnus-icalendar-org-setup} is called. + +The full default capture template is: + +@lisp +("#" "used by gnus-icalendar-org" entry + (file+olp ,gnus-icalendar-org-capture-file ,gnus-icalendar-org-capture-headline) + "%i" :immediate-finish t) +@end lisp + +where the values of the variables @code{gnus-icalendar-org-capture-file} +and @code{gnus-icalendar-org-capture-headline} are inserted via macro +expansion. + +If, for example, you wanted to store ical events in a date tree, +prompting for the date, you could use the following: + +@lisp +("#" "used by gnus-icalendar-org" entry + (file+olp+datetree path-to-capture-file) + "%i" :immediate-finish t :time-prompt t) +@end lisp + @node Sauron @section Sauron