From: Carsten Dominik <dominik@science.uva.nl>
To: Christopher Kuettner <ckuettner@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: debug agenda-buffer deadlines
Date: Fri, 27 Oct 2006 19:11:56 +0200 [thread overview]
Message-ID: <97c034b9577f08a5ee24bf2438239882@science.uva.nl> (raw)
In-Reply-To: <4540C650.1000702@gmail.com>
Hi Christopher,
I need more information to find this bug.
Either make me a small example file that will reproduce this bug if I
set my org-agenda-files to just this file.
Or try to make me a traceback (I need to document in the manual how to
do this). Here is how:
First, load org.el uncompiled - i.e. temporarily rename org.elc to
something else, then start Emacs again.
In the Options menu, turn on "Enter debugger on error".
Run into the error, A bugger *Backtrace* will be shown, send me the
content of that buffer.
Thanks.
- Carsten
On Oct 26, 2006, at 16:29, Christopher Kuettner wrote:
> yesterday I added some deadlines to my sole agenda-file. today, when
> invoking *Agenda* with C-c a a I get following message:
>
> org-agenda-get-deadlines: Wrong type argument: number-or-marker-p, nil
>
> The *Agenda* is shown but when I want to switch day/week I get:
>
> org-agenda-check-type: Not allowed in nil-type agenda buffers
>
> Invoking the *Agenda* with C-c a L gives me:
>
> byte-code: Cannot restrict agenda to current buffer
>
> Regards,
> Christopher
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
prev parent reply other threads:[~2006-10-27 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 14:29 debug agenda-buffer deadlines Christopher Kuettner
2006-10-27 17:11 ` Carsten Dominik [this message]
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=97c034b9577f08a5ee24bf2438239882@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=ckuettner@gmail.com \
--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 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.