From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: specify time of day for org-resolve-clocks, not number of minutes Date: Thu, 13 Feb 2020 08:16:18 +0100 Message-ID: <87imkbez3x.fsf@bzg.fr> References: <87wo8r5nvi.fsf@gnu.org> <877e0ri7sb.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54443) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j28jk-00051Z-HX for emacs-orgmode@gnu.org; Thu, 13 Feb 2020 02:16:37 -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-mx.org@gnu.org Sender: "Emacs-orgmode" To: Kyle Meyer Cc: Dan Drake , emacs-orgmode@gnu.org Hi Kyle and Dan, Kyle Meyer writes: > Thanks, though sadly Dan had already taken the time to follow up with a > patch: > > https://lists.gnu.org/archive/html/emacs-orgmode/2020-01/msg00175.html Err, my bad, sorry Dan -- and thanks Kyle for the warning. (I too hastily assume 1 thread = 1 topic, I should have checked.) I reverted my changes and pushed Dan's commit to master. I took the liberty of inlining the function and making the message a bit more explicit. Dan, let me know if that's okay. Interestingly, our (different and complementary) implementations may lead to a new idea: your implementation is like the `k' option while mine is like the `g' option (when you "got back"). I guess both can make sense, and what the user expect is to be able to enter a number of minutes *or* a HH:MM time spec in both `t' and `g'. That would also have the advantage of having less options while still having the possibility to use HH:MM. (Also, using org-read-date here seems a bit too much here, but maybe that's okay.) Dan, what do you think? Would you like to try implementing this or can I give it a try? Thanks, -- Bastien