John Wiegley writes:
> On Oct 19, 2009, at 11:41 AM, Bernt Hansen wrote:
>
>> Is there a way to turn off the idle time check to support the old
>> functionality?
>
> I'll a configuration variable for this, to disable auto-resolution
> entirely.
Thanks,
-Bernt
_
On Oct 19, 2009, at 11:41 AM, Bernt Hansen wrote:
Is there a way to turn off the idle time check to support the old
functionality?
I'll a configuration variable for this, to disable auto-resolution
entirely.
John
___
Emacs-orgmode mailing list
John Wiegley writes:
> Looking for anyone who uses Org's time clocking facilities and is
> willing to test this with me. I've been using it for a couple of days
> now. The functionality is based on the way the commercial app
> OfficeTime handles idleness.
>
> Excerpt from the new manual section
On Oct 16, 2009, at 2:09 PM, Gregory J. Grubbs wrote:
Since my intention was to clock in to A, I would find it confusing in
any event to suddenly find myself clocked into B. Even in the case
of a
dangling clock caused by an emacs crash, I would prefer to stay in
control! Should task B strik
John Wiegley writes:
> On Oct 16, 2009, at 11:59 AM, Gregory J. Grubbs wrote:
>
>> One suggestion: I think when your code stops on a clock and prompts to
>> keep/subtract/cancel, it should expand the drawer (for those of us who
>> use drawers).
>
> I've added this to the version of the patch belo
On Oct 16, 2009, at 1:41 PM, John Wiegley wrote:
At the moment, the auto-resolver only checks files which are
referred to by org-agenda-files. It does not scan the entire buffer
list looking for any org-mode buffer. Do you think it should do the
latter instead?
I have a better answer fo
On Oct 16, 2009, at 1:02 PM, Jeff Kowalczyk wrote:
I am unable to reproduce the
cancel-timer failure here. Please load org-clock.el into Emacs and
type M-x eval-buffer and then trigger it again, that I may see the
complete stack trace.
No error anymore as mentioned above.
I'm not sure I'm tr
John Wiegley gmail.com> writes:
>
> On Oct 16, 2009, at 10:25 AM, Jeff Kowalczyk wrote:
>
> > I applied the patch against 93f396, and on Emacs 23.1 I get an error
> > when clocking in. The error happens the first clock-in for
> > each Emacs session, but the 'invalid timer' message shows for
>
On Oct 16, 2009, at 11:59 AM, Gregory J. Grubbs wrote:
One suggestion: I think when your code stops on a clock and prompts to
keep/subtract/cancel, it should expand the drawer (for those of us who
use drawers).
I've added this to the version of the patch below.
As another question:
When atte
On Oct 16, 2009, at 10:25 AM, Jeff Kowalczyk wrote:
I applied the patch against 93f396, and on Emacs 23.1 I get an error
when
clocking in. The error happens the first clock-in for each Emacs
session, but
the 'invalid timer' message shows for subsequent clock-in/out.
In org-clock.el, on lin
John Wiegley writes:
> Looking for anyone who uses Org's time clocking facilities and is
> willing to test this with me. I've been using it for a couple of days
> now. The functionality is based on the way the commercial app
> OfficeTime handles idleness.
Wow. Your patch helped me clean up a m
John Wiegley gmail.com> writes:
> Looking for anyone who uses Org's time clocking facilities and is
> willing to test this with me. I've been using it for a couple of days
> now. The functionality is based on the way the commercial app
> OfficeTime handles idleness.
Hi John,
This is int
12 matches
Mail list logo
