emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Rainer Stengele <rainer.stengele@online.de>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Debugger entered--Lisp error: (void-variable org-keys)
Date: Wed, 29 Aug 2012 16:46:47 -0400	[thread overview]
Message-ID: <6580.1346273207@alphaville.americas.hpqcorp.net> (raw)
In-Reply-To: Message from Rainer Stengele <rainer.stengele@online.de> of "Wed, 29 Aug 2012 22:25:53 +0200." <503E7AD1.4020002@online.de>

Rainer Stengele <rainer.stengele@online.de> wrote:


> I use sticky Agenda since some months.
> Doing a "org-toggle-sticky-agenda" and calling any agenda function makes the error disappear!
> 

OK - that clarifies things: I don't use sticky agenda, so that explains
why I didn't get the error. Looking at the backtrace a bit more also
shows it clearly - 50/50 hindsight is such a blessing - but I didn't
look at it carefully the first time. I guess Achim's suggestion of
giving it an initial value in the defvar should work, but I don't
understand how org-keys is supposed to work.

Nick

> Here is my currrent backtrace, make autoloads does not change anything:
> 
> Debugger entered--Lisp error: (void-variable org-keys)
>   (and org-keys (stringp org-match))
>   (cond ((and org-keys (stringp org-match)) (format "*Org Agenda(%s:%s)*" org-keys org-match)) (org-keys (format "*Org Agenda(%s)*" org-keys)) (t "*Org Agenda(a)*"))
>   (setq org-agenda-buffer-name (cond ((and org-keys (stringp org-match)) (format "*Org Agenda(%s:%s)*" org-keys org-match)) (org-keys (format "*Org Agenda(%s)*" org-keys)) (t "*Org
> Agenda(a)*")))
>   (if org-agenda-sticky (setq org-agenda-buffer-name (cond ((and org-keys (stringp org-match)) (format "*Org Agenda(%s:%s)*" org-keys org-match)) (org-keys (format "*Org
> Agenda(%s)*" org-keys)) (t "*Org Agenda(a)*"))))
>   ...
>   org-agenda-list(nil "2012-08-22")
>   org-agenda-goto-date("2012-08-22")
>   call-interactively(org-agenda-goto-date nil nil)
> 

  reply	other threads:[~2012-08-29 20:46 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 [this message]
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=6580.1346273207@alphaville.americas.hpqcorp.net \
    --to=nicholas.dokos@hp.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rainer.stengele@online.de \
    /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).