From: Jude DaShiell <jdashiel@panix.com>
To: Bob Newell <bobnewell@bobnewell.net>, help-gnu-emacs@gnu.org
Subject: Re: creating an afk timeline
Date: Wed, 20 Dec 2023 22:03:39 -0500 [thread overview]
Message-ID: <0d79f545-20ef-395d-4e93-c740e81e14c0@panix.com> (raw)
In-Reply-To: <ysu2r8dqmejw.mxnasj1oni@hhvxv63.vpuvrv.info>
orgmode would have a problem with it since duration times do not span
dates. If afk from [2023-12-20 wed 22:58] as start time and [2023-12-21
Thu 04:00] as end time duration last time I checked would not return
05:02.
If that were fixed, orgmode could be used to log health events.
--
Jude <jdashiel at panix dot com>
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Wed, 20 Dec 2023, Bob Newell wrote:
> > Samuel Wales <samologist@gmail.com> writes:
>
> >> i'd like to know when i stopped using emacs, or linux, for a while, so
> >> i can figure out when i likely started. perhaps a timeline of
> >> idleness, preferably in emacs, could help me guess when i started
> >> doing non-computer.
> >>
> >> this could help me guess when i rested, took a supplement, brushed
> >> teeth, etc. sometimes i need to know when 2h is up after i started.
>
> This is an intriguing idea, and I think perhaps the ideas
> discussed here can be made to do what you wish with a little
> more hacking.
>
> https://www.reddit.com/r/emacs/comments/kda2lr/make_something_happen_when_i_return_from_idle/
>
> It makes use of the Emacs idle timer and of course would only
> measure idleness in Emacs (not Linux in general, if that's
> what you're seeking).
>
>
prev parent reply other threads:[~2023-12-21 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 4:17 creating an afk timeline Samuel Wales
2023-12-20 20:16 ` tpeplt
2023-12-21 2:51 ` Bob Newell
2023-12-21 3:03 ` Jude DaShiell [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d79f545-20ef-395d-4e93-c740e81e14c0@panix.com \
--to=jdashiel@panix.com \
--cc=bobnewell@bobnewell.net \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.