From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Drake Subject: Re: specify time of day for org-resolve-clocks, not number of minutes Date: Thu, 13 Feb 2020 08:02:23 -0600 Message-ID: References: <87wo8r5nvi.fsf@gnu.org> <877e0ri7sb.fsf@kyleam.com> <87imkbez3x.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000075241a059e758aff" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52938) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j2F4l-00057F-No for emacs-orgmode@gnu.org; Thu, 13 Feb 2020 09:02:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j2F4k-0008Mh-DZ for emacs-orgmode@gnu.org; Thu, 13 Feb 2020 09:02:43 -0500 In-Reply-To: <87imkbez3x.fsf@bzg.fr> 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: Bastien Cc: emacs-orgmode@gnu.org --00000000000075241a059e758aff Content-Type: text/plain; charset="UTF-8" I like the idea of using g/G and intelligently interpreting the user's response -- it's good UI / UX design. (Imagine asking a friend when they "got back" -- both "20 minutes ago" and "8:35" are unambiguous answers to the question.) Now we need to decide how to distinguish the two. Would it work to just examine the user input for a colon and branch based on that? I'll see if I can get this working. On Thu, Feb 13, 2020 at 1:16 AM Bastien wrote: > 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 > -- Ceci n'est pas une .signature. --00000000000075241a059e758aff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I like the idea of using g/G and intelligently interp= reting the user's response -- it's good UI / UX design. (Imagine as= king a friend when they "got back" -- both "20 minutes ago&q= uot; and "8:35" are unambiguous answers to the question.)

Now we need to decide how to distinguish the two. Would i= t work to just examine the user input for a colon and branch based on that?= I'll see if I can get this working.

On Thu, Feb 13, 2020 at 1= :16 AM Bastien <bzg@gnu.org> wrote= :
Hi Kyle and Da= n,

Kyle Meyer <kyle@ky= leam.com> writes:

> Thanks, though sadly Dan had already taken the time to follow up with = a
> patch:
>
>=C2=A0 =C2=A0https://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 =3D 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.=C2=A0 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").=C2=A0 I gu= ess 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.=C2=A0 (Also, using org-read-date here<= br> seems a bit too much here, but maybe that's okay.)

Dan, what do you think?=C2=A0 Would you like to try implementing this or can I give it a try?

Thanks,

--
=C2=A0Bastien


--
Ceci n'est pas une .signature.
--00000000000075241a059e758aff--