* Struggling with large: :LOGBOOK: .. :END: blocks
@ 2012-04-05 13:26 Rainer Stengele
2012-04-05 14:44 ` William Gardella
0 siblings, 1 reply; 2+ messages in thread
From: Rainer Stengele @ 2012-04-05 13:26 UTC (permalink / raw)
To: emacs-orgmode
Hi all,
As a long time Org user I have a lot of tasks having large
:LOGBOOK:
..
:END:
blocks, sometimes 50 and more CLOCK entries.
Why? Well, I have tasks to read and organise E-Mail which I do at least once I day and which I have to clock.
I also do have to adjust the latest few CLOCK lines manually.
Now, opening the :LOGBOOK: block I cannot see the text following the :LOGBOOK: block
because all the CLOCK entries flood my screen.
But I would like to see it in order to get some context of the task.
Wouldn't it be a nice thing to be able to configure the number of visible block entries?
This could result in:
Opening the :LOGBOOK block with TAB shows this:
* TODO text
:LOGBOOK:
CLOCK: [2012-03-27 Di 13:00]--[2012-03-27 Di 13:30] => 0:30
CLOCK: [2012-03-06 Di 11:30]--[2012-03-06 Di 11:45] => 0:15
CLOCK: [2012-03-02 Fr 14:45]--[2012-03-02 Fr 15:15] => 0:30
..
:END:
Another TAB would show all CLOCK entries.
The next TAB would close the block again.
The variable could configure:
"show the first n entries of the BLOCK"
"show the last n entries of the BLOCK"
"show the first n and last m entries of the BLOCK"
Regards,
Rainer
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Struggling with large: :LOGBOOK: .. :END: blocks
2012-04-05 13:26 Struggling with large: :LOGBOOK: .. :END: blocks Rainer Stengele
@ 2012-04-05 14:44 ` William Gardella
0 siblings, 0 replies; 2+ messages in thread
From: William Gardella @ 2012-04-05 14:44 UTC (permalink / raw)
To: emacs-orgmode
Hi Rainer,
Rainer Stengele <rainer.stengele@online.de> writes:
>
> Wouldn't it be a nice thing to be able to configure the number of
> visible block entries?
>
> This could result in:
> Opening the :LOGBOOK block with TAB shows this:
>
>
> * TODO text
> :LOGBOOK:
> CLOCK: [2012-03-27 Di 13:00]--[2012-03-27 Di 13:30] => 0:30
> CLOCK: [2012-03-06 Di 11:30]--[2012-03-06 Di 11:45] => 0:15
> CLOCK: [2012-03-02 Fr 14:45]--[2012-03-02 Fr 15:15] => 0:30
> ..
> :END:
>
>
> Another TAB would show all CLOCK entries.
> The next TAB would close the block again.
>
> The variable could configure:
>
> "show the first n entries of the BLOCK"
> "show the last n entries of the BLOCK"
> "show the first n and last m entries of the BLOCK"
A "fuzzy" logbook view (perhaps similar to the "fuzziness" sparse trees
currently have, providing a few lines of context) would indeed be pretty
cool.
I also have some rather long strings of clock entries, but I prefer to
have them summarized for me using the `org-clock-report' function, C-c
C-x C-r.
Cheers,
Will
--
I use grml (http://grml.org/)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-05 14:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-05 13:26 Struggling with large: :LOGBOOK: .. :END: blocks Rainer Stengele
2012-04-05 14:44 ` William Gardella
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).