From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Vicente Vera <vicentemvp@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Exporting blocks of text completely verbatim
Date: Thu, 9 Feb 2017 15:27:53 +0100 [thread overview]
Message-ID: <CAJ51ETquYH8gu0pdjRx2ycdwAgNmRFwYZB7m90vy75_WoNiH+w@mail.gmail.com> (raw)
In-Reply-To: <CAMfbzvC68fw0V-5LLfNzepiFV7UYJ_s5vLkbp3GbKtk+1+eWtQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
Isn't
#+BEGIN_EXAMPLE
Long block
#+END_EXAMPLE
what you want?
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Thu, Feb 9, 2017 at 3:11 PM, Vicente Vera <vicentemvp@gmail.com> wrote:
> Hello. This discussion
> https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00163.html
> points out that Org tables are converted to HTML tables when exporting
> through "ox-md". Leaving Markdown-related issues aside, I've stumbled
> upon this problem a while back.
>
> It is suggested that wrapping the table within a "#+(BEGIN|END)_EXPORT
> md" should leave it as-is in the exported document but that is not the
> case. The table gets converted to HTML anyway.
>
> When skimming through the Org manual I found that
> "#+(BEGIN|END)_EXPORT back-end" blocks are used to export text *only*
> for the specified back-end. This appears in the ASCII back-end
> documentation (does it work like this for others back-ends?).
>
> In a general level, is there a way to keep blocks of text completely
> unmodified (without indentation also) on export?
>
>
[-- Attachment #2: Type: text/html, Size: 2061 bytes --]
next prev parent reply other threads:[~2017-02-09 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 14:11 Exporting blocks of text completely verbatim Vicente Vera
2017-02-09 14:27 ` John Kitchin [this message]
2017-02-09 16:27 ` Vicente Vera
2017-02-09 19:19 ` Charles C. Berry
2017-02-09 23:16 ` Vicente Vera
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=CAJ51ETquYH8gu0pdjRx2ycdwAgNmRFwYZB7m90vy75_WoNiH+w@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=vicentemvp@gmail.com \
/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).