emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Fraga <e.fraga@ucl.ac.uk>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: [bug] new exporter fails on read only files
Date: Thu, 3 May 2012 19:07:40 +0930	[thread overview]
Message-ID: <87ehr1ip0b.fsf@ucl.ac.uk> (raw)
In-Reply-To: <8762ckdi4h.fsf@gmail.com> (Nicolas Goaziou's message of "Fri, 27 Apr 2012 22:39:26 +0200")

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> Eric Fraga <e.fraga@ucl.ac.uk> writes:
>> Actually, I have updated (one minute ago) and the problem has now
>> changed!  I now get this error:
>> ,----
>> | and: Wrong type argument: stringp, (latex-fragment (:value "\\ref{sec:evaporative}" :begin 11957 :end 11978 :post-blank 0))
>> `----
> This is a bit short to start investigations. Something is happening at
> position 11957 in your buffer. You may want to narrow it to the
> paragraph/table/construct around and try to export it again. It could
> make a minimal example.

Okay, I have investigated.  Attached is a simple example which
illustrates the problem which appears to be use of a latex macro within
a table.  Are latex macros still allowed?  I have used emacs -Q and
loaded in the new export etc.  No customisations.

The error message for this example is:

| and: Wrong type argument: stringp, (latex-fragment (:value "\\ref{sec:bug}" :begin 322 :end 335 :post-blank 0))

> You may also try (org-element-parse-buffer) to see if the error comes
> from the parser or the export engine. You could even try to export to

It's the export engine and it's due to my \ref{...} having the \
escaped, which should not happen.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: examplebug.org --]
[-- Type: text/org, Size: 476 bytes --]

#+TITLE:     examplebug.org
#+AUTHOR:    Eric S Fraga
#+EMAIL:     e.fraga@ucl.ac.uk
#+DATE:      2012-01-09 Mon

* new exporter

  This section illustrates a simple bug in the new exporter, I think.

  | Section       | Description                |
  | \ref{sec:bug} | An illustration of the bug |

  The table has a reference using a direct latex command.

[-- Attachment #3: Type: text/plain, Size: 106 bytes --]

: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs
: using Org release_7.8.09-414-gb3e8a8

  reply	other threads:[~2012-05-03  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 12:36 [bug] new exporter fails on read only files Eric Fraga
2012-04-26 12:59 ` Bastien
2012-04-27 13:22   ` Eric Fraga
2012-04-27 14:50     ` Bastien
2012-04-27 20:39     ` Nicolas Goaziou
2012-05-03  9:37       ` Eric Fraga [this message]
2012-05-03 12:34         ` Nicolas Goaziou
2012-05-06 13:55           ` Eric Fraga
2012-05-06 18:13             ` Nicolas Goaziou
2012-05-06 23:48               ` Eric S Fraga

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:

  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=87ehr1ip0b.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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