emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Russell Adams <RLAdams@adamsinfoserv.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Alternatives to clocking in/out for reporting time
Date: Sun, 10 Jul 2022 17:30:37 +0800	[thread overview]
Message-ID: <87a69huxfm.fsf@localhost> (raw)
In-Reply-To: <Ysl4M6TiR1skY5+B@tahm>

Russell Adams <RLAdams@adamsinfoserv.com> writes:

>> Can you then formulate what exactly you want to achieve?
>> Do you want to consider only agenda items? All the timestamps in the
>> matching items or maybe just some?
>
> I typically use agenda for the month with logbook view and inactive
> timestamps enabled.
>
> I'd love to iterate over the list of all timestamps from that view.

You can. What you need to know about agenda buffers is that various
useful information is stored in text properties.

Every agenda line, which corresponds to a headline contains a non-nil
'org-hd-marker text property. In log mode, there will also be non-nil
'date and 'time-of-day text properties. You can examine the full list
yourself by running M-x describe-text-properties with point at an agenda
entry.

Hope it helps.

Best,
Ihor


  reply	other threads:[~2022-07-10  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 14:59 Alternatives to clocking in/out for reporting time Russell Adams
2022-06-29 21:26 ` Tim Cross
2022-06-29 22:09   ` Russell Adams
2022-06-30  2:11 ` Samuel Wales
2022-06-30  2:12   ` Samuel Wales
2022-06-30  8:57   ` Russell Adams
2022-06-30 22:32     ` Samuel Wales
2022-07-08  7:02 ` Ihor Radchenko
2022-07-08  8:10   ` Russell Adams
2022-07-09  4:00     ` Ihor Radchenko
2022-07-09 12:44       ` Russell Adams
2022-07-10  9:30         ` Ihor Radchenko [this message]
2022-07-10 23:09           ` Samuel Wales
2022-07-10 12:26 ` Olaf Dietsche

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=87a69huxfm.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=RLAdams@adamsinfoserv.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).