emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: latex environment inside math mode problem
Date: Tue, 20 Jan 2015 12:57:36 +0100	[thread overview]
Message-ID: <873875zmtr.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k30hogg4.fsf@gmx.us> (rasmus@gmx.us's message of "Tue, 20 Jan 2015 12:10:51 +0100")

Hello,

Rasmus <rasmus@gmx.us> writes:

> Marko Schütz Schmuck <MarkoSchuetz@web.de> writes:
>
>> the new exporter does not seem to handle \begin/\end inside \( ... \).
>>
>> If the org file contains
>>
>>     \(f =
>>       \begin{cases}
>>       t & 1\\
>>       f & 2\\
>>       \end{cases}
>>     \)
>
> This will also work:
>
> \(f = \begin{cases}
>       t & 1\\
>       f & 2\\
>       \end{cases}\)
>
>
> Technically, I think what happens is that latex-fragments are "objects" in
> the lingo of org-element whereas environments are elements.  If you run
> (org-element-latex-fragment-parser) at "\(f" it is indeed interpret
> correctly as a latex-fragment.  Yet, the nested environment is recognized
> as a latex-environment and it seems the former can't "hold" the latter.
> Why the above work is because a latex-environment starts on its own line
> (cf.  org-element--latex-begin-environment).

That's correct. Elements bind stronger than objects.

> Nicolas will be able to tell if this is a feature or a bug.

This is per Org syntax.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2015-01-20 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 23:29 latex environment inside math mode problem Marko Schütz Schmuck
2015-01-20  1:30 ` Nick Dokos
2015-01-20  3:44   ` Marko Schütz Schmuck
2015-01-20  1:33 ` John Kitchin
2015-01-20  3:34   ` Marko Schütz Schmuck
2015-01-20  8:48     ` Eric S Fraga
2015-01-20 11:51       ` Marko Schütz Schmuck
2015-01-20 11:10 ` Rasmus
2015-01-20 11:57   ` Nicolas Goaziou [this message]

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=873875zmtr.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).