From: Bastien <bzg@altern.org>
To: mb@mkblog.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Upgrade to org 7.9.3.: clock in/out and org-odt export
Date: Tue, 08 Jan 2013 23:48:53 +0100 [thread overview]
Message-ID: <87sj6b2sve.fsf@bzg.ath.cx> (raw)
In-Reply-To: <50EC7D34.8010009@mkblog.org> (Martin Butz's message of "Tue, 08 Jan 2013 21:10:28 +0100")
Hi Martin,
Martin Butz <mb@mkblog.org> writes:
> (1) Clock in/out just by toggeling the task state does not work anymore.
> For starting and stopping the clock I have the code from Sacha Chua [2]
> in my dot-emacs. I suppose, that this does not work any more with the
> new org-code. As I frequently rely on the clock I would be glad to solve
> the problem. Does someone have a hint for me?
You can add a function to `org-after-todo-state-change-hook',
which will call `org-clock-in/out' at some point. But better to ask
Sacha since this is her code.
> (2) I did some tests with the org-odt-exporter, which where successful
> in case of a small test file but failed with some of my daily used file.
> In one case the emacs message buffer seemed to contain the whole export
> output (pasting just a few lines here)
> #(" " 0 10 (face org-indent)) wrap-prefix #(" " 0 10
> (face org-indent))) 48810 49241 (fontified nil org-category
> "hfk-design-durch-aneignung" line-prefix #(" " 0 10 (face
> org-indent)) wrap-prefix #(" " 0 13 (face org-indent)))
> 49241 49242 (fontified nil org-category "hfk-design-durch-aneignung"
> line-prefix #(" " 0 10 (face org-indent)) wrap-prefix #("
> " 0 10 (face org-indent))) 49242 49340 (fontified nil org-category
> "hfk-design-durch-aneignung" line-prefix #(" " 0 10 (face
> org-indent)) wrap-prefix #(" " 0 13 (face org-indent)))
> 49341 49361 (original-indentation 0) 49361 49362 (fontified nil
> org-category "hfk-design-durch-aneignung" line-prefix #(" " 0
> 10 (face org-indent)) wrap-prefix #(" " 0 13 (face
> org-indent))) 49362 49374 (fontified nil org-category
> "hfk-design-durch-aneignung" line-prefix #(
>
> I did get nothing else and wonder, what's the best way to debug such
> a case?
I suggest to bisect the .org source file until you find the part that
prevents ODT exports.
Best,
--
Bastien
next prev parent reply other threads:[~2013-01-08 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 20:10 Upgrade to org 7.9.3.: clock in/out and org-odt export Martin Butz
2013-01-08 22:48 ` Bastien [this message]
2013-01-09 5:31 ` Jambunathan K
2013-01-09 8:06 ` Martin Butz
2013-01-09 19:25 ` Martin Butz
2013-01-09 20:19 ` Jambunathan K
2013-01-10 9:53 ` Martin Butz
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=87sj6b2sve.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=mb@mkblog.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).