emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: ConcreteVitamin <concretevitamin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to generate clock report for hours worked each day?
Date: Mon, 25 Sep 2017 03:58:13 +0000	[thread overview]
Message-ID: <CAG2+eog1xPb43ZWAUeWQwDXkt3YmXD46Jwk-k0kiZOk8zryDwg@mail.gmail.com> (raw)
In-Reply-To: <87377ckvvd.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

Thanks!  This workflow works.

I can't help but wonder, does my use case show that in org-mode philosophy,
tasks are best filed under a plain entry, not within a datetree?

On Sun, Sep 24, 2017 at 7:35 AM Matt Lundin <mdl@imapmail.org> wrote:

> ConcreteVitamin <concretevitamin@gmail.com> writes:
>
> > Thanks, it does show the hours clocked on the current day. Is there
> > something on top of this mode that allows me to specify the specific
> > day? (Better, I just want to quickly show the <lastweek> to see the
> > trend of my productivity :)).
>
> Yes, you can just move back and forward in the agenda with "b" and "f."
> Or you can pick a day on the calendar with "j". And you can view your
> aggregated time for the week with "vw".
>
> Best,
> Matt
>
>

[-- Attachment #2: Type: text/html, Size: 1200 bytes --]

  reply	other threads:[~2017-09-25  3:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-23 20:51 How to generate clock report for hours worked each day? ConcreteVitamin
2017-09-24  2:04 ` Matt Lundin
2017-09-24  5:28   ` ConcreteVitamin
2017-09-24 14:35     ` Matt Lundin
2017-09-25  3:58       ` ConcreteVitamin [this message]
2017-09-25  7:39         ` Eric S Fraga
2017-09-26 18:27           ` ConcreteVitamin
2017-09-27  5:57             ` Eric S Fraga
2017-09-28 23:43               ` ConcreteVitamin
2017-09-29 12:58                 ` Eric S Fraga
2017-10-02  9:17             ` Yasushi SHOJI

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=CAG2+eog1xPb43ZWAUeWQwDXkt3YmXD46Jwk-k0kiZOk8zryDwg@mail.gmail.com \
    --to=concretevitamin@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).