From: Rainer Stengele <rainer.stengele@online.de>
To: Bastien <bzg@altern.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Debugger entered--Lisp error: (void-variable org-keys)
Date: Thu, 30 Aug 2012 10:28:36 +0200 [thread overview]
Message-ID: <503F2434.9010203@online.de> (raw)
In-Reply-To: <87fw75gclx.fsf@altern.org>
Am 30.08.2012 07:42, schrieb Bastien:
> Achim Gratz <Stromeko@nexgo.de> writes:
>
>> 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.
>
> I don't have any steady theory about this, but as a convention I try to
> (defvar [var] nil) for dynamically bound vars in the current file and to
> (defvar [var]) for variables declared in other files. I just cleaned-up
> org-agenda.el a bit wrt this.
>
> Thanks for the heads up,
>
Thanks Bastien, no more "Lisp error"!
Now - being in a sticky agenda and jumping to another date via "j" the
agenda command called is not the one I was in.
Example:
I am in "Org Agenda(01)", jump to yesterday and get "Org Agenda(a)",
which of course is not what I want.
This looks like a bug.
Thanks again,
Rainer
next prev parent reply other threads:[~2012-08-30 8:28 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
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 [this message]
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=503F2434.9010203@online.de \
--to=rainer.stengele@online.de \
--cc=Stromeko@nexgo.de \
--cc=bzg@altern.org \
--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).