From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: Capturing to datetree with inactive timestamp messes up level of heading Date: Sat, 22 Aug 2015 00:38:57 +0200 Message-ID: <871tewjmgu.fsf@nicolasgoaziou.fr> References: <20150819220651.GE2464@boo.workgroup> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46938) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSuw4-00028c-QT for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 18:37:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZSuw3-00021q-Te for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 18:37:20 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:33900) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZSuw3-00020e-N0 for emacs-orgmode@gnu.org; Fri, 21 Aug 2015 18:37:19 -0400 Received: from selenimh (unknown [IPv6:2a01:6600:8080:9601::2de]) (Authenticated sender: mail@nicolasgoaziou.fr) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 4E8BB172081 for ; Sat, 22 Aug 2015 00:37:18 +0200 (CEST) In-Reply-To: <20150819220651.GE2464@boo.workgroup> (Gregor Zattler's message of "Thu, 20 Aug 2015 00:06:51 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Hello, Gregor Zattler writes: > customizing org to add timestamps in datetrees via =E2=80=A6 > (org-datetree-add-timestamp (quote inactive) nil nil "Add an > inactive time stamp when create a datetree entry.")=E2=80=A6 and > activating a minimal capture template which captures to a > datetree results in: > > a) > > * 2015=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20 > ** 2015-08 August=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20 > *** 2015-08-19 Mittwoch=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > [2015-08-19 Mi]=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20 > ** 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=E2=80=99s much more > interesting to capture with date+time. This is not the purpose of `org-datetree-add-timestamp' variable.=20 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, --=20 Nicolas Goaziou