emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Davison <davison@stats.ox.ac.uk>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] noweb expansion in latex source blocks
Date: Sun, 01 Nov 2009 14:47:55 -0500	[thread overview]
Message-ID: <878weq2fis.fsf@stats.ox.ac.uk> (raw)
In-Reply-To: <3BDDF8C0-6091-4911-A3E5-B924FE9062B0@TSDYE.Com> (Thomas S. Dye's message of "Sat, 31 Oct 2009 18:09:07 -1000")

"Thomas S. Dye" <tsd@tsdye.com> writes:

> Aloha all,
>
> Noweb expansion in latex source blocks inserts spaces that can
> introduce unwanted paragraph breaks in LaTeX.

Hi Tom,

I've just fixed this issue and the other one you posted, regarding
multiple references on a line. The changes will be in org-mode git
within the next few hours.

Thanks for reporting these problems.

Dan

>
> The outer-block in this org file looks like something that should be
> set as one paragraph in LaTeX.
>
> * noweb expansion
>
> #+srcname: outer-block
> #+begin_src latex :tangle noweb_exp.tex
> This is an observation.
> <<inner-block>>
> This is a conclusion.
> #+end_src
>
> #+srcname: inner-block
> #+begin_src latex
> This is an analysis.
> #+end_src
>
> But it tangles a LaTeX snippet with three paragraphs.
>
> % generated by org-babel-tangle
>
> % [[file:~/Public/projects/903_adzes/org-babel/noweb-
> expansion.org::*noweb%20expansion][outer-block]]
> This is an observation.
>
> This is an analysis.
>
> This is a conclusion.
> % outer-block ends here
>
> All the best,
> Tom
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-11-01 19:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01  4:09 [babel] noweb expansion in latex source blocks Thomas S. Dye
2009-11-01 19:47 ` Dan Davison [this message]
2009-11-01 21:27   ` Thomas S. Dye
2009-11-01 21:43     ` Eric Schulte

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=878weq2fis.fsf@stats.ox.ac.uk \
    --to=davison@stats.ox.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).