Re: [O] problems invoking org-agenda

[Peter Salazar]

Ah perfect! I followed your steps and tracked the problem down to one of my agenda files. Not sure why org didn't like it, but when I removed that file from my agenda list, it worked like a charm.

Thank you!

On Sat, Feb 25, 2012 at 12:52 AM, Nick Dokos <address@hidden> wrote:

Peter Salazar <address@hidden> wrote:

> Maybe this is too esoteric for anyone to know, but I'm struggling and I can't figure this out. 
>
> The time is Aquamacs 2.4. The place is org-mode 7.8.03. When I try to invoke org-agenda (C-c a a ---
> i.e.  "Agenda for current week or day"), I get the error message: 
>
> Args out of range: #(" work :        " 0 14 org-category "work" tags nil org-highest-priority 65
> or-lowest priority 67 time-of-day nil ...)), 0, 20
>
> As far as I know I don't have any categories or priorities. 
>
> Has anyone seen this before? 
>

It's probably because of a bad customization. To make sure,
run with a minimal .emacs that just loads org and *none*
of your customizations, something as simple as the following
(with obvious adjustments for your setup):

--8<---------------cut here---------------start------------->8---
;;; -*- mode: emacs-lisp -*-
;;; constant part
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)

(setq debug-on-error t)
(setq debug-on-quit t)
(setq eval-_expression_-print-length nil)
(setq eval-_expression_-print-level nil)

(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
--8<---------------cut here---------------end--------------->8---

Save this in your home directory as minimal.org.el and start emacs
with

       emacs -q -l ~/minimal.org.el

and then do C-c a a - do you get the error? Probably not.

The second thing you should do (this in your full emacs session,
where you get the error) is

M-x toggle-debug-on-error RET

and then C-c a a to trigger the error - but now it will produce a
backtrace which should tell you where the error occurred.  If you can't
figure it out, post the backtrace to the list.

Nick