From: Bastien <bastienguerry@googlemail.com>
To: meingbg <meingbg@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clean Org Clock with step
Date: Sat, 25 Jul 2009 20:37:43 +0800 [thread overview]
Message-ID: <87my6t0wh4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <e83e84da0907240726s55e3c690j1d6a6303b43e0015@mail.gmail.com> (meingbg@gmail.com's message of "Fri, 24 Jul 2009 16:26:45 +0200")
meingbg <meingbg@gmail.com> writes:
> Just looking at the output, maybe this could be implemented as a regexp replace
> on the entire block performed after putting together the tables? Just thinking
> it might save you some headache, if you don't think it's too ugly of a hack.
Well, it *is* to ugly of a hack, but here it is:
(defun my-org-remove-empty-daily-clock-report ()
"Remove empty daily clock reports"
(interactive)
(while (re-search-forward "^Daily report:.*$" nil t)
(let ((beg0 (match-beginning 0))
(beg1 (1+ (match-end 0)))
(end (save-excursion
(re-search-forward "^$\\|^#\\+END.*" nil t)
(match-beginning 0))))
(when (re-search-forward "Total time.*0:00" end t)
(delete-region beg0 end)
(delete-char -1)))))
It will definitely not make its way thru Org, we need a mechanism that
prevents the display of empty report instead.
> And while I'm at it - my employer requires me to report not only what I'm doing
> and how long it takes, but also when I'm doing it. I assume most people
> wouldn't benefit from a feature like this, and that there are many other things
> on the wish list with higher priority, so I'm just asking if someone could
> point out an API guide or something like that, it would be wonderful.
That makes sense...
--
Bastien
next prev parent reply other threads:[~2009-07-25 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 22:10 Clean Org Clock with step meingbg
2009-07-23 16:30 ` Bastien
2009-07-24 14:26 ` meingbg
2009-07-25 12:37 ` Bastien [this message]
2009-07-25 22:12 ` Bastien
2009-08-03 13:38 ` Carsten Dominik
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=87my6t0wh4.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=meingbg@gmail.com \
/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).