Hello,
Carsten Dominik writes:
> We do disagree here a bit. This little bit of extra work just keeps the
> existing templates working. We do not introduce a really different
> structure of the org-capture-templates. Rather, the code introduces a new
> target type, and it makes some older targ
Hi Nicolas,
thank you for taking the time to look at the proposed changes in detail.
My replies and comments are below.
On Sat, Feb 4, 2017 at 1:48 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Carsten Dominik writes:
>
> > Attached is a patch that does the following:
> >
> > It consolidates all fou
Hello,
Carsten Dominik writes:
> Attached is a patch that does the following:
>
> It consolidates all four different org-capture target types that have to do
> with
> date/week trees into a single one, called `file+olp+datetree'. This target
> allows for an optional outline path specification t
Hi Nicolas,
ok, here is where I have gotten with this:
Attached is a patch that does the following:
It consolidates all four different org-capture target types that have to do
with
date/week trees into a single one, called `file+olp+datetree'. This target
allows for an optional outline path spe
Hi Samuel,
Yes, this is of course also a very good solution that avoids the
overhead of a date tree. One of the reasons why the dates
in Org are in ISO format was to make them sortable by
a simple text sort. Thanks for sharing.
Carsten
On Wed, Jan 18, 2017 at 9:19 PM, Samuel Wales wrote:
> as
as an aside, just wanted to point out an alternative that i use
exclusively instead of date trees. of course it is not for everybody
and i do not want to hijack the thread, so followups should have a
different header.
* CONVERSATION [2017-01-15 Sun 14:09] talked with carsten
i sort these i
Hello,
Carsten Dominik writes:
> I meant
>
> :DATE_TREE: my_diary
> :DATE_TREE: food_and_health
> :DATE_TREE: movies watched
It sounds less useful because we already have ways to identify uniquely
a heading.
> Another thing I was thinking is a way to force prompting for a date, for
> example t
On Tue, Jan 17, 2017 at 6:50 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Carsten Dominik 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
Hello,
Carsten Dominik 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.
> I'll rethink that and I wi
Hi Nicolas,
thanks for your reaction.
By default, a day or week tree will assume that it is the only thing in a
file when it is created and handled.
The exception is that if you have an Org entry with a property
DATE_TREE: t
that the date tree will be placed under that specific node. But since
Hello,
Carsten Dominik writes:
> here is a patch that allows to have multiple date trees or iso-week trees
> in a single file by allowing to specify the property name that will be used
> to place the tree. The property name can be set in org-capture-templates,
> individually for every template
Hi everyone,
here is a patch that allows to have multiple date trees or iso-week trees
in a single file by allowing to specify the property name that will be used
to place the tree. The property name can be set in org-capture-templates,
individually for every template if so desired. I use that t
12 matches
Mail list logo