From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabrice Popineau Subject: Datetrees and tags Date: Mon, 1 Jan 2018 15:27:08 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c043d2829ebb70561b7c8db" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40136) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eW13q-0000Pn-LA for emacs-orgmode@gnu.org; Mon, 01 Jan 2018 09:27:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eW13p-0000As-Qh for emacs-orgmode@gnu.org; Mon, 01 Jan 2018 09:27:30 -0500 Received: from mail-qk0-x235.google.com ([2607:f8b0:400d:c09::235]:41270) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eW13p-0000Am-Kq for emacs-orgmode@gnu.org; Mon, 01 Jan 2018 09:27:29 -0500 Received: by mail-qk0-x235.google.com with SMTP id a8so21678342qkb.8 for ; Mon, 01 Jan 2018 06:27:29 -0800 (PST) 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" To: emacs-orgmode@gnu.org --94eb2c043d2829ebb70561b7c8db Content-Type: text/plain; charset="UTF-8" Hi, It seems that currently, datetrees do not support tags. IE if I add a tag to some datetree and I try to add another item to the same date, then another date is insereted: *** 2017-12-29 vendredi :perso: [2017-12-29 ven.] - Bla-bla-bla-bla *** 2017-12-29 vendredi [2017-12-29 ven.] - Actually, looking at org-datetree.el, the several regex here do not take possible tags into account, so this is expected. So my question: would it make sense to enhance datetrees entries with optional tags? Or would that introduce some kind of inconsistency elsewhere? Happy New Year to everybody. Fabrice --94eb2c043d2829ebb70561b7c8db Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hi,

It seems = that currently, datetrees do not support tags.
IE if I add a tag = to some datetree and I try to add another item to the same date,
= then another date is insereted:

*** 2017-12-2= 9 vendredi=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0:perso:
[2017-12-29 ven.]

<= /div>
- Bla-bla-bla-bla

*** 2017-12-29 vendred= i
[2017-12-29 ven.]

-=C2=A0
<= div>
Actually, looking at org-datetree.el, the several regex = here do not take possible tags into account, so this is expected.

So my question: would it make sense to enhance datetrees en= tries with optional tags?
Or would that introduce some kind of in= consistency elsewhere?

Happy New Year to everybody= .

Fabrice
--94eb2c043d2829ebb70561b7c8db--