From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Denis Bitouzé" <dbitouze@wanadoo.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: LaTeX source code blocks not exported in Markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)]
Date: Fri, 11 Sep 2015 17:58:18 +0200 [thread overview]
Message-ID: <87twr1uew5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m3pp1prsbx.fsf@drums.chezmoi.fr> ("Denis \=\?utf-8\?Q\?Bitouz\?\= \=\?utf-8\?Q\?\=C3\=A9\=22's\?\= message of "Fri, 11 Sep 2015 15:36:18 +0200")
Hello,
dbitouze@wanadoo.fr (Denis Bitouzé) writes:
> When exported to Mardown, the following org mode file:
>
[...]
> * \LaTeX code
> #+BEGIN_SRC latex
> latex
> #+END_SRC
>
> (Huh: nothing?)
>
> gives:
>
> ┌────
> │ <div id="table-of-contents">
> │ [...]
> │ </div>
> │
> │ # Lisp code<a id="orgheadline1"></a>
> │
> │ (some-code)
> │
> │ # Foo code<a id="orgheadline2"></a>
> │
> │ Foo
> │
> │ # \LaTeX code<a id="orgheadline3"></a>
> │
> │ (Huh: nothing?)
> └────
>
> Expected behavior:
>
> ┌────
> │ #+BEGIN_SRC latex
> │ latex
> │ #+END_SRC
> └────
>
> gives:
>
> ┌────
> │ latex
> └────
This is because latex block can be evaluated, which gives:
#+RESULTS:
#+BEGIN_LaTeX
latex
#+END_LaTeX
i.e., the generated results appear only when using latex export backend.
The original block is removed thereafter. You can use instead:
#+BEGIN_SRC latex :exports code
latex
#+END_SRC
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-09-11 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:36 Bug: LaTeX source code blocks not exported in Markdown [8.3.1 (8.3.1-103-g366dc4-elpa @ /home/bitouze/.emacs.d/elpa/org-20150907/)] Denis Bitouzé
2015-09-11 15:58 ` Nicolas Goaziou [this message]
[not found] ` <87twr1uew5.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-12 6:17 ` Denis Bitouzé
2015-09-11 16:10 ` Charles C. Berry
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=87twr1uew5.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=dbitouze@wanadoo.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).