From: Carsten Dominik <dominik@uva.nl>
To: org-mode list <emacs-orgmode@gnu.org>
Subject: Subject: Use of date trees in Capture has been modified
Date: Thu, 16 Mar 2017 08:55:09 +0100 [thread overview]
Message-ID: <CADn3Z2+AanLPvUO9ENhZ_2tkAvsmdnq9ewR3sFasn=zV--shXg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Dear all,
I have just pushed (to master) a patch that modifies the use
of date trees in capture templates. If you don't use them,
no need to read on.
We used to have 4 different capture targets that work with date trees:
file+datetree, file+datetree+prompt, file+weektree,
file+weektree+promt.
All these are now consolidated to a single new target,
file+olp+datetree, which also allows for the optional specification of
an outline-path to build the tree under a specific headline instead of
at top level in the target file. In this way, you can have several
date trees in a file. The type of tree (month or iso-week) is now
controlled with a property :tree-type, the option to force a
date/time prompt is controlled by the property :time-prompt.
For the time being, the old targets will be automatically translated
and used correctly. When you use customize to change
org-capture-templates, things will automatically be updated next time
you change the variable. The recommendation is to go and update your
templates, in case at some time in the future, we might remove the
compatibility layer.
Let me know if any issues arise.
Carsten
[-- Attachment #2: Type: text/html, Size: 1473 bytes --]
next reply other threads:[~2017-03-16 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 7:55 Carsten Dominik [this message]
2017-03-16 8:34 ` Subject: Use of date trees in Capture has been modified Alan Schmitt
2017-03-16 11:41 ` Carsten Dominik
[not found] <59779b8073fa4f0683216c82e6ec9cce@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-16 9:39 ` Eric S Fraga
2017-03-16 10:10 ` Carsten Dominik
[not found] ` <b855abbe7ad14fcfbd3f76767d8a4a0b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-03-16 19:12 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADn3Z2+AanLPvUO9ENhZ_2tkAvsmdnq9ewR3sFasn=zV--shXg@mail.gmail.com' \
--to=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.