Re: [O] Feature that org mode needs most
Steinar Bang writes: >> Bastien : >> Steinar Bang writes: > >>> (The previously clocked item and it's :CLOCK: drawer was opened. I don't >>> know if that was intentional, or not...?) > >> This is intentional -- to make sure you see the change. > >> But perhaps the message is enough. Let me know if you think so. > > No, I'm good with the current behaviour. Okay -- thanks for letting me know, -- Bastien
Re: [O] Feature that org mode needs most
> Bastien : > Steinar Bang writes: >> (The previously clocked item and it's :CLOCK: drawer was opened. I don't >> know if that was intentional, or not...?) > This is intentional -- to make sure you see the change. > But perhaps the message is enough. Let me know if you think so. No, I'm good with the current behaviour. Thanks!
Re: [O] Feature that org mode needs most
Hi Steinar, Steinar Bang writes: > (The previously clocked item and it's :CLOCK: drawer was opened. I don't > know if that was intentional, or not...?) This is intentional -- to make sure you see the change. But perhaps the message is enough. Let me know if you think so. -- Bastien
Re: [O] Feature that org mode needs most
> Bastien : >> is this known, and has been fixed later than the above commit? If so, I >> can pull, and try again. > It should be fixed now, please confirm. I can confirm it works. Ie. that it adjusts the end time of the previously clocked item correctly. My current latest commit after the pull, is 952d722dcddb275d84ad6dd356bee2fd5c8027c8 (The previously clocked item and it's :CLOCK: drawer was opened. I don't know if that was intentional, or not...?) Thanks!
Re: [O] Feature that org mode needs most
Hi Steinar, Steinar Bang writes: > is this known, and has been fixed later than the above commit? If so, I > can pull, and try again. It should be fixed now, please confirm. Thanks, -- Bastien
Re: [O] Feature that org mode needs most
> Bastien : > Steinar Bang writes: >> I will pull and try the new functionality. > Yes -- please let me know. The drawback of this functionality is that > it changes things outside of sight, which I don't really like. You get > a message, and the subtree of the (possibly distant) clock get unfolded, > but perhaps the change can be made more visible -- or "into control". My git version of org has commit d02eedc987ab73ae5de5dacf3825536c3252c6e5 as its newest commit. What happens here is that when I do S-M-down on minutes in the start time of the current clock, it adjust both the current clock and the previous clock with 5 minutes, but the cursor ends up in the end time of the previous clock and have to be moved back to do further adjustments. is this known, and has been fixed later than the above commit? If so, I can pull, and try again.
Re: [O] Feature that org mode needs most
Steinar Bang writes: > I will pull and try the new functionality. Yes -- please let me know. The drawback of this functionality is that it changes things outside of sight, which I don't really like. You get a message, and the subtree of the (possibly distant) clock get unfolded, but perhaps the change can be made more visible -- or "into control". Let me know, -- Bastien
Re: [O] Feature that org mode needs most
Hi Sébastien, "Sebastien Vauban" writes: > I'm back from a black hole for some time, and still have 100's of Org posts to > read, so my question can be already answered somewhere... Welcome back! > In the following case: > > ** Some task (A) >:LOGBOOK: >CLOCK: [2012-08-01 Wed 13:34]--[2012-08-01 Wed 15:00] => 1:26 >:END: > > ** Another one (B) >:LOGBOOK: >CLOCK: [2010-08-01 Thu 15:00]--[2010-08-01 Thu 16:45] => 1:45 >:END: > > Do you mean that changing the *beginning timestamp* of task B would change the > *ending timestamp* of task A? Yes. > In the other way as well: changing A's end impacting B's beginning > time? Yes. > Is it based on the clock history file (limited in number of entries), or > generally speaking based on the fact that those 2 timestamps were simply > identical? It is based on `org-clock-history'. HTH, -- Bastien
Re: [O] Feature that org mode needs most
> Bastien : > The keybindings are S-M-. ...and requires a fresh pull from git. I will pull and try. [snip!] >> I'm guessing it's the first, because I've used S-up and S-down, but I >> haven't seen them adjust the previously clocked item (my clocked >> items are often far apart). > Did you see a message saying that a clock had been adjusted? No, but since I've only used S-up and S-down on pre-summer git pulls (eg. the org-mode on this particular machine was last pulled om May 8), that's probably as expected. :-) I will pull and try the new functionality.
Re: [O] Feature that org mode needs most
Hi Bastien, Bastien wrote: > Steinar Bang writes: >>> Mehul Sanghvi : >>> You can use the S-up and S-down key combinations to adjust the clocks >>> for the current activity and the previous one. >> >> Is that "previous" as in the "previous item in the org tree" or as the >> "previously clocked item"? > > As "previously clocked item". > >> I'm guessing it's the first, because I've used S-up and S-down, but I >> haven't seen them adjust the previously clocked item (my clocked items >> are often far apart). > > Did you see a message saying that a clock had been adjusted? > > You should see a message in any case, either saying a clock has been > adjusted or saying no related clock could be found. I'm back from a black hole for some time, and still have 100's of Org posts to read, so my question can be already answered somewhere... In the following case: --8<---cut here---start->8--- ** Some task (A) :LOGBOOK: CLOCK: [2012-08-01 Wed 13:34]--[2012-08-01 Wed 15:00] => 1:26 :END: ** Another one (B) :LOGBOOK: CLOCK: [2010-08-01 Thu 15:00]--[2010-08-01 Thu 16:45] => 1:45 :END: --8<---cut here---end--->8--- Do you mean that changing the *beginning timestamp* of task B would change the *ending timestamp* of task A? In the other way as well: changing A's end impacting B's beginning time? Is it based on the clock history file (limited in number of entries), or generally speaking based on the fact that those 2 timestamps were simply identical? Best regards, Seb -- Sebastien Vauban
Re: [O] Feature that org mode needs most
Steinar Bang writes: >> Mehul Sanghvi : > >> You can use the S-up and S-down key combinations to adjust the clocks >> for the current activity and the previous one. The keybindings are S-M-. > > Is that "previous" as in the "previous item in the org tree" or as the > "previously clocked item"? As "previously clocked item". > I'm guessing it's the first, because I've used S-up and S-down, but I > haven't seen them adjust the previously clocked item (my clocked items > are often far apart). Did you see a message saying that a clock had been adjusted? You should see a message in any case, either saying a clock has been adjusted or saying no related clock could be found. -- Bastien
Re: [O] Feature that org mode needs most
> Mehul Sanghvi : > You can use the S-up and S-down key combinations to adjust the clocks > for the current activity and the previous one. Is that "previous" as in the "previous item in the org tree" or as the "previously clocked item"? I'm guessing it's the first, because I've used S-up and S-down, but I haven't seen them adjust the previously clocked item (my clocked items are often far apart).
Re: [O] Feature that org mode needs most
Hi Joseph, Joseph Thomas writes: > This solution best best allows me to keep accurate clocks without > disrupting focus on my current activity, and will already make a big > difference going forward. You might want to have a look at `org-clock-continuously', that I implemented last week. It defaults to nil, but from the docstring: "Non-nil means to start clocking from the last clock-out time, if any." > If, in the future though, you implemented > S-up and S-down functionality so that it adjusted current and > previous clocks simultaneously (or at least the ability to turn this > on as an option), I would be your biggest fan :) I implemented this. S-M- on a clock timestamp will try to update the previous/next clock timestamp too. Please test this heavily. Thanks, -- Bastien
Re: [O] Feature that org mode needs most
Hi Joseph, Joseph Thomas writes: > Could you make a suggestion? >From latest git, you can now use `C-c C-x C-z'. Nothing really logical -- ideally, this would have been C-c C-x C-zz ... :) -- Bastien
Re: [O] Feature that org mode needs most
Da: Joseph Thomas Inviato: Mercoledì 18 Luglio 2012 16:06 > I plan to use org-resolve-clocks much more > regularly than perhaps it was intended, I would like to make a key biniding > for it. > If there are plans to do this in an emacs distribution at some point, I don't think so: key bindings are really personal, depends on how much you do use the function bond ;-) > I'd like to choose something logical- ideally something that the org team > would choose. > Could you make a suggestion? how about F11 like Bernt? cheers, Giovanni
Re: [O] Feature that org mode needs most
Da: John Hendy Inviato: Mercoledì 18 Luglio 2012 20:26 Hi, John > You might want to check out Brent's answer to a similar question I > asked a bit back (basically an expanded version of some answers given > above): > - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40499.html I haven't tought to the "K" option! really thank you! ...Giovanni
Re: [O] Feature that org mode needs most
You might want to check out Brent's answer to a similar question I asked a bit back (basically an expanded version of some answers given above): - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg40499.html Also, per your shortcut question, I have this in ~/.emacs: ,--- | (global-set-key "\C-cr" 'org-resolve-clocks) `--- Best regards, John
Re: [O] Feature that org mode needs most
Thanks so much, I'll follow the instructions on this page, it seems like a better approach than what I did earlier today. On Wed, Jul 18, 2012 at 11:46 AM, Giovanni Ridolfi < giovanni.rido...@yahoo.it> wrote: > Da: Joseph Thomas > Inviato: Mercoledì 18 Luglio 2012 16:01 > > > I did download the latest snapshot of org from git, but as I need to > maintain my todo.in > > > NT emacs at work, I don't have make > > > and so > > and so . > > you read the nice page on worg written by Achim Gratz > http://orgmode.org/worg/org-hacks.html > and followed the instructions for us leaving through the Windows > > great! > > juice of the instructions---BUT > PLEASE READ THEM ALL - > > your current directory must be where org has been unpacked into > > Windows CMD.exe has quite different quoting rules and this won't work, so > your other option is to start Emacs like this > emacs -Q -L lisp -l ../UTILITIES/org-fixup > then paste the following into the *scratch* buffer > (let ((org-fake-release "7.8.11") (org-fake-git-version "7.8.11-fake")) > (org-make-autoloads)) > position the cursor after the closing paren and press C-j or C-x C-e to > evaluate the form. > - >
Re: [O] Feature that org mode needs most
Da: Joseph Thomas Inviato: Mercoledì 18 Luglio 2012 16:01 > I did download the latest snapshot of org from git, but as I need to >maintain my todo.in > NT emacs at work, I don't have make > and so and so . you read the nice page on worg written by Achim Gratz http://orgmode.org/worg/org-hacks.html and followed the instructions for us leaving through the Windows great! juice of the instructions--- BUT PLEASE READ THEM ALL - your current directory must be where org has been unpacked into Windows CMD.exe has quite different quoting rules and this won't work, so your other option is to start Emacs like this emacs -Q -L lisp -l ../UTILITIES/org-fixup then paste the following into the *scratch* buffer (let ((org-fake-release "7.8.11") (org-fake-git-version "7.8.11-fake")) (org-make-autoloads)) position the cursor after the closing paren and press C-j or C-x C-e to evaluate the form. -
Re: [O] Feature that org mode needs most
Forgot to ask in my last response- since I plan to use org-resolve-clocks much more regularly than perhaps it was intended, I would like to make a key biniding for it. If there are plans to do this in an emacs distribution at some point, I'd like to choose something logical- ideally something that the org team would choose. Could you make a suggestion? Thanks again! Joe On Wed, Jul 18, 2012 at 4:50 AM, Giovanni Ridolfi wrote: > > > Hi, Joseph, > (I cc'ed also Bernt Hansen, aka "the king of clocking" ;-) > maybe he has better ideas; he's more experience than me, for sure ;) > > > Da: Joseph Thomas > Inviato: Martedì 17 Luglio 2012 23:15 > > > there's no easy way I can see to make quick adjustments to clocked time > between activities. > > > Every day I will forget to clock to a new activity at some point. > > > By the time I remember, time has passed. For example, I come back from > a meeting and begin to work on a project. > > > 20 minutes into it, I clock in. > > > But I must then manually adjust both the previous activity and the > current one so that they are accurate and don't overlap in the agenda view. > > > When you can back from a meeting you can resolve idel time > [[info:org#Resolving%20idle%20time][info:org#Resolving idle time]] > > > If you changed your task but you forgot to clock outyou should check: > > [[info:org#Clocking%20commands][info:org#Clocking commands]] > > (`org-clock-in-last')' > Reclock the last clocked task. With one `C-u' prefix argument, > select the task from the clock history. With two `C-u' prefixes, > force continuous clocking by starting the clock when the last clock > stopped. > > > Be careful to have a recent git version since this is a new feature, but > it had bugs and > the bugs have been fixed. > > > Other thoughts: > > You can change the time from the agenda (never tried) but: > > [[info:org#Agenda%20commands][info:org#Agenda commands]] > `v c' > Show overlapping clock entries, clocking gaps, and other clocking > problems in the current agenda range. You can then visit clocking > lines and fix them manually. See the variable > `org-agenda-clock-consistency-checks' for information on how to > customize the definition of what constituted a clocking problem. > To return to normal agenda display, press `l' to exit Logbook mode. > > > Finally you can also use the brute force method: > clock in the new task > > then run > > M-x org-resolve-clocks > > > so that you can "restart" your current task by, say, 20 minutes > then you can set > > > (defcustom org-clock-out-remove-zero-time-clocks t > "Non-nil means remove the clock line when the resulting time is zero." > :group 'org-clock > :type 'boolean) > > However the last clocked-out task (the meeting) has been clocked out 20 > minutes later. > > cheers, > Giovanni > >
Re: [O] Feature that org mode needs most
Giovanni, thanks so much for taking the time to respond. I had learned about the idle time feature from the info docs when I first started using org. The reason this solution won't work for me though is that, if I understand correctly, it would only apply in scenarios where my emacs session detects inactivity for the configured amount of time, like when I leave my desk. If so, this doesn't cover the scenarios where I begin working on a new task at my computer but forget to clock-in to the new task in org (about 60% of the cases where I forget). However, I reviewed your other suggestions. I did download the latest snapshot of org from git, but as I need to maintain my todo.in NT emacs at work, I don't have make and so just hacked my config by replacing the emacs 23.4.1 distribution org .el files with the current ones. I needed to comment out the org-version.el warning, but otherwise everything seems to work fine. The new "v c" agenda view is great! Very useful. It appears for those like myself that what will work best under the latest functionality is the following use case, which I tested a little while ago: In my forget-to-clock-in-to-new-task scenario, 1. I use org-resolve-clocks, with the "K" option. 2. I then specify the number of minutes that passed since I forgot. 3. Clock in to the new task. 4. Org kindly asks me if I would like to clock-in but adjusting for the same amount of minutes. This solution best best allows me to keep accurate clocks without disrupting focus on my current activity, and will already make a big difference going forward. If, in the future though, you implemented S-up and S-down functionality so that it adjusted current and previous clocks simultaneously (or at least the ability to turn this on as an option), I would be your biggest fan :) Regards, Joe On Wed, Jul 18, 2012 at 4:50 AM, Giovanni Ridolfi wrote: > > > Hi, Joseph, > (I cc'ed also Bernt Hansen, aka "the king of clocking" ;-) > maybe he has better ideas; he's more experience than me, for sure ;) > > > Da: Joseph Thomas > Inviato: Martedì 17 Luglio 2012 23:15 > > > there's no easy way I can see to make quick adjustments to clocked time > between activities. > > > Every day I will forget to clock to a new activity at some point. > > > By the time I remember, time has passed. For example, I come back from > a meeting and begin to work on a project. > > > 20 minutes into it, I clock in. > > > But I must then manually adjust both the previous activity and the > current one so that they are accurate and don't overlap in the agenda view. > > > When you can back from a meeting you can resolve idel time > [[info:org#Resolving%20idle%20time][info:org#Resolving idle time]] > > > If you changed your task but you forgot to clock outyou should check: > > [[info:org#Clocking%20commands][info:org#Clocking commands]] > > (`org-clock-in-last')' > Reclock the last clocked task. With one `C-u' prefix argument, > select the task from the clock history. With two `C-u' prefixes, > force continuous clocking by starting the clock when the last clock > stopped. > > > Be careful to have a recent git version since this is a new feature, but > it had bugs and > the bugs have been fixed. > > > Other thoughts: > > You can change the time from the agenda (never tried) but: > > [[info:org#Agenda%20commands][info:org#Agenda commands]] > `v c' > Show overlapping clock entries, clocking gaps, and other clocking > problems in the current agenda range. You can then visit clocking > lines and fix them manually. See the variable > `org-agenda-clock-consistency-checks' for information on how to > customize the definition of what constituted a clocking problem. > To return to normal agenda display, press `l' to exit Logbook mode. > > > Finally you can also use the brute force method: > clock in the new task > > then run > > M-x org-resolve-clocks > > > so that you can "restart" your current task by, say, 20 minutes > then you can set > > > (defcustom org-clock-out-remove-zero-time-clocks t > "Non-nil means remove the clock line when the resulting time is zero." > :group 'org-clock > :type 'boolean) > > However the last clocked-out task (the meeting) has been clocked out 20 > minutes later. > > cheers, > Giovanni > >
Re: [O] Feature that org mode needs most
Am 17.07.2012 23:33, schrieb Mehul Sanghvi: > On Tue, Jul 17, 2012 at 5:15 PM, Joseph Thomas wrote: >> Hello. >> I couldn't believe I hadn't been aware of org mode until a few months ago, >> as someone who's been using emacs for everything for many years. >> >> I use it to journal how all my time is spent in a given work day- for both >> work related tasks and non-work tasks (ex. getting coffee, lunch, >> conversations, etc.). Org mode is the only GTD software package I've seen >> that makes this possible without getting in the way. It just needs one >> small thing that keeps it from being perfect. >> >> Those who use it the same way I do (as a log of how all time was spent in a >> given day), there's no easy way I can see to make quick adjustments to >> clocked time between activities. Every day I will forget to clock to a new >> activity at some point. By the time I remember, time has passed. For >> example, I come back from a meeting and begin to work on a project. 20 >> minutes into it, I clock in. But I must then manually adjust both the >> previous activity and the current one so that they are accurate and don't >> overlap in the agenda view. This can be cumbersome, which seems to go >> against the overall idea of org mode. All that is needed to correct it is >> either a new fn and key binding, or a prefix arg to org-clock-in that allows >> you to enter an adjustment (in this example, 20) to subtract from the >> previous clock's out time and current clock's in time. >> >> Seems like it would be a minor thing to add that would make an enormous >> difference for users like me. >> >> Thanks for reading my request! >> >> Regards, >> Joe > > > Joe, > > You can use the S-up and S-down key combinations to adjust the clocks for > the current activity and the previous one. Move over to the hour and > do S-up or S-down, > then do the same with the minutes. The date gets adjusted > automatically if you're > straddling midnight. > > > cheers, > >mehul > > p.s. does that make org-mode perfect now ? :) > > Hi, as a help being in agenda view pressing "v c" will: v c Show overlapping clock entries, clocking gaps, and other clocking problems in the current agenda range. You can then visit clocking lines and fix them manually. See the variable org-agenda-clock-consistency-checks for information on how to customize the definition of what constituted a clocking problem. To return to normal agenda display, press l to exit Logbook mode. Cheers, Rainer
Re: [O] Feature that org mode needs most
Hi, Joseph, (I cc'ed also Bernt Hansen, aka "the king of clocking" ;-) maybe he has better ideas; he's more experience than me, for sure ;) Da: Joseph Thomas Inviato: Martedì 17 Luglio 2012 23:15 > there's no easy way I can see to make quick adjustments to clocked time > between activities. > Every day I will forget to clock to a new activity at some point. > By the time I remember, time has passed. For example, I come back from a > meeting and begin to work on a project. > 20 minutes into it, I clock in. > But I must then manually adjust both the previous activity and the current >one so that they are accurate and don't overlap in the agenda view. When you can back from a meeting you can resolve idel time [[info:org#Resolving%20idle%20time][info:org#Resolving idle time]] If you changed your task but you forgot to clock outyou should check: [[info:org#Clocking%20commands][info:org#Clocking commands]] (`org-clock-in-last')' Reclock the last clocked task. With one `C-u' prefix argument, select the task from the clock history. With two `C-u' prefixes, force continuous clocking by starting the clock when the last clock stopped. Be careful to have a recent git version since this is a new feature, but it had bugs and the bugs have been fixed. Other thoughts: You can change the time from the agenda (never tried) but: [[info:org#Agenda%20commands][info:org#Agenda commands]] `v c' Show overlapping clock entries, clocking gaps, and other clocking problems in the current agenda range. You can then visit clocking lines and fix them manually. See the variable `org-agenda-clock-consistency-checks' for information on how to customize the definition of what constituted a clocking problem. To return to normal agenda display, press `l' to exit Logbook mode. Finally you can also use the brute force method: clock in the new task then run M-x org-resolve-clocks so that you can "restart" your current task by, say, 20 minutes then you can set (defcustom org-clock-out-remove-zero-time-clocks t "Non-nil means remove the clock line when the resulting time is zero." :group 'org-clock :type 'boolean) However the last clocked-out task (the meeting) has been clocked out 20 minutes later. cheers, Giovanni
Re: [O] Feature that org mode needs most
On Tue, Jul 17, 2012 at 5:15 PM, Joseph Thomas wrote: > Hello. > I couldn't believe I hadn't been aware of org mode until a few months ago, > as someone who's been using emacs for everything for many years. > > I use it to journal how all my time is spent in a given work day- for both > work related tasks and non-work tasks (ex. getting coffee, lunch, > conversations, etc.). Org mode is the only GTD software package I've seen > that makes this possible without getting in the way. It just needs one > small thing that keeps it from being perfect. > > Those who use it the same way I do (as a log of how all time was spent in a > given day), there's no easy way I can see to make quick adjustments to > clocked time between activities. Every day I will forget to clock to a new > activity at some point. By the time I remember, time has passed. For > example, I come back from a meeting and begin to work on a project. 20 > minutes into it, I clock in. But I must then manually adjust both the > previous activity and the current one so that they are accurate and don't > overlap in the agenda view. This can be cumbersome, which seems to go > against the overall idea of org mode. All that is needed to correct it is > either a new fn and key binding, or a prefix arg to org-clock-in that allows > you to enter an adjustment (in this example, 20) to subtract from the > previous clock's out time and current clock's in time. > > Seems like it would be a minor thing to add that would make an enormous > difference for users like me. > > Thanks for reading my request! > > Regards, > Joe Joe, You can use the S-up and S-down key combinations to adjust the clocks for the current activity and the previous one. Move over to the hour and do S-up or S-down, then do the same with the minutes. The date gets adjusted automatically if you're straddling midnight. cheers, mehul p.s. does that make org-mode perfect now ? :) -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
