From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Upgrade to org 7.9.3.: clock in/out and org-odt export Date: Tue, 08 Jan 2013 23:48:53 +0100 Message-ID: <87sj6b2sve.fsf@bzg.ath.cx> References: <50EC7D34.8010009@mkblog.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52633) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tshyb-0000h4-E6 for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 17:48:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tshya-000249-7c for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 17:48:57 -0500 Received: from mail-we0-f172.google.com ([74.125.82.172]:51226) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tshya-000242-1F for emacs-orgmode@gnu.org; Tue, 08 Jan 2013 17:48:56 -0500 Received: by mail-we0-f172.google.com with SMTP id r3so754739wey.17 for ; Tue, 08 Jan 2013 14:48:55 -0800 (PST) In-Reply-To: <50EC7D34.8010009@mkblog.org> (Martin Butz's message of "Tue, 08 Jan 2013 21:10:28 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: mb@mkblog.org Cc: emacs-orgmode@gnu.org Hi Martin, Martin Butz 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