From: Bernt Hansen <bernt@norang.ca>
To: Richard Riley <rileyrg@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: error navigating the agenda "org-agenda-earlier"
Date: Mon, 03 Jan 2011 19:10:36 -0500 [thread overview]
Message-ID: <87y671plz7.fsf@norang.ca> (raw)
In-Reply-To: <iftno9$vv1$1@dough.gmane.org> (Richard Riley's message of "Tue, 04 Jan 2011 00:56:57 +0100")
Richard Riley <rileyrg@googlemail.com> writes:
> Using org from git today:-
>
> C-c a a to bring up my agenda for the week.
>
> ,----
> | b runs the command org-agenda-earlier, which is an interactive compiled Lisp
> | function in `org-agenda.el'.
> `----
>
> Debugger entered--Lisp error: (error "Not allowed in nil-type agenda buffers")
> signal(error ("Not allowed in nil-type agenda buffers"))
> error("Not allowed in %s-type agenda buffers" nil)
> org-agenda-check-type(t agenda)
> org-agenda-later(-1)
> org-agenda-earlier(1)
> call-interactively(org-agenda-earlier nil nil)
>
> The first few "b" presses worked then sometime in my october I got the
> above.
>
> If you cant reproduce I can try and narrow it down more.
Hi Richard,
More information would be good. Things like:
- what is the SHA1 of the git commit are you on?
- Is it back that breaks or something on the week you are displaying?
- Is your org-agenda-files variable a list of files, directories, other?
I can't reproduce this here. I went back to September 2010 a week at a
time without any problems. I'm currently using org-agenda-files with a
list of directories instead of files (but I have no idea if that has
anything to do with your problem or not).
Regards,
Bernt
next prev parent reply other threads:[~2011-01-04 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 23:56 error navigating the agenda "org-agenda-earlier" Richard Riley
2011-01-04 0:10 ` Bernt Hansen [this message]
2011-01-04 0:18 ` Richard Riley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y671plz7.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=rileyrg@googlemail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.