Hi, Please take a look at the below org file. Initially I created the TODO item and then clocked in and out. Then inserted a note. Followed by some clock ins and outs. Everything is organized from top to bottom as we enter items. Earlier I remember the clock entries were grouped and always appeared at the top but now it is cluttered. I am using the latest version from git repo. Is this the expected behavior or am I missing something by which I can group all the clock entries into a group at the top or bottom? Also I remember that I was able to hide entire clock entries. ----------------------CUT--------------------------------------- * Inbox ** TODO This is a test CLOCK: [2009-08-05 Wed 18:46] CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00 CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00 - Note taken on [2009-08-05 Wed 18:46] \\ Test CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00 ----------------------CUT---------------------------------------- Thanks and Regards Noorul
Noorul Islam K M <gnukid@gmail.com> writes:
> Please take a look at the below org file. Initially I created the TODO
> item and then clocked in and out. Then inserted a note. Followed by some
> clock ins and outs. Everything is organized from top to bottom as we
> enter items. Earlier I remember the clock entries were grouped and
> always appeared at the top but now it is cluttered. I am using the
> latest version from git repo. Is this the expected behavior or am I
> missing something by which I can group all the clock entries into a
> group at the top or bottom? Also I remember that I was able to hide
> entire clock entries.
Take a look at the variable org-clock-into-drawer. This saves your
clock entries in a :LOGBOOK: drawer which you can expand or hide.
-Bernt
At Wed, 05 Aug 2009 11:28:40 -0400,
Bernt Hansen wrote:
>
> Noorul Islam K M <gnukid@gmail.com> writes:
>
> > Please take a look at the below org file. Initially I created the TODO
> > item and then clocked in and out. Then inserted a note. Followed by some
> > clock ins and outs. Everything is organized from top to bottom as we
> > enter items. Earlier I remember the clock entries were grouped and
> > always appeared at the top but now it is cluttered. I am using the
> > latest version from git repo. Is this the expected behavior or am I
> > missing something by which I can group all the clock entries into a
> > group at the top or bottom? Also I remember that I was able to hide
> > entire clock entries.
>
> Take a look at the variable org-clock-into-drawer. This saves your
> clock entries in a :LOGBOOK: drawer which you can expand or hide.
Mine says this:
org-clock-into-drawer's value is t
Documentation:
Should clocking info be wrapped into a drawer?
When t, clocking info will always be inserted into a :CLOCK: drawer.
If necessary, the drawer will be created.
When nil, the drawer will not be created, but used when present.
When an integer and the number of clocking entries in an item
reaches or exceeds this number, a drawer will be created.
alas with my current version (6.21), it still spreads clock items
everywhere. Is it something known ? Should I update my orgmode
copy ?
Thanks
Xavier
On Aug 5, 2009, at 2:49 PM, Noorul Islam K M wrote:
>
> Hi,
>
> Please take a look at the below org file. Initially I created the TODO
> item and then clocked in and out. Then inserted a note. Followed by
> some
> clock ins and outs. Everything is organized from top to bottom as we
> enter items. Earlier I remember the clock entries were grouped and
> always appeared at the top but now it is cluttered. I am using the
> latest version from git repo. Is this the expected behavior or am I
> missing something by which I can group all the clock entries into a
> group at the top or bottom? Also I remember that I was able to hide
> entire clock entries.
>
> ----------------------CUT---------------------------------------
> * Inbox
> ** TODO This is a test
> CLOCK: [2009-08-05 Wed 18:46]
> CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00
> CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00
> - Note taken on [2009-08-05 Wed 18:46] \\
> Test
> CLOCK: [2009-08-05 Wed 18:46]--[2009-08-05 Wed 18:46] => 0:00
>
> ----------------------CUT----------------------------------------
Notes and clock entries are supposed to be kept in
chronological sequence. So yes, this is the expected behavior.
You can define a separate drawer for clock entries, if you prefer so:
(setq org-clock-into-drawer "CLOCK")
- Carsten
Xavier Maillard <xma@gnu.org> writes:
> At Wed, 05 Aug 2009 11:28:40 -0400,
> Bernt Hansen wrote:
>>
>> Noorul Islam K M <gnukid@gmail.com> writes:
>>
>> > Please take a look at the below org file. Initially I created the TODO
>> > item and then clocked in and out. Then inserted a note. Followed by some
>> > clock ins and outs. Everything is organized from top to bottom as we
>> > enter items. Earlier I remember the clock entries were grouped and
>> > always appeared at the top but now it is cluttered. I am using the
>> > latest version from git repo. Is this the expected behavior or am I
>> > missing something by which I can group all the clock entries into a
>> > group at the top or bottom? Also I remember that I was able to hide
>> > entire clock entries.
>>
>> Take a look at the variable org-clock-into-drawer. This saves your
>> clock entries in a :LOGBOOK: drawer which you can expand or hide.
>
> Mine says this:
>
> org-clock-into-drawer's value is t
>
> Documentation:
> Should clocking info be wrapped into a drawer?
> When t, clocking info will always be inserted into a :CLOCK: drawer.
> If necessary, the drawer will be created.
> When nil, the drawer will not be created, but used when present.
> When an integer and the number of clocking entries in an item
> reaches or exceeds this number, a drawer will be created.
>
>
> alas with my current version (6.21), it still spreads clock items
> everywhere. Is it something known ? Should I update my orgmode
> copy ?
I also have org-log-into-drawer set to t. I don't remember this
functionality changing recently. Try restarting your emacs and if that
doesn't fix it, upgrade org-mode and retest. If the problem persists
make a minimal emacs setup that creates the problem and post that so
others can try to duplicate what you are seeing.
Specifying your emacs version might also be helpful.
-Bernt