From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: James Ryland Miller <james.ryland.miller@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Org not preserving Python indent levels on LaTex export due to tabs
Date: Sun, 16 Feb 2014 11:11:28 +0100 [thread overview]
Message-ID: <8761ofs6y7.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8vzu-NCZ9n1kToceWh7p8-qBjNJ0LPcTaTcO7b0s-EjXw@mail.gmail.com> (Samuel Wales's message of "Thu, 13 Feb 2014 17:32:58 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> i can't seem to find the -i flag in the manual. perhaps i used the
> wrong search term? i looked in literal examples and in working with
> source code. i am using maint.
Indeed. It doesn't appear in the manual.
I don't use it. Maybe Someone using it can provide a patch for it.
> also:
>
> - is there another flag to set org-src-preserve-indentation to nil?
> - will -i still work if org-src.preserve-indentation is t?
No.
> i'd be happy with a fixed 2-space indentation, but that is not
> possible in current org. i find org-src-preserve-indentation to cause
> more issues than it improves, so i am going to transition to it being
> t, which feels safer even though it is not the default and does not
> have the 2 spaces.
FWIW, I'm happy with `org-src-preserve-indentation' set to nil.
Anyway, if you think `org-src-preserve-indentation' needs improvement,
please provide a description (or ECM) of what you expect it to do.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-16 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 23:56 Org not preserving Python indent levels on LaTex export due to tabs James Ryland Miller
2014-02-02 7:49 ` Nicolas Goaziou
2014-02-02 17:32 ` James Ryland Miller
2014-02-02 18:05 ` John Hendy
2014-02-03 13:08 ` Sebastien Vauban
2014-02-03 14:56 ` Bastien
2014-02-14 0:32 ` Samuel Wales
2014-02-16 10:11 ` Nicolas Goaziou [this message]
2014-03-15 6:43 ` Bastien
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=8761ofs6y7.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=james.ryland.miller@gmail.com \
--cc=samologist@gmail.com \
/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).