From: Carsten Dominik <carsten.dominik@gmail.com>
To: Charles Cave <charles.cave@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Bug report: filing into a date tree in year 2011 when 2010 exists in file
Date: Tue, 4 Jan 2011 07:24:18 +0100 [thread overview]
Message-ID: <04D3058F-17E9-47AA-99A2-E6D729176B2E@gmail.com> (raw)
In-Reply-To: <loom.20110104T044436-262@post.gmane.org>
What would be helpful is a minimal file that, as a date-tree target,
reproduces the issue. I am sure the problem could then easily be found.
- Carsten
On Jan 4, 2011, at 4:48 AM, Charles Cave wrote:
>> Carsten Dominik <carsten.dominik <at> gmail.com> writes:
>
>> Strange, for me this worked without any problems this morning.
>
> I have found that the new year was created in other files but it
> definitely
> misbehaves in my taskdiary.org file.
>
> I can only assume there is a pattern of characters that fools the
> algorithm
> for locating the headline
>
> I did another test and this is what the sparse tree looks like:
>
> * 2010
> :PROPERTIES: ...
> * 2010-10 October...
> * 2010-11 November...
> * 2011-01 January
> * Testing
> Added [2011-01-04 Tue 14:45]
>
> I will keep checking the data and see if I can locate the offending
> text.
> It is annoying to see the years out of sequence
>
> Charles
>
> http://twitter.com/#!/ozcaveman
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-04 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 21:59 Bug report: filing into a date tree in year 2011 when 2010 exists in file Charles Cave
2011-01-01 7:13 ` Carsten Dominik
2011-01-01 9:27 ` Ian Barton
2011-01-04 3:48 ` Charles Cave
2011-01-04 6:24 ` Carsten Dominik [this message]
2011-01-04 7:07 ` 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=04D3058F-17E9-47AA-99A2-E6D729176B2E@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=charles.cave@gmail.com \
--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 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).