From: John Hendy <jw.hendy@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Preservation of white space in babel blocks, exporting to PDF
Date: Sat, 1 Feb 2014 19:33:22 -0600 [thread overview]
Message-ID: <CA+M2ft9KZO8sX_Hqp+PKVDTRHcD+u1SEv-bbAAP4NeyrLFpcUw@mail.gmail.com> (raw)
In-Reply-To: <87ob2qr32x.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
On Feb 1, 2014 2:26 PM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
>
> Hello,
>
> John Hendy <jw.hendy@gmail.com> writes:
>
> > On Sat, Feb 1, 2014 at 2:28 AM, Nicolas Goaziou <n.goaziou@gmail.com>
wrote:
>
> >> There is no discrepancy. You indent your code with tabs and these tabs
> >> appear in the TeX file, but Beamer cannot handle them properly. The
same
> >> problem will arise in an example block.
> >
> > From whence comes this assumption? In the previous emails, I mentioned
> > the different treatment between src and example blocks with the same
> > code. I don't know why I'd complain about the .tex containing "some
> > sort of tab character" if I'd put it there myself!
>
> Again, you have `indent-tabs-mode' set to a non-nil value. This is what
> I mean by "you indent your code with tabs".
What do you mean, "again"? Have you mentioned that variable in this
conversation yet? I've not done anything with that variable, as evidenced
by the minimal config I sent. Thus, I take it that the default org setting
is non-nil?
I am a bit frustrated by trying to be as clear as I could about the
situation with reproducible examples, and then finding out the behavior was
apparently obvious, but due to a variable I didn't know existed...
I'll try a fresh pull tomorrow as well as looking at indent-tabs-mode.
John
>
> Babel happens to indent source blocks when re-inserting them after
> evaluation. So you get tabs even if you didn't explicitly write them in
> the first place.
>
>
> Regards,
>
> --
> Nicolas Goaziou
[-- Attachment #2: Type: text/html, Size: 2130 bytes --]
next prev parent reply other threads:[~2014-02-02 1:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 5:58 Preservation of white space in babel blocks, exporting to PDF John Hendy
2014-01-31 8:09 ` Nicolas Goaziou
2014-01-31 22:16 ` John Hendy
2014-01-31 22:25 ` Nicolas Goaziou
2014-01-31 22:46 ` John Hendy
2014-01-31 23:04 ` Nicolas Goaziou
2014-01-31 23:16 ` John Hendy
2014-01-31 23:25 ` Andreas Leha
2014-02-01 4:08 ` John Hendy
2014-02-01 8:28 ` Nicolas Goaziou
2014-02-01 17:54 ` John Hendy
2014-02-01 20:27 ` Nicolas Goaziou
2014-02-01 21:02 ` Nicolas Goaziou
2014-02-02 1:33 ` John Hendy [this message]
2014-02-02 8:45 ` Nicolas Goaziou
2014-02-02 15:59 ` John Hendy
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=CA+M2ft9KZO8sX_Hqp+PKVDTRHcD+u1SEv-bbAAP4NeyrLFpcUw@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).