From: Sven Gaerner <sgaerner@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Bug: clockreport-mode fails in agenda if org-startup-indented is t [6.33f]
Date: Fri, 8 Jan 2010 23:21:40 +0100 [thread overview]
Message-ID: <20100108232140.52c3936d@gmx.net> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 992 bytes --]
Hi,
first of all: thanks to all for this great mode. Since about 9 months
I'm running it nearly every day. I started with a very simple setup
that was extended every now and then.
I tried to use org-startup-indented in order not to add #+STARTUP:
hidestars to each org-mode file. After setting org-startup-indented to
true in my .emacs, I got the attached backtrace when trying to enable
the clockreport-mode within the agenda buffer.
If org-startup-indented is set to nil, the clockreport-mode is enabled
without any errors.
I reproduced this error also with an emacs that was started with -q. I
then just required org-install and org and created a single org-mode
file. Depending on the value of org-startup-indented, opening the
clockreport-mode within the agenda buffer works or fails.
The org-mode version is 6.33f.
It would be nice if someone could look into this matter.
Regards,
Sven
PS: Please CC any answers to me, I'm not subscribed to the list.
[-- Attachment #1.1.2: backtrace --]
[-- Type: application/octet-stream, Size: 7890 bytes --]
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-01-08 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 22:21 Sven Gaerner [this message]
2010-01-09 14:37 ` Bug: clockreport-mode fails in agenda if org-startup-indented is t [6.33f] Carsten Dominik
2010-01-10 12:03 ` Sven Gaerner
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=20100108232140.52c3936d@gmx.net \
--to=sgaerner@gmx.net \
--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).