From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: fix confirmed (was: Re: Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)])
Date: Tue, 3 Feb 2015 22:27:01 +0100 [thread overview]
Message-ID: <20150203212701.GG1231@boo.workgroup> (raw)
In-Reply-To: <87bnlc449s.fsf@nicolasgoaziou.fr>
Hi Nicolas,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [02. Feb. 2015]:
> Gregor Zattler <grfz@gmx.de> writes:
>> adding a date to the datetree in the org-agenda-diary-file
>> produces a mess:
>>
>> - emacs-snapshot -Q -L /home/grfz/src/org-mode/lisp/ -nw –eval (setq org-agenda-diary-file "/tmp/diary.org")
>> - Mx org-agenda
>> - a
>> - i
>> - d
>> - error
>>
>> gives:
>>
>>>>>>>>>>>>>>>>>
>>
>> * 2015
>> ** 2015-02 Februar
>> <2015-02-01 So>*** 2015-02-01 Sonntag
>> **** error
>>
>> <<<<<<<<<<<<<<<<<<<<
>>
>>
>> instead of:
>>
>>>>>>>>>>>>>>>>>
>> * 2015
>> ** 2015-02 Februar
>> *** 2015-02-01 Sonntag
>> **** error
>> <2015-02-01 So>
>> <<<<<<<<<<<<<<<<<<<<
>
> This should be fixed. Thank you.
Confirmed, thank you.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2015-02-03 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 21:23 Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)] Gregor Zattler
2015-02-02 17:22 ` Nicolas Goaziou
2015-02-03 21:27 ` Gregor Zattler [this message]
2015-02-04 16:37 ` fix is with another glitch when adding two dates (was: Re: Bug: org-agenda-diary-entry messes with datetree in org-agenda-diary-file [8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)]) Gregor Zattler
2015-02-05 9:06 ` fix is with another glitch when adding two dates Nicolas Goaziou
2015-02-06 14:08 ` Gregor Zattler
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=20150203212701.GG1231@boo.workgroup \
--to=telegraph@gmx.net \
--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).