emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Dan Drake <dan.drake@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: specify time of day for org-resolve-clocks, not number of minutes
Date: Thu, 13 Feb 2020 15:53:53 +0100	[thread overview]
Message-ID: <87blq2bkse.fsf@gnu.org> (raw)
In-Reply-To: <CAKqbAeHuJJAgDKb__2DaKfRdiYDg9t3CW2D8iHhxL+9tMXNgoA@mail.gmail.com> (Dan Drake's message of "Thu, 13 Feb 2020 08:02:23 -0600")

Hi Dan,

Dan Drake <dan.drake@gmail.com> writes:

> 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?

You can use `read-string' and try to match either a wholenumberp (as
"[0-9]\+") or a time spec (as "[0-9]\+:[0-9]\\{2\\}").

I don't think we need to trigger the calendar: relying on (concat
(format-time-string "%F " last-valid) time) is good enough.

No need to support am/pm notation either, as long as we advertize the
need to enter HH:MM time.

We shall support this for both k/K ("keep") and g/K ("got back"),
don't you think so?

> I'll see if I can get this working.

Thanks a lot!  Since this is a new feature, I'd like to polish it
before Org 9.4 (which I initially planned for tomorrow, but I will


      reply	other threads:[~2020-02-13 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 15:05 specify time of day for org-resolve-clocks, not number of minutes Dan Drake
2020-01-07  8:17 ` Nicolas Goaziou
2020-02-13  0:31 ` Bastien
2020-02-13  1:40   ` Kyle Meyer
2020-02-13  7:16     ` Bastien
2020-02-13 14:02       ` Dan Drake
2020-02-13 14:53         ` Bastien [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blq2bkse.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=dan.drake@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).