From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Gaspard Subject: =?UTF-8?B?UmU6IOKAnEZ1enp54oCdIHRpbWVzICjigJxldmVuaW5n4oCdLCA=?= =?UTF-8?B?4oCcbW9ybmluZ+KAnSwg4oCcbmlnaHTigJ3igKYp?= Date: Mon, 10 Dec 2018 02:00:22 +0900 Message-ID: <87wooihbyx.fsf@llwynog.ekleog.org> References: <875zw3j4g8.fsf@llwynog.ekleog.org> <87bm5vkhk5.fsf@geus3064linuxwsm.geus.dk> 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]:58434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gW2Ra-0002c8-6u for emacs-orgmode@gnu.org; Sun, 09 Dec 2018 12:00:39 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gW2RW-00078F-4x for emacs-orgmode@gnu.org; Sun, 09 Dec 2018 12:00:38 -0500 Received: from grym.ekleog.org ([94.23.42.210]:44804 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 1gW2RV-00075n-Ne for emacs-orgmode@gnu.org; Sun, 09 Dec 2018 12:00:34 -0500 In-Reply-To: <87bm5vkhk5.fsf@geus3064linuxwsm.geus.dk> 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: Ken Mankoff Cc: emacs-orgmode@gnu.org Ken Mankoff writes: > On 2018-12-08 at 09:47 -0800, Leo Gaspard wrote: >> 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) >> [...] >> What do you think about this idea? Is there a better way to do what >> I'm trying to do with current tools? > > > I think this would be a neat feature. But as a first pass which can work = immediately, what about using one of the multiple text expansion packages t= hat are Org-agnostic to achieve this: Yasnippets or abbrev mode, for exampl= e? > > This doesn't maintain the "semantics (time still fuzzy)", but does let yo= u define and enter time ranges in a simpler way. Hmm=E2=80=A6 I guess some abbreviation or command could add the fuzzy time = and add a comment to indicate that the time is fuzzy should work as a temporary workaround indeed, thank you for the idea :)