From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: David Dynerman <emperordali@block-party.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: buffer local org-src-preserve-indentation not respected
Date: Sat, 03 Dec 2016 23:58:54 +0100 [thread overview]
Message-ID: <87shq4bowh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2mvgedmcb.fsf@block-party.net> (David Dynerman's message of "Fri, 02 Dec 2016 13:59:00 -0800")
Hello,
David Dynerman <emperordali@block-party.net> writes:
> I'd like to report a bug. It seems that setting
> org-src-preserve-indentation to true doesn't work if it's set buffer
> local.
>
> To reproduce, save the following as an org file:
>
> #+BEGIN_SRC python :tangle preserve-indent.py
> class Foo:
> bar = 5
> #+END_SRC
>
>
> Here is some interstitial text!
>
> #+BEGIN_SRC python :tangle preserve-indent.py
> def __init__(self):
> self.bar = 7
> #+END_SRC
>
> Then:
>
> 1) (setq org-src-preserve-indentation nil) and tangle the file. Open
> preserve-indent.py and note that def __init__ has no leading whitespace,
> which means python will not recognize it as a member of Foo
>
> 2) (setq org-src-preserve-indentation t) and tangle the file. Open
> preserve-indent.py and note that now def __init__ is properly
> indented. This is the expected behavior.
>
> 3) (setq org-src-perserve-indentation nil), then M-x
> make-variable-buffer-local and set org-src-preserve-indentation to
> t. Tangle the file and open preserve-indent.py. Note that def __init__
> is back to being not-indented. The expected behavior is that the
> indentation would be respected, as in #2.
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-12-03 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 21:59 buffer local org-src-preserve-indentation not respected David Dynerman
2016-12-03 22:58 ` Nicolas Goaziou [this message]
2016-12-07 23:58 ` David Dynerman
2016-12-09 23:22 ` Nicolas Goaziou
2016-12-11 18:37 ` David Dynerman
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=87shq4bowh.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=emperordali@block-party.net \
/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).