[O] Scheduling calling debugger
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 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-in-active-region(Scheduled to 2011-07-21 Thu) org-schedule(nil) call-interactively(org-schedule nil nil) PS: this is with emacs -Q with Org-mode version 7.6 release_7.6.100.gde4d on GNU Emacs 24.0.50.1 -- Suvayu Open source is the future. It sets us free.
Re: [O] Scheduling calling debugger
Suvayu Ali fatkasuvayu+li...@gmail.com 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-in-active-region(Scheduled to 2011-07-21 Thu) org-schedule(nil) call-interactively(org-schedule nil nil) PS: this is with emacs -Q with Org-mode version 7.6 release_7.6.100.gde4d on GNU Emacs 24.0.50.1 I can not reproduce that with Org-mode version 7.6 (release_7.6.120.g0b9c.dirty) on GNU Emacs 23.3.1 (i486-pc-linux-gnu, GTK+ Version 2.24.3) of 2011-04-10 on raven, modified by Debian Memnon
Re: [O] Scheduling calling debugger
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 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-in-active-region(Scheduled to 2011-07-21 Thu) org-schedule(nil) call-interactively(org-schedule nil nil) This looks like a macro problem. Could you try make clean make and see if the problem still persists? Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgp2Wt9LTZTBq.pgp Description: PGP signature
Re: [O] Scheduling calling debugger
Hi David and Memnon, Thank you for looking at this. On Tue, Jul 19, 2011 at 7:53 PM, David Maus dm...@ictsoc.de 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(nil) call-interactively(org-schedule nil nil) This looks like a macro problem. Could you try make clean make and see if the problem still persists? That solved it! Just for the sake of understanding, what was most likely the issue here and what is a macro problem? Best, -- David Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] Scheduling calling debugger
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 dm...@ictsoc.de 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(nil) call-interactively(org-schedule nil nil) This looks like a macro problem. Could you try make clean make and see if the problem still persists? 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) ^^^ Invalid function means that Emacs was not able to get a callable function for the symbol named 'org-loop-over-siblings-in-active-region` It tried to look up one, but failed[1]. 'org-loop-over-siblings-in-active-region' is a macro (hence macro problem). A macro is a Lisp structure that expands into Lisp code if you compile (or run) a Lisp application.[2] I suppose what happened was, that Emacs knew that loop-over-siblings is a macro but got confused with the new .el and the old .elc files and couldn't look up what the macro should expand into. Thus the invalid function error. The old .elc files were the issue. Best, -- David [1] See Emacs Elisp manual, http://www.gnu.org/s/emacs/manual/html_node/elisp/Function-Indirection.html [2] http://www.gigamonkeys.com/book/macros-defining-your-own.html -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpwh0mNz9HOk.pgp Description: PGP signature
Re: [O] Scheduling calling debugger
Hi David, On Tue, Jul 19, 2011 at 8:44 PM, David Maus dm...@ictsoc.de 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) ^^^ Invalid function means that Emacs was not able to get a callable function for the symbol named 'org-loop-over-siblings-in-active-region` It tried to look up one, but failed[1]. 'org-loop-over-siblings-in-active-region' is a macro (hence macro problem). A macro is a Lisp structure that expands into Lisp code if you compile (or run) a Lisp application.[2] [...] Best, -- David [1] See Emacs Elisp manual, http://www.gnu.org/s/emacs/manual/html_node/elisp/Function-Indirection.html [2] http://www.gigamonkeys.com/book/macros-defining-your-own.html Thank you for the clear explanation and the pointers to the references. I will definitely go through them. :) -- Suvayu Open source is the future. It sets us free.
