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

Hi David,

On Tue, Jul 19, 2011 at 8:44 PM, David Maus <dmaus@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.

      reply	other threads:[~2011-07-19 22:38 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
2011-07-19 22:37       ` suvayu ali [this message]

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=CAMXnza2WSko4-dk1b+pEF4YdgnG5bJOCV3qqfNOENB64ObjoMA@mail.gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    /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).