From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Subhan Michael Tindall <SubhanT@familycareinc.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Robert Klein <roklein@roklein.de>
Subject: Re: Clocking each days entries into one table?
Date: Fri, 12 Jun 2015 18:46:57 +0100 [thread overview]
Message-ID: <87mw04izu6.fsf@skimble.plus.com> (raw)
In-Reply-To: <ecaf6223718d40a59a059a959ae6b070@fcmailsvr2.familycareinc.org> (Subhan Michael Tindall's message of "Tue, 9 Jun 2015 15:58:43 +0000")
[-- Attachment #1: Type: text/plain, Size: 4175 bytes --]
Subhan Michael Tindall <SubhanT@familycareinc.org> writes:
> Have you investigated clocktables?
> Type in the following & hit C-c C-c with point on the 'BEGIN' line somewhere to update.
> This one produces a month summary by agenda file
> #+BEGIN: clocktable :block thismonth :narrow 30 :tcolumns 6 :maxlevel 1 :step day :fileskip0 :timestamp :scope agenda :link t
> #+END:
>
> This followed by a little re search & replace macro to combine the blocks should just about the job for you
>
> Assumes each project is a file in org-agenda-files, but can easily be
> modified to do a single file, or tag or set of tags at a time if that is
> how you define your projects
> Formatting options:
> https://www.gnu.org/software/emacs/manual/html_node/org/The-clock-table.html
>
> My apologies if this has already been suggested
Thanks for this, I am using clocktables from the page you referred
to in your link. With your line as a starter, the best that I've
come up with is this -
╭────
│#+BEGIN: clocktable :block thismonth :narrow 30 :tcolumns 6 :maxlevel 2 :step week :stepskip0 :fileskip0 :timestamp :scope file :link t
╰────
This breaks it down to a weekly block, which can be merged by
deleting lines and then using "C-c C-c" to equalise the cell limits.
This could be done just as easily for a day setup, where you delete
cell titles and equalise cell limits again. However if you "C-c C-c"
it destroys all your deletions and equalises again. I did try with
╭────
│:step month
╰────
but that just threw up a debug buffer! That, to me, was a logical
step but it didn't work!
ATM, my clocktables and clocks are all in one file, maybe later I'll
split them up, but I've only started using clocktables this month.
Thanks
Sharon.
>
>> -----Original Message-----
>> From: emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org
>> [mailto:emacs-orgmode-bounces+subhant=familycareinc.org@gnu.org] On
>> Behalf Of Sharon Kimble
>> Sent: Tuesday, June 09, 2015 1:43 AM
>> To: Robert Klein
>> Cc: emacs-orgmode@gnu.org
>> Subject: Re: [O] Clocking each days entries into one table?
>>
>> Robert Klein <roklein@roklein.de> writes:
>>
>> > Hi,
>> >
>> > did you read Bernt Hansen's doumentation
>> > (http://doc.norang.ca/org-mode.html)? Sections 9 and 10 in particular
>> > could be of help to you.
>> >
>> > Best regards
>> > Robert
>>
>> Thanks Robert, I am aware of Bernt Hansen's setup, and have included some
>> of it in my setup. But I'm still searching for that elusive month-end table
>> display!
>>
>> Sharon.
>> >
>> >
>> > On 06/08/2015 09:15 PM, Sharon Kimble wrote:
>> >> I've recently started clocking the work that I'm doing, and am now
>> >> considering a month-end report. Is it possible to have one table per
>> >> project with each line being that days total time entries? I've seen
>> >> how to get it showing each days entries but not in separate lines
>> >> within the table. The method described online splits each days
>> >> entries into separate split tables.
>> >>
>> >> But I'm looking for one table with a maximum of 31 lines which
>> >> correspond to each days entries. Is it possible please?
>> >>
>> >> Thanks
>> >> Sharon.
>> >>
>>
>> --
>> A taste of linux = http://www.sharons.org.uk TGmeds =
>> http://www.tgmeds.org.uk Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.1
>
> This message is intended for the sole use of the individual and entity to
> which it is addressed and may contain information that is privileged,
> confidential and exempt from disclosure under applicable law. If you are
> not the intended addressee, nor authorized to receive for the intended
> addressee, you are hereby notified that you may not use, copy, disclose or
> distribute to anyone the message or any information contained in the
> message. If you have received this message in error, please immediately
> advise the sender by reply email and delete the message. Thank you.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2015-06-12 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 19:15 Clocking each days entries into one table? Sharon Kimble
2015-06-09 5:31 ` Robert Klein
2015-06-09 8:42 ` Sharon Kimble
2015-06-09 15:58 ` Subhan Michael Tindall
2015-06-12 17:46 ` Sharon Kimble [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
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=87mw04izu6.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=SubhanT@familycareinc.org \
--cc=emacs-orgmode@gnu.org \
--cc=roklein@roklein.de \
/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).