From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Re: Problems with LaTeX export for $x\text{foo $x$}$-like construts?
Date: Fri, 30 Dec 2022 10:08:29 +0100 [thread overview]
Message-ID: <CAO48Bk9+f1PGuPBGUWwJySFNaZZYDhG0dVbMf=9XkuD4S5OHzA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
> From: Ihor Radchenko <yantar92@posteo.net>
> To: alain.cochard@unistra.fr
> Cc: emacs-orgmode@gnu.org
> Subject: Re: Problems with LaTeX export for $x\text{foo $x$}$-like
> construts?
> Message-ID: <87wn6av84v.fsf@localhost>
> Content-Type: text/plain
>
> Alain.Cochard@unistra.fr writes:
>
> > Version used: release_9.6-149-g554935
> >
> > With an org file containing only
> >
> > #+begin_export latex
> > $x \text{foo $y$}$
> >
> > \(x \text{foo \(y\)}\)
> >
> > $x \text{foo \(y\)}$
> >
> > \(x \text{foo $y$}\)
> > #+end_export
> >
> > the pdf generated upon latex export gives as expected, i.e., with 'x'
> > and 'y' in mathematical font.
>
> This is to be expected because of how Org parser works.
In my experience, this also applies for some situations while creating
listings.
My question is if there would be space for a `:raw t` in the
`#+begin_export latex` to produce a _verbatim_ copy of the contents of the
environment.
All the best, freedom and just(=justa, gerecht) peace in 2023,
/PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 2080 bytes --]
next reply other threads:[~2022-12-30 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 9:08 Pedro Andres Aranda Gutierrez [this message]
2022-12-31 14:23 ` Re: Problems with LaTeX export for $x\text{foo $x$}$-like construts? Ihor Radchenko
2022-12-31 15:10 ` [org-promote-subtree + undo] adds one star Alain.Cochard
2023-01-01 13:44 ` Ihor Radchenko
2023-01-01 14:05 ` Alain.Cochard
2023-01-01 14:13 ` Ihor Radchenko
2023-01-01 15:09 ` Alain.Cochard
2023-01-01 15:56 ` Ihor Radchenko
2023-02-10 11:44 ` Ihor Radchenko
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='CAO48Bk9+f1PGuPBGUWwJySFNaZZYDhG0dVbMf=9XkuD4S5OHzA@mail.gmail.com' \
--to=paaguti@gmail.com \
--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).