From: Christian Moe <mail@christianmoe.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [PATCH][ANN] org-html/org-odt
Date: Mon, 21 Mar 2011 16:20:34 +0100 [thread overview]
Message-ID: <4D876CC2.3070708@christianmoe.com> (raw)
In-Reply-To: <81oc54txa4.fsf@gmail.com>
Hi,
I see. Would you like to continue to receive bug reports based on
byte-compilation, or should I just load the sources for now?
Yours,
Christian
On 3/21/11 2:31 PM, Jambunathan K wrote:
>
> Hello Christian
>
> Thanks for your first bug report. I have the habit of not using
> byte-compilation.
>
> The reason for the crash you have reported is that
> `with-org-html-preserve-paragraph-state' is a macro and some of the
> references to it preceded the definition. As a result the byte compiler
> was mistaken in to thinking that this was a function.
>
> Jambnathan K.
>
>> With a minimal Emacs as per the old instructions, and with one minor
>> change to your test file (`LaTeX:verbatim' -- I don't have dvipng
>> installed), I get this:
>>
>>
>> Debugger entered--Lisp error: (invalid-function
>> with-org-html-preserve-paragraph-state)
>> with-org-html-preserve-paragraph-state(nil)
>> byte-code("[...THIS LINE DIDN'T COPY-PASTE WELL... CHRISTIAN]
>> org-do-export(nil nil nil nil nil nil)
>> (let* ((org-parse-get-callback ...)
>> (org-export-html-special-string-regexps
>> org-export-odt-special-string-regexps)) (org-do-export arg hidden
>> ext-plist to-buffer body-only pub-dir))
>> org-export-as-odt(nil)
>> call-interactively(org-export-as-odt)
>> org-export(nil)
>> call-interactively(org-export nil nil)
>
>
next prev parent reply other threads:[~2011-03-21 15:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 18:32 [PATCH][ANN] org-html/org-odt Jambunathan K
2011-03-21 8:21 ` Bastien
2011-03-21 8:53 ` Christian Moe
2011-03-21 9:31 ` Jambunathan K
2011-03-21 11:06 ` Christian Moe
2011-03-21 13:31 ` Jambunathan K
2011-03-21 15:20 ` Christian Moe [this message]
2011-03-21 16:39 ` Jambunathan K
2011-03-21 19:38 ` Jambunathan K
2011-03-21 9:40 ` Jambunathan K
2011-03-21 8:55 ` Jambunathan K
2011-03-21 10:03 ` Jambunathan K
2011-03-21 21:26 ` Christian Moe
2011-04-12 8:33 ` Jambunathan K
2011-04-12 14:47 ` Christian Moe
2011-04-25 12:47 ` Christian Moe
2011-04-26 16:09 ` Jambunathan K
2011-03-25 22:32 ` Sean O'Halpin
2011-03-26 4:57 ` Jambunathan K
2011-04-15 20:39 ` [PATCH][ANN] org-html/org-odt/org-docbook Jambunathan K
2011-04-30 6:06 ` [PATCH][ANN] org-html/org-odt Jambunathan K
2011-04-30 6:54 ` Christian Moe
2011-05-01 12:52 ` Matt Lundin
2011-05-01 13:31 ` Matt Lundin
2011-05-02 6:00 ` Jambunathan K
2011-05-18 23:18 ` [ANN] ELPA Repo for org-html/org-odt Jambunathan K
2011-05-18 23:21 ` Jambunathan K
2011-05-19 4:58 ` suvayu ali
2011-05-19 5:29 ` Jambunathan K
2011-05-19 6:52 ` suvayu ali
2011-05-24 13:41 ` Jambunathan K
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=4D876CC2.3070708@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.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 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).