From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Babel blocks not indented
Date: Fri, 10 May 2013 18:32:11 -0400 [thread overview]
Message-ID: <87d2syo49g.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: CADzxs1=E+et+2oE82pYpGCrDqGo9V2O1exi=9O-1mj2Eykk1Tg@mail.gmail.com
Leo Alekseyev <dnquark@gmail.com> writes:
> I've brought this up before, but I think there's value in SRC blocks
> /not/ being indented, and in fact, I would love it if there were a way
> to make the contents of the SRC blocks / not/ be indented (as opposed
> to the default 2 space offset). Whitespace often matters,
> particularly when working with Python, and every now and then I find
> myself having to manually delete the extra spacing when pasting code
> into the Python interpreter. Other times I want to paste code
> snippets from SRC blocks into source files -- again, indentation gets
> in the way. I agree that it's aesthetically appealing, but my
> workflow would be easier without it.
>
> --Leo
>
Does this help?
,----
| org-edit-src-content-indentation is a variable defined in `org-src.el'.
| Its value is 2
|
| Documentation:
| Indentation for the content of a source code block.
| This should be the number of spaces added to the indentation of the #+begin
| line in order to compute the indentation of the block content after
| editing it with M-x org-edit-src-code. Has no effect if
| `org-src-preserve-indentation' is non-nil.
`----
--
Nick
next prev parent reply other threads:[~2013-05-10 22:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 17:11 Babel blocks not indented Julien Cubizolles
2013-05-07 18:19 ` Eric Schulte
2013-05-07 21:48 ` Julien Cubizolles
2013-05-10 3:32 ` J. David Boyd
2013-05-10 21:07 ` Leo Alekseyev
2013-05-10 22:32 ` Nick Dokos [this message]
2013-05-13 9:31 ` Leo Alekseyev
2013-05-13 9:53 ` Andreas Röhler
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=87d2syo49g.fsf@pierrot.dokosmarshall.org \
--to=ndokos@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).