From: Antti Kaihola <akaihola@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] [BUG] incorrect indentation when tangling with org-src-preserve-indentation
Date: Sat, 9 Oct 2010 15:22:03 +0300 [thread overview]
Message-ID: <AANLkTim1s_km=Q0i1jgK6U=jx=gaQ-kC0+d7PX3jpUta@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinsu1A7B-JQ6=tcZXHTpsVcWU3DyJV+2w-4VnK0@mail.gmail.com>
The following changes fix the indenting problem for first lines of
source code blocks but introduces extra blank lines:
diff --git a/lisp/ob-python.el b/lisp/ob-python.el
index c172756..27936e8 100644
--- a/lisp/ob-python.el
+++ b/lisp/ob-python.el
@@ -58,3 +58,3 @@
(nth 1 (or processed-params (org-babel-process-params params))) "\n")
- "\n" (org-babel-trim body) "\n"))
+ "\n" body "\n"))
diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el
index a9429c4..ba6387a 100644
--- a/lisp/ob-tangle.el
+++ b/lisp/ob-tangle.el
@@ -365,3 +365,3 @@ form
(insert (format "%s\n" (replace-regexp-in-string
- "^," "" (org-babel-trim body))))
+ "^," "" body)))
(when link-p
2010/10/9 Antti Kaihola <akaihola@gmail.com>:
> As pointed out in the documentation, when tangling Python code, it's
> important to set org-src-preserve-indentation to a non-nil value.
> However, tangling still doesn't seem to work correcly: If the first
> line of a source code block is indented, it ends up dedented to the
> first column in the resulting .py file.
next prev parent reply other threads:[~2010-10-09 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 11:09 [BUG] incorrect indentation when tangling with org-src-preserve-indentation Antti Kaihola
2010-10-09 12:22 ` Antti Kaihola [this message]
2010-10-09 15:36 ` [babel] " Antti Kaihola
2010-10-12 14:54 ` Dan Davison
2010-10-12 16:40 ` Achim Gratz
2010-10-13 5:03 ` Eric Schulte
2010-10-15 7:14 ` Antti Kaihola
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='AANLkTim1s_km=Q0i1jgK6U=jx=gaQ-kC0+d7PX3jpUta@mail.gmail.com' \
--to=akaihola@gmail.com \
--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).