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

Hello,

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

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

Thank you. This bug should be fixed now.

> Are latex macros still allowed?

They are.

As side note, is the provided example, you can also replace
"\label{sec:bug}" with, for example <<sec-bug>> and "\ref{sec:bug}" with
[[sec-bug]] to achieve the same result, with the added benefit of being
able to navigate between the two with `org-open-link'.

> * new exporter
>   \label{sec:bug}
>
>   This section illustrates a simple bug in the new exporter, I think.
>
>   | Section       | Description                |
>   |---------------+----------------------------|
>   | \ref{sec:bug} | An illustration of the bug |
>   |---------------+----------------------------|


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2012-05-03 12:36 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
2012-05-03 12:34         ` Nicolas Goaziou [this message]
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:
  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=87d36lqw93.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@gnu.org \
    --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).