From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [BUG] in last org in indentation of source blocks Date: Thu, 28 May 2015 08:15:29 -1000 Message-ID: References: <87oal4y6ri.fsf@posteo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33985) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yy2LU-0000du-03 for emacs-orgmode@gnu.org; Thu, 28 May 2015 14:15:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yy2LO-0002fL-Vb for emacs-orgmode@gnu.org; Thu, 28 May 2015 14:15:55 -0400 Received: from gproxy6-pub.mail.unifiedlayer.com ([67.222.39.168]:53775) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1Yy2LO-0002ag-OB for emacs-orgmode@gnu.org; Thu, 28 May 2015 14:15:50 -0400 In-Reply-To: <87oal4y6ri.fsf@posteo.de> (Titus von der Malsburg's message of "Thu, 28 May 2015 10:02:57 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Titus von der Malsburg Cc: emacs-orgmode@gnu.org Titus von der Malsburg writes: > I can=E2=80=99t reproduce the second indent but I think it=E2=80=99s a bu= g that there is > any indentation at all. > > The documentation of `org-edit-special' (C-x ') says: > > Call a special editor for the element at point. =E2=80=A6 > > No mention of indentation or other reformatting of my code. > > The same goes for `org-edit-src-exit' (C-c C-c) which says: > > Kill current sub-editing buffer and return to source buffer. > > The edit-in-buffer feature should not touch the indentation. If the > syntax of the language is sensitive to indentation (e.g. Python) this > can break the code. Example: > > #+BEGIN_SRC python :results output > print "test" > #+END_SRC > > is invalid Python syntax. > > Also having one function perform two very different actions (edit code > in separate buffer *and* reformat the code) is poor design. At least in > this special case. When I open the code in a separate buffer but then > decide not to change it (C-c C-c), I'll end up with extra indentation > and this will create unnecessary changes when I commit the file in git. Does the variable org-src-preserve-indentation get the behavior you're after? hth, Tom --=20 Thomas S. Dye http://www.tsdye.com