emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Christian Moe <mail@christianmoe.com>
To: Bastien <bzg@altern.org>
Cc: 12718@debbugs.gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: bug#12718:  bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument
Date: Wed, 24 Oct 2012 15:48:21 +0200	[thread overview]
Message-ID: <5087F1A5.2090707__33273.3661206023$1351094792$gmane$org@christianmoe.com> (raw)
In-Reply-To: <87a9vc3shw.fsf@bzg.ath.cx>

Hi, Bastien,

Apologies. I was the original poster of this bug report, and I had to 
correct it later: The problem is not that ODT export fails, but that 
ODT export-and-open fails to locate the exported file.

Please see if you can reproduce it with a capital O in the export command:

C-c C-e O

One other user already reported reproducing it, and I still get it with

emacs -Q

running Org 7.9.2 on Emacs 24.1.1.

Yours,
Christian

On 10/24/12 3:32 PM, Bastien wrote:
> Hi Jambunathan,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> When I try to export to ODT (without invoking the new exporter or
>> anything), I get:
>>
>> OpenDocument export failed: Wrong type argument: stringp,
>> (org-export-odt-preprocess-latex-fragments)
>
> I cannot reproduce this with current Emacs trunk and
>
> emacs -Q
> C-x C-f test.org RET
> [some simple org file]
> C-c C-e o
>
> How can I reproduce the problem above?
>
> Thanks,
>

next prev parent reply	other threads:[~2012-10-24 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877gqgs5me.fsf@gmail.com>
2012-10-24 13:32 ` bug#12718: 24.2.50; ODT export (old) fails with wrong-type-argument Bastien
2012-10-24 13:48   ` Christian Moe [this message]
     [not found] ` <87a9vc3shw.fsf__4156.39701900563$1351085626$gmane$org@bzg.ath.cx>
2012-10-24 13:46   ` Jambunathan K
     [not found]   ` <87sj94oudk.fsf@gmail.com>
2012-10-24 13:57     ` Bastien

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='5087F1A5.2090707__33273.3661206023$1351094792$gmane$org@christianmoe.com' \
    --to=mail@christianmoe.com \
    --cc=12718@debbugs.gnu.org \
    --cc=bzg@altern.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

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).