emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Denis Bitouzé" <dbitouze-39ZsbGIQGT5GWvitb5QawA@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.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: Sat, 12 Sep 2015 08:17:20 +0200	[thread overview]
Message-ID: <m3h9n0noun.fsf@example.com> (raw)
In-Reply-To: <87twr1uew5.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> (Nicolas Goaziou's message of "Fri, 11 Sep 2015 17:58:18 +0200")

Le 11/09/15 à 17h58, Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> a écrit :

> Hello,

Hi Nicolas and Charles,

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

Ooops, sorry for the noise due to this misuse.

Regards.
-- 
Denis

  parent reply	other threads:[~2015-09-12  6:17 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
     [not found]   ` <87twr1uew5.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2015-09-12  6:17     ` Denis Bitouzé [this message]
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=m3h9n0noun.fsf@example.com \
    --to=dbitouze-39zsbgiqgt5gwvitb5qawa@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).