From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-babel-trangle, proble when loop is interrupted by documentation
Date: Sat, 21 Apr 2018 14:15:57 +0200 [thread overview]
Message-ID: <87efj821s2.fsf@mat.ucm.es> (raw)
In-Reply-To: 87sh7oex61.fsf@nicolasgoaziou.fr
> Hello,
> Uwe Brauer <oub@mat.ucm.es> writes:
> I guess you have to set `org-src-preserve-indentation' globally, or use
> "-i" flag for the block, which is locally equivalent.
Great that does it.
However there is still an empty line generated. Any possibility get rid
of this as well, I look a bit in the org-src.el and could no find
anything.
Regards
next prev parent reply other threads:[~2018-04-21 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 8:32 org-babel-trangle, proble when loop is interrupted by documentation Uwe Brauer
2018-04-21 9:17 ` Nicolas Goaziou
2018-04-21 12:15 ` Uwe Brauer [this message]
2018-04-21 12:20 ` [SOLVED :padline no] (was: org-babel-trangle, proble when loop is interrupted by documentation) Uwe Brauer
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=87efj821s2.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).