emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Julius Dittmar <Julius.Dittmar@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: preserving (zero-space) indenting in begin_src when exporting/publishing (to mark-down)
Date: Wed, 28 Oct 2020 14:53:34 +0100	[thread overview]
Message-ID: <35d0a538-4841-ec47-48cd-7071afc60726@gmx.de> (raw)
In-Reply-To: <86a6w6fr3l.fsf@login.ifi.uio.no>

Hi Martin,

if I understand correctly, you do not want to have a section that quotes
source code, but literal source code.

As far as I understand, that means using
#+begin_export markdown
block, not
#+begin_src markdown
block. That block will then be ignored in any other export format, and
used as-is in markdown export. (I hope "markdown" is the correct label,
I did not test it.)

Hope that helps,

Am 28.10.20 um 13:54 schrieb Martin Steffen:
> I have troubles to export (or publish) some orgfiles, which contain
> ``src'' snippets intended for markdown. The (for me) unwelcome behavior
> is the same for org-export and org-publish, I guess, since it has the
> same core reason.
> The problem currently for me is for the markdown format. I have seen
> similar behavior for other exports, though did not care since it for
> those situations, it was/is ``good enough''. Now, however, I do some
> export to md, to be used for Jekyll webpages, and it's no longer good
> enough.
> For concreteness sake: I got some section
> #+begin_src markdown
> ---
> layout: default
> title: Some Title
> description: Some information
> ---
> #+end_src
> which is exported to md literally, but with 4 leading spaces as
> indentation, like
>      ---
>      layout: default
>      title: Some Title
>      description: Some information
>      ---
> That's insofar unwelcome, as Jekyll wants those pieces of information
> without indentation.

  reply	other threads:[~2020-10-28 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 12:54 preserving (zero-space) indenting in begin_src when exporting/publishing (to mark-down) Martin Steffen
2020-10-28 13:53 ` Julius Dittmar [this message]
2020-10-28 14:30   ` Martin Steffen

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:

  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=35d0a538-4841-ec47-48cd-7071afc60726@gmx.de \
    --to=julius.dittmar@gmx.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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