From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [Ann] Tool to hack time
Date: Wed, 08 Feb 2017 15:47:47 +0100 [thread overview]
Message-ID: <84zihwd9ik.fsf@tm6592> (raw)
In-Reply-To: m237fox45t.fsf@brautaset.org
Hi Stig,
Thanks for your feedback!
>> https://gitlab.com/marcowahl/hack-time is a little tool to forge the
>>[...]
>> Comments welcome, as always.
>
> I gave it a quick spin. The first thing that struck me was sadness at
> not finding an elpa package :-(
You are right, I think. I'll propose the hack-time code soon as elpa
package. Possibly in the form of a minor mode. You are invited to
contribute to the realization as package.
> Anyway, I obtained it from its repo and I positioned calendar on 7th of
> February, and invoked it on an entry I forgot to mark as done yesterday.
> This is the result:
>
> ,----
> | ** TODO Practice guitar
> | SCHEDULED: <2017-02-08 Wed ++1d/3d>
> | :PROPERTIES:
> | :STYLE: habit
> | :LAST_REPEAT: [2017-02-08 Tue 12:01]
> | :END:
> | :LOGBOOK:
> | - State "DONE" from "TODO" [2017-02-07 Tue 11:55] \\
> `----
>
> Note that:
>
> - new scheduled time is correct
> - logbook entry is correct
> - LAST_REPEAT property is *incorrect*; I expect this too to be
> [2017-02-07 Tue 11:55]
Yes. I also noticed the issue with LAST_REPEAT. I should have told in
the announcement that 'hack-time' depends on the Org 'master' branch
since about two weeks to handle LAST_REPEAT reliably.
Unfortunately 'hack-time' in its current form is not strong enough to
hack ANY time in Emacs. Up to now 'hack-time' only applies to elisp
code when it calls 'current-time'.
Best regards,
Marco
prev parent reply other threads:[~2017-02-08 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 16:07 [Ann] Tool to hack time Marco Wahl
2017-02-03 20:18 ` Christian Moe
2017-02-04 8:48 ` Marco Wahl
2017-02-08 19:13 ` Samuel Wales
2017-02-09 19:17 ` Marco Wahl
2017-02-08 12:23 ` Stig Brautaset
2017-02-08 14:47 ` Marco Wahl [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=84zihwd9ik.fsf@tm6592 \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).