From: Carsten Dominik <dominik@uva.nl>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Allowing multiple date trees in a single file
Date: Wed, 18 Jan 2017 06:53:46 +0100 [thread overview]
Message-ID: <CADn3Z2JBEEpE=C+VBm8q5XfkTqDwcfeH4YtvpeM6PoCOyEXjgQ@mail.gmail.com> (raw)
In-Reply-To: <871sw1zice.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
On Tue, Jan 17, 2017 at 6:50 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Carsten Dominik <dominik@uva.nl> writes:
>
> > Another way to implement this would be to use different VALUES for the
> > DATE_TREE/WEEK_TREE property - maybe that would actually be a somewhat
> > cleaner implementation.
>
> I think ":DATE_TREE: week" ":DATE_TREE: t" is cleaner, indeed.
>
This is not quite what I meant.
I meant
:DATE_TREE: my_diary
:DATE_TREE: food_and_health
:DATE_TREE: movies watched
>
> > I'll rethink that and I will also define a test.
>
> I also agree there's an opportunity to refactor this and come out with
> a more generic interface.
>
> Yet another option is to define new capture targets, e.g.
>
> - file+datetree+olp
> - file+datetree+olp+date
> - file+datetree+regexp
> - file+datetree+regexp+date
> - ...
> - file+weektree+olp
> - ...
>
> Those would ignore WEEK_TREE and DATE_TREE properties altogether.
>
Yes, one could have additional ways - but I am not going to take out the
existing ones, which would needlessly break things with various users.
Another thing I was thinking is a way to force prompting for a date, for
example through a prefix argument, so that a single capture template could
be used for using the current date and optionally a set one.
Carsten
>
> Regards,
>
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 2389 bytes --]
next prev parent reply other threads:[~2017-01-18 5:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 16:46 Allowing multiple date trees in a single file Carsten Dominik
2017-01-16 7:45 ` Nicolas Goaziou
2017-01-17 12:19 ` Carsten Dominik
2017-01-17 17:50 ` Nicolas Goaziou
2017-01-18 5:53 ` Carsten Dominik [this message]
2017-01-18 11:23 ` Nicolas Goaziou
2017-02-03 14:08 ` Carsten Dominik
2017-02-04 12:48 ` Nicolas Goaziou
2017-02-05 10:40 ` Carsten Dominik
2017-02-06 13:06 ` Nicolas Goaziou
2017-01-18 20:19 ` Samuel Wales
2017-01-19 12:57 ` Carsten Dominik
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADn3Z2JBEEpE=C+VBm8q5XfkTqDwcfeH4YtvpeM6PoCOyEXjgQ@mail.gmail.com' \
--to=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).