Hi David,
On Tue, Jul 19, 2011 at 8:44 PM, David Maus wrote:
>> That solved it! Just for the sake of understanding, what was most
>> likely the issue here and what is a "macro problem"?
>
> My diagnosis went like this:
>
> (invalid-function org-loop-over-siblings-in-active-region)
> ^^^
>
> Inva
At Tue, 19 Jul 2011 20:23:40 +0200,
suvayu ali wrote:
>
> Hi David and Memnon,
>
> Thank you for looking at this.
>
> On Tue, Jul 19, 2011 at 7:53 PM, David Maus wrote:
> >> Debugger entered--Lisp error: (invalid-function
> >> org-loop-over-siblings-in-active-region)
> >> org-loop-over-sibli
Hi David and Memnon,
Thank you for looking at this.
On Tue, Jul 19, 2011 at 7:53 PM, David Maus wrote:
>> Debugger entered--Lisp error: (invalid-function
>> org-loop-over-siblings-in-active-region)
>> org-loop-over-siblings-in-active-region("Scheduled to <2011-07-21 Thu>")
>> org-schedule(n
At Tue, 19 Jul 2011 13:22:10 +0200,
Suvayu Ali wrote:
>
> Hi Orgers,
>
> Scheduling or rescheduling seems to be invoking the debugger for me (I
> run emacs with debug-on-error set to t). Although it doesn't seem to do
> anything wrong to the scheduled entry. Strange!
>
> The error at the end was ge
Suvayu Ali writes:
> The error at the end was generated on attempting to reschedule a
> headline like this:
>
> ** TODO Read note on fitter
>SCHEDULED: <2011-07-19 Tue>
>
> Debugger entered--Lisp error: (invalid-function
> org-loop-over-siblings-in-active-region)
> org-loop-over-siblings-i
Hi Orgers,
Scheduling or rescheduling seems to be invoking the debugger for me (I
run emacs with debug-on-error set to t). Although it doesn't seem to do
anything wrong to the scheduled entry. Strange!
The error at the end was generated on attempting to reschedule a
headline like this:
** TODO R
