From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: [PATCH 0/2] org-clock: Simplify `untilnow' range logic Date: Fri, 28 Dec 2018 16:36:25 -0500 Message-ID: <20181228213627.387-1-kyle@kyleam.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43150) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gd072-0004XC-OV for emacs-orgmode@gnu.org; Fri, 28 Dec 2018 16:56:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gczoK-0007FT-TB for emacs-orgmode@gnu.org; Fri, 28 Dec 2018 16:37:53 -0500 Received: from pb-smtp21.pobox.com ([173.228.157.53]:62717) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gczoK-0007DR-Hp for emacs-orgmode@gnu.org; Fri, 28 Dec 2018 16:36:52 -0500 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 Cc: jhenahan@me.com Hello, For the clock table `untilnow' behavior, we set the starting point to a really old date, but that falls outside the YYYY-MM-DD that org-parse-time-string was designed to handle. I've reworked org-clock-special-range to use nil to represent the starting bound for `untilnow' and updated org-parse-time-string to mention the YYYY-MM-DD assumption. Please let me know if you have any objections. Otherwise, I'll apply the following commits to maint in a few days. org-clock: Simplify `untilnow' range logic org-parse-time-string: Describe time stamp matching behavior lisp/org-clock.el | 9 ++++----- lisp/org-macs.el | 4 +++- 2 files changed, 7 insertions(+), 6 deletions(-) --=20 2.20.0