From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Subject: Use of date trees in Capture has been modified Date: Thu, 16 Mar 2017 08:55:09 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ec9bc88e9f2054ad462a8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1coQFw-0001C3-H5 for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 03:55:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1coQFv-00081V-Qc for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 03:55:32 -0400 Received: from mail-io0-x22e.google.com ([2607:f8b0:4001:c06::22e]:36008) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1coQFv-00081M-M0 for emacs-orgmode@gnu.org; Thu, 16 Mar 2017 03:55:31 -0400 Received: by mail-io0-x22e.google.com with SMTP id l7so36462910ioe.3 for ; Thu, 16 Mar 2017 00:55:31 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: org-mode list --001a113ec9bc88e9f2054ad462a8 Content-Type: text/plain; charset=UTF-8 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 --001a113ec9bc88e9f2054ad462a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear all,

I have just pushed= (to master) a patch that modifies the use=C2=A0
of date trees in= capture templates.=C2=A0 If you don't use them,
no need to r= ead on.

We used to have 4 different capture target= s 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 als= o allows for the optional specification of
an outline-path to bui= ld the tree under a specific headline instead of
at top level in = the target file.=C2=A0 In this way, you can have several
date tre= es in a file.=C2=A0 The type of tree (month or iso-week) is now
c= ontrolled 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<= /div>
and used correctly. When you use customize to change
or= g-capture-templates, things will automatically be updated next time
you change the variable.=C2=A0 The recommendation is to go and update yo= ur
templates, in case at some time in the future, we might remove= the compatibility layer.

Let me know if any issue= s arise.

Carsten

--001a113ec9bc88e9f2054ad462a8--