emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Maus <dmaus@ictsoc.de>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: David Maus <dmaus@ictsoc.de>,
	Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Scheduling calling debugger
Date: Tue, 19 Jul 2011 20:44:20 +0200	[thread overview]
Message-ID: <87y5zuyut7.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <CAMXnza3-oMnCBdd_5uadTgrW2Q5M=7ubFxfcb_W=yGqtGYG9VA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1757 bytes --]

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 <dmaus@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.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]

  reply	other threads:[~2011-07-19 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 11:22 Scheduling calling debugger Suvayu Ali
2011-07-19 14:30 ` Memnon Anon
2011-07-19 17:53 ` David Maus
2011-07-19 18:23   ` suvayu ali
2011-07-19 18:44     ` David Maus [this message]
2011-07-19 22:37       ` suvayu ali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y5zuyut7.wl%dmaus@ictsoc.de \
    --to=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).