From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: time range, timestamps // was: docstring typoes in org-read-date-force-compatible-dates Date: Sat, 05 Jan 2019 12:43:47 -0500 Message-ID: <87o98vuhik.fsf@kyleam.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggsout.gnu.org ([209.51.188.92]:52519 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gfpzG-0002IC-Cq for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 12:43:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gfpzD-000185-74 for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 12:43:54 -0500 Received: from pb-smtp2.pobox.com ([64.147.108.71]:63587) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gfpzD-00017l-1e for emacs-orgmode@gnu.org; Sat, 05 Jan 2019 12:43:51 -0500 In-Reply-To: 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: Van L Cc: Org Mode Mailing List Van L writes: [...] > I am muddling my way through > > [info:org#Creating timestamps] > [info:org#The date/time prompt] > > and see that org-evaluate-time-range does nothing for > > <2019-01-04 Fri 11:00-12:15> It looks like org-evaluate-time-range uses org-at-date-range-p, which matches only the timestamp--timestamp range style. I'd guess that the easiest way to make org-evaluate-time-range support the single timestamp range variant would be to update it to use the org-element api (e.g., org-element-context reports the above timestamp as :type active-range). -- kyle