From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Debugger entered--Lisp error: (void-variable org-keys)
Date: Wed, 29 Aug 2012 20:30:05 +0200 [thread overview]
Message-ID: <87ehmpd00i.fsf@Rainer.invalid> (raw)
In-Reply-To: 2950.1346264029@alphaville
Nick Dokos writes:
> There was a backtrace in Rainer's original message complaining about
> org-keys not being defined. If I had to guess, I'd say it looks like a
> frankenstein build to me, but I'm really not sure.
Yes, but he's since re-made the autoloads file at least and the new
backtrace might be different.
Anyway, org-keys is defined in org-agenda and it looks like most if not
all of the backtrace is also from org-agenda, and it's been a recent
addition by Bastien… it seems that it is declared as a dynamic variable
but not bound in all autoloaded functions, so there definitely are
codepaths that might find this variable undefined. I don't know if
something would preclude the declaration be changed to e definition with
nil as a value, but I think Bastien would know.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2012-08-29 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 15:40 Debugger entered--Lisp error: (void-variable org-keys) Rainer Stengele
2012-08-29 16:21 ` Nick Dokos
2012-08-29 17:40 ` Rainer Stengele
2012-08-29 17:57 ` Bastien
2012-08-29 18:02 ` Achim Gratz
2012-08-29 18:13 ` Nick Dokos
2012-08-29 18:30 ` Achim Gratz [this message]
2012-08-29 20:25 ` Rainer Stengele
2012-08-29 20:46 ` Nick Dokos
2012-08-30 6:08 ` Nick Dokos
2012-08-30 5:42 ` Bastien
2012-08-30 8:28 ` Rainer Stengele
2012-08-30 8:58 ` Bastien
2012-08-30 9:24 ` Rainer Stengele
2012-08-30 9:52 ` Bastien
2012-08-30 10:05 ` Rainer Stengele
2012-08-30 11:25 ` Bastien
2012-08-30 12:30 ` Rainer Stengele
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=87ehmpd00i.fsf@Rainer.invalid \
--to=stromeko@nexgo.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).