emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: on the fragility of export to ODT
Date: Tue, 17 Feb 2015 22:04:45 +0100	[thread overview]
Message-ID: <87lhjwuu4y.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87a90c9zsg.fsf@delle7240.chemeng.ucl.ac.uk> (Eric S. Fraga's message of "Tue, 17 Feb 2015 18:08:15 +0000")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I have many internal references; in this document, all are to named
> tables and figures.

The error comes from a figure, not a table, if that helps.

> I have tried but haven't managed to track down which one is causing
> problems in this case.
>
> I have tried extracting various bits into smaller org files but then the
> problems disappear... :(
>
> Part of the problem, I think (but please correct me if I'm wrong), is
> that the positions indicated in the error messages are in the buffer
> being exported after a certain amount of processing (including, I would
> imagine, babel) and so it's difficult to find the actual location of the
> problem.
>
> If this is indeed the case, is there any way to retain the buffer that
> is being processed at the point the error occurs?

You're right, buffer positions mean nothing here.

However, there's a simpler solution. In- "ox-odt.el", function
`org-odt-link--infer-description', line 2655 (but it depends on Org
version), there is

  (t (error "FIXME: Resolve %s" destination))

Replace it with

  (t (error "FIXME: Resolve %s" (org-element-interpret-data destination))))

reload Org then trigger the error. The backtrace should be more interesting.


Regards,

  reply	other threads:[~2015-02-17 21:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:29 on the fragility of export to ODT Eric S Fraga
2015-02-16 20:20 ` Nicolas Goaziou
2015-02-17 18:08   ` Eric S Fraga
2015-02-17 21:04     ` Nicolas Goaziou [this message]
2015-02-18  9:56       ` Eric S Fraga
2015-02-18 13:55         ` Nicolas Goaziou
2015-02-18 15:04           ` 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:
  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=87lhjwuu4y.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.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).