From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Gaspard Subject: =?UTF-8?B?4oCcRnV6ennigJ0gdGltZXMgKOKAnGV2ZW5pbmfigJ0sIOKAnG1v?= =?UTF-8?B?cm5pbmfigJ0sIOKAnG5pZ2h04oCd4oCmKQ==?= Date: Sun, 09 Dec 2018 02:47:35 +0900 Message-ID: <875zw3j4g8.fsf@llwynog.ekleog.org> 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]:35742) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gVghe-0007Gb-3x for emacs-orgmode@gnu.org; Sat, 08 Dec 2018 12:47:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gVgha-0000fo-Rt for emacs-orgmode@gnu.org; Sat, 08 Dec 2018 12:47:46 -0500 Received: from grym.ekleog.org ([94.23.42.210]:45912 helo=smtp.gaspard.ninja) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gVgha-0000es-FA for emacs-orgmode@gnu.org; Sat, 08 Dec 2018 12:47:42 -0500 Received: by smtp.gaspard.ninja (OpenSMTPD) with ESMTP id 7f923252 for ; Sat, 8 Dec 2018 17:47:45 +0000 (UTC) Received: by smtp.gaspard.ninja (OpenSMTPD) with ESMTP id dc7b591f for ; Sat, 8 Dec 2018 17:47:45 +0000 (UTC) Received: from localhost (llwynog [local]) by llwynog (OpenSMTPD) with ESMTPA id e79cbe20 for ; Sat, 8 Dec 2018 17:47:35 +0000 (UTC) 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 Hello, In the process of migrating all my self-organization to org-mode, I noticed there is something that cannot currently be encoded in timestamps: fuzzy times, where an appointment is made for =E2=80=9CDec 4, T= ue, evening=E2=80=9D but with the hours not yet fixed. Currently my way of handling this has been to mark the tasks with time spans approx. correct and add a comment to fix them. However, I think it may be a good idea to allow eg. this kind of timestamps: <2018-02-04 Tue evening> That would be handled as though it was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable), so that it would be both semantically correct (the time is still fuzzy) and correctly displayed (eg. on an agenda) To be perfectly honest, my ulterior motive here is to auto-generate tasks =E2=80=9CDecide of an exact time for [task]=E2=80=9D a few days befor= e the timestamp. However, I haven't investigated yet whether that'd actually be doable and I'm still pretty new to the lisp/emacs/org-mode ecosystems, so this may be completely impossible. What do you think about this idea? Is there a better way to do what I'm trying to do with current tools? Cheers, Leo