From: Adam Spiers <email@example.com>
To: No Wayman <firstname.lastname@example.org>
Cc: org-mode mailing list <email@example.com>
Subject: Re: time-warping - retroactively marking DONE?
Date: Sun, 30 Aug 2020 01:22:33 +0100 [thread overview]
Message-ID: <CAOkDyE-2aCPucSyBbHvf0fsbuJ1DkRqbPjzEE=xCVppp7J=QTA@mail.gmail.com> (raw)
On Wed, 8 Jul 2020 at 23:09, No Wayman <firstname.lastname@example.org> wrote:
> I emailed Adam directly with an experimental package I wrote to
> solve the problem of changing the todo-state of an entry at an
> arbitrary time.
> He suggested I posted here as well:
> The package advises current-time to return `epoch-current-time' if
> is set (falling back to the usual current-time if not).
> A macro, `epoch-with-time' is provided which allows a body to be
> executed with current-time set to an arbitrary time.
> Two commands (which I may separate into their own package),
> `epoch-todo' and `epoch-agenda-todo' call their respective
> org-mode commands.
> `org-read-date' is called with the tasks's SCHEDULED or DEADLINE
> time pre-populated so one can easily edit relative to that time.
> Still very much a work in progress, but the two commands are
> useful for me so far.
> Any ideas, suggestions, criticisms are appreciated.
Many thanks again for this. It's working great for me!
In case anyone's interested, here's my use-package config (which uses
the awesome straight.el package manager to install it):
I agree with your observation that it might be nicer to separate out
the org-specific stuff into a separate package, because the epoch
stuff seems useful in its own right outside org-mode.
next prev parent reply other threads:[~2020-08-30 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2020-07-08 21:38 ` time-warping - retroactively marking DONE? No Wayman
2020-08-30 0:22 ` Adam Spiers [this message]
2020-08-30 1:32 ` No Wayman
2020-07-07 11:26 Adam Spiers
2020-07-08 4:53 ` Kyle Meyer
2020-07-08 5:52 ` Marcin Borkowski
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).