Date-tree capture confused when nearby trees have dates

Date-tree capture confused when nearby trees have dates

[Suvayu Ali]

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]

Hi Orgers,

I came a cross a curious problem.  When I try to capture with the
following template:

(setq org-capture-templates
      '(("m" "Meeting notes" entry (file+datetree "~/tmp/tests/target.org")
	 "**** %^{prompt} %U\n%?")
	))

Capture gets confused and cannot find the real date-tree if there are
nearby trees with headlines like this:

  ** 2013 June - Event 2
  ** 2013 March - Event 1

You can replicate this by using the file target_before.org (attached) as
a capture target.  I expect the captured entry to go under

  * 2013
  ** 2013-04 April
  *** 2013-04-15 Monday

Instead it goes under "Topical lectures" as shown by target_after.org
(attached).

Is this a bug, or am I making a mistake?  Any ideas?

-- 
Suvayu

Open source is the future. It sets us free.

[-- Attachment #2: target_before.org --]
[-- Type: text/plain, Size: 272 bytes --]

* Topical lectures
** 2013 June - Dark Matter
   <2013-06-10 Mon>--<2013-06-12 Wed>
** 2013 March - Accelerators
   <2013-03-20 Wed>--<2013-03-22 Fri>


* 2013
** 2013-04 April
*** 2013-04-12 Friday
**** Some meeting notes [2013-04-12 Fri 14:37]
Stuff ... and more stuff.

[-- Attachment #3: target_after.org --]
[-- Type: text/plain, Size: 385 bytes --]

* Topical lectures
** 2013 June - Dark Matter
   <2013-06-10 Mon>--<2013-06-12 Wed>
** 2013-04 April
*** 2013-04-15 Monday
**** Testing meeting notes [2013-04-15 Mon 00:53]
Really important notes!
** 2013 March - Accelerators
   <2013-03-20 Wed>--<2013-03-22 Fri>


* 2013
** 2013-04 April
*** 2013-04-12 Friday
**** Some meeting notes [2013-04-12 Fri 14:37]
Stuff ... and more stuff.

Re: Date-tree capture confused when nearby trees have dates

[Bastien]

Hi Suvayu,

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> Capture gets confused and cannot find the real date-tree if there are
> nearby trees with headlines like this:
>
>   ** 2013 June - Event 2
>   ** 2013 March - Event 1

Fixed, thanks.

Note that you can still use tags in a datetree.

So

** 2013

and

** 2013   :noexport:

are equivalent.

Thanks for reporting this!

-- 
 Bastien

Re: Date-tree capture confused when nearby trees have dates

[Suvayu Ali]

On Thu, Apr 18, 2013 at 12:21:42PM +0200, Bastien wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > Capture gets confused and cannot find the real date-tree if there are
> > nearby trees with headlines like this:
> >
> >   ** 2013 June - Event 2
> >   ** 2013 March - Event 1
> 
> Fixed, thanks.

I can confirm the problem is gone.  :)

> Note that you can still use tags in a datetree.
> 
> So
> 
> ** 2013
> 
> and
> 
> ** 2013   :noexport:
> 
> are equivalent.

I can't think when I would use it, but I'll keep that in mind.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: Date-tree capture confused when nearby trees have dates

[Bastien]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> I can't think when I would use it, but I'll keep that in mind.

Yep, I added a footnote for this in the manual.

-- 
 Bastien