emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Stig Brautaset <stig@brautaset.org>, emacs-orgmode@gnu.org
Subject: Re: Feature request: org-agenda-clockreport-mode to omit files with no clocked time
Date: Sun, 26 Apr 2020 18:56:10 +0000	[thread overview]
Message-ID: <87r1wam5yt.fsf@kyleam.com> (raw)
In-Reply-To: <m2v9lmgkoy.fsf@brautaset.org>

Stig Brautaset <stig@brautaset.org> writes:

> I often end up with empty files in my org-agenda-clockreport-mode,
> something like this. (For the avoidance of doubt: this is an ECM ;-) )
>
> | File         | Headline         | Time   |   |
> |--------------+------------------+--------+---|
> |              | ALL *Total time* | *0:42* |   |
> |--------------+------------------+--------+---|
> | maybe.org    | *File time*      | *0:00* |   |
> |--------------+------------------+--------+---|
> | projects.org | *File time*      | *0:00* |   |
> |--------------+------------------+--------+---|
> | tasks.org    | *File time*      | *0:42* |   |
> |              | Foo              | 0:08   |   |
> |              | Bar              | 0:24   |   |
> |              | Quux             | 0:10   |   |
>
> I would have liked it to hide all the uninteresting files (i.e. files
> with no clocked time) and instead shown me:

[...]

> It seems like a small-ish change I may brave to implement--unless
> someone beats me to it, which I'm fine with! I would appreciate some
> pointers:
>
> 1. Would I need to introduce an option, in case anyone relies on the
>    empty sections? (I *think* not, as I gather the prevailing wind is to
>    reduce the number of options.)

I haven't tried, but can you already do this via
org-agenda-clockreport-parameter-plist, in particular by adding
`:fileskip0 t'?


  reply	other threads:[~2020-04-26 18:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 18:34 Feature request: org-agenda-clockreport-mode to omit files with no clocked time Stig Brautaset
2020-04-26 18:56 ` Kyle Meyer [this message]
2020-04-26 20:52   ` Stig Brautaset

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=87r1wam5yt.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=stig@brautaset.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).