* Bug: Capturing to datetree with inactive timestamp messes up level of heading
@ 2015-08-19 22:06 Gregor Zattler
2015-08-21 22:38 ` Nicolas Goaziou
0 siblings, 1 reply; 3+ messages in thread
From: Gregor Zattler @ 2015-08-19 22:06 UTC (permalink / raw)
To: emacs-orgmode
Dear org-mode developers,
customizing org to add timestamps in datetrees via …
(org-datetree-add-timestamp (quote inactive) nil nil "Add an
inactive time stamp when create a datetree entry.")… and
activating a minimal capture template which captures to a
datetree results in:
a)
* 2015
** 2015-08 August
*** 2015-08-19 Mittwoch
[2015-08-19 Mi]
** actual entry heading of captured item
The heading of the newly captured item is at level 2 instead at
level 4. I consider this to be a bug. A second capture item to
the same day is correctly created at level 4 (and bevor the first
captured item which does not belong to the same (or any) day in
the datetree).
2)
The timestamp is added to the heading of the day under which the
captured item is stored iff the day entry is created for this
capture.
I think the timestamp should go with the actual captured entry.
This allows for a timestamp for each captured entry under the
same date heading. They may be made at different days.
3)
The timestamp adds only a date but I think it’s much more
interesting to capture with date+time. Think of several journal
entries all done at the same day but at different times of a day.
All three observations werde made with an otherwise uncustimazed
org-mode (emacs -Q). I created the journal capture template from
the org-capture prompt („C“).
Org-mode version 8.3.1 (release_8.3.1-120-gc5cbc6 @ /home/grfz/src/org-mode/lisp/)
GNU Emacs 25.0.50.6 (i686-pc-linux-gnu, GTK+ Version 3.14.5) of 2015-08-19 on boo
Thanks for your attention, Gregor
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading
2015-08-19 22:06 Bug: Capturing to datetree with inactive timestamp messes up level of heading Gregor Zattler
@ 2015-08-21 22:38 ` Nicolas Goaziou
2015-08-22 7:15 ` 3 thanks (was: Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading) Gregor Zattler
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2015-08-21 22:38 UTC (permalink / raw)
To: emacs-orgmode
Hello,
Gregor Zattler <telegraph@gmx.net> writes:
> customizing org to add timestamps in datetrees via …
> (org-datetree-add-timestamp (quote inactive) nil nil "Add an
> inactive time stamp when create a datetree entry.")… and
> activating a minimal capture template which captures to a
> datetree results in:
>
> a)
>
> * 2015
> ** 2015-08 August
> *** 2015-08-19 Mittwoch
> [2015-08-19 Mi]
> ** actual entry heading of captured item
>
> The heading of the newly captured item is at level 2 instead at
> level 4. I consider this to be a bug. A second capture item to
> the same day is correctly created at level 4 (and bevor the first
> captured item which does not belong to the same (or any) day in
> the datetree).
Fixed. Thank you.
> 2)
>
> The timestamp is added to the heading of the day under which the
> captured item is stored iff the day entry is created for this
> capture.
>
> I think the timestamp should go with the actual captured entry.
> This allows for a timestamp for each captured entry under the
> same date heading. They may be made at different days.
This is a different feature. Since it belongs to the captured entry, the
timestamp should be defined in your capture template (e.g. "%t"
placeholder) instead.
> 3)
>
> The timestamp adds only a date but I think it’s much more
> interesting to capture with date+time.
This is not the purpose of `org-datetree-add-timestamp' variable.
Its main uses are to link datetrees with agenda and to build time-based
sparse trees from a datetree.
> Think of several journal entries all done at the same day but at
> different times of a day.
See above. You can use "%T".
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 3+ messages in thread
* 3 thanks (was: Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading)
2015-08-21 22:38 ` Nicolas Goaziou
@ 2015-08-22 7:15 ` Gregor Zattler
0 siblings, 0 replies; 3+ messages in thread
From: Gregor Zattler @ 2015-08-22 7:15 UTC (permalink / raw)
To: emacs-orgmode
Hi Nicolas,
* Nicolas Goaziou <mail@nicolasgoaziou.fr> [22. Aug. 2015]:
> Gregor Zattler <telegraph@gmx.net> writes:
>> customizing org to add timestamps in datetrees via …
>> (org-datetree-add-timestamp (quote inactive) nil nil "Add an
>> inactive time stamp when create a datetree entry.")… and
>> activating a minimal capture template which captures to a
>> datetree results in:
>>
>> a)
>>
>> * 2015
>> ** 2015-08 August
>> *** 2015-08-19 Mittwoch
>> [2015-08-19 Mi]
>> ** actual entry heading of captured item
>>
>> The heading of the newly captured item is at level 2 instead at
>> level 4. I consider this to be a bug. A second capture item to
>> the same day is correctly created at level 4 (and bevor the first
>> captured item which does not belong to the same (or any) day in
>> the datetree).
>
> Fixed. Thank you.
Thanks.
>> 2)
> This is a different feature. Since it belongs to the captured entry, the
> timestamp should be defined in your capture template (e.g. "%t"
> placeholder) instead.
Thanks.
>> 3)
> See above. You can use "%T".
Thanks again.
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-08-22 7:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-19 22:06 Bug: Capturing to datetree with inactive timestamp messes up level of heading Gregor Zattler
2015-08-21 22:38 ` Nicolas Goaziou
2015-08-22 7:15 ` 3 thanks (was: Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading) Gregor Zattler
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).