From: Nicolas Goaziou <firstname.lastname@example.org>
To: Dan Drake <email@example.com>
Subject: Re: specify time of day for org-resolve-clocks, not number of minutes
Date: Tue, 07 Jan 2020 09:17:44 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <CAKqbAeHeDrM4npyYOgQb1V=T+35u3Dh-cRX_3vERNO2p_yUkww@mail.gmail.com> (Dan Drake's message of "Fri, 3 Jan 2020 09:05:26 -0600")
Dan Drake <email@example.com> writes:
> Instead, I want to specify a *time*, since usually that's what I remember
> ("my coworker stopped to ask a question at 10:45"). I'd like a way to get
> the K functionality, but instead of doing the math to figure out a number
> of minutes, I want to just type in a time of day.
> Is there a way to do this already?
I don't think so.
> Or would this require a new clock resolution command -- perhaps "t",
> for "time": it would effectively just be a wrapper around "k" that
> parses the provided time, looks at the current clocked-in task,
> computes the appropriate number of minutes, and then just does
> whatever "k" (or "K") does.
This is a good idea. It might be useful to provide a date somehow, e.g.,
if you want to rewind to yesterday at 11:00pm. I'm not sure what a good
interface would be, though. `org-read-date' is pretty much future
next prev parent reply other threads:[~2020-01-07 8:17 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 [this message]
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
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 \
* 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).