On 2023-06-25, at 18:03, Adam Spiers wrote:
> Three years later, I finally tried this:
>
> On Wed, 8 Jul 2020 at 05:53, Kyle Meyer wrote:
>> Adam Spiers writes:
>> > I'm looking for a way to retroactively mark a task as having been done
>> > at a previous time/date. I know that I can just
On Sun, 25 Jun 2023 at 17:03, Adam Spiers wrote:
> Three years later, I finally tried this:
Apologies for the noise; apparently three years is enough time for me
to completely forget that I'd already found a better solution to this:
Three years later, I finally tried this:
On Wed, 8 Jul 2020 at 05:53, Kyle Meyer wrote:
> Adam Spiers writes:
> > I'm looking for a way to retroactively mark a task as having been done
> > at a previous time/date. I know that I can just change the keyword to
> > DONE and then edit the
Adam Spiers writes:
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):
On Wed, 8 Jul 2020 at 23:09, No Wayman 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:
>
> https://github.com/progfolio/epoch/
>
> The package advises
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:
https://github.com/progfolio/epoch/
The package advises current-time to return `epoch-current-time' if
is set
On 2020-07-07, at 13:26, Adam Spiers wrote:
> Hi all,
>
> I'm looking for a way to retroactively mark a task as having been done
> at a previous time/date. I know that I can just change the keyword to
org-todo-yesterday?
Hth,
--
Marcin Borkowski
http://mbork.pl
Adam Spiers writes:
> I'm looking for a way to retroactively mark a task as having been done
> at a previous time/date. I know that I can just change the keyword to
> DONE and then edit the timestamp, but this is tedious when it's a
> repeating event, e.g.:
[...]
I'm not aware of any built-in
