From: Gregor Zattler <grfz@gmx.de>
To: emacs-orgmode@gnu.org
Subject: 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: Sun, 01 Feb 2015 22:23:47 +0100 [thread overview]
Message-ID: <87mw4xjpgc.fsf@boo.workgroup> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------
Dear org-mode developers,
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 is with:
Emacs : GNU Emacs 25.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.14.5)
of 2015-02-01 on boo
Package: Org-mode version 8.3beta (release_8.3beta-785-gb5d9f4 @ /home/grfz/src/org-mode/lisp/)
I did a git bisect and got:
a1116aa54ee4befd8fa52e3f92207db200ebfd59 is the first bad commit
commit a1116aa54ee4befd8fa52e3f92207db200ebfd59
Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Date: Fri Jan 30 10:23:47 2015 +0100
Fix ‘org-agenda-insert-diary-make-new-entry’
* lisp/org-agenda.el (org-agenda-insert-diary-make-new-entry): Ensure
point is at a real body line and not in front of meta data, so
regular contents can be inserted safely after a call to this
function.
Reported-by: Samuel Loury <konubinix@gmail.com>
<http://permalink.gmane.org/gmane.emacs.orgmode/94482>
:040000 040000 c02a04761fd8b4f2b518852afca3b44f4f0642ae 60b6dc4cf3232b8059b8e8c778949d8b466a2e75 M lisp
Thanks for your attention, Gregor
next reply other threads:[~2015-02-01 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 21:23 Gregor Zattler [this message]
2015-02-02 17:22 ` 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/)] Nicolas Goaziou
2015-02-03 21:27 ` 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/)]) Gregor Zattler
2015-02-04 16:37 ` fix is with another glitch when adding two dates " 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=87mw4xjpgc.fsf@boo.workgroup \
--to=grfz@gmx.de \
--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).