emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: emacs-orgmode@gnu.org
Subject: [babel] noweb syntax
Date: Sat, 31 Oct 2009 08:15:37 -1000	[thread overview]
Message-ID: <28BF59BE-7FF8-4DFB-BD6E-A224D9A133BA@tsdye.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]

Aloha all,

The new expanded noweb syntax in org-babel is sensitive to line  
breaks.  It looks to me as if it isn't possible to expand two noweb  
references on the same line.  As the following example shows, there is  
a workaround that yields valid LaTeX source.   Insensitivity to line  
breaks seems more intuitive to me, but I can live with the workaround  
if this is a feature and not a bug.

--------------------------- org file ---------------------------------
* test

#+begin_src latex :tangle gobble
   This is tangled <<a()>>, and not this <<b()>>, but so this is.
   This is tangled <<a()>>,
   and so is this <<b()>>.
#+end_src

** Python code

#+srcname: a
#+begin_src python
1
#+end_src

#+resname: a
: 1

#+srcname: b
#+begin_src python
2
#+end_src

#+resname: b
: 2

-------------------------- gobble.tex ---------------------------

% generated by org-babel-tangle

% [[file:~/Public/projects/903_adzes/org-babel/test-babel.org::*test] 
[block-1]]
This is tangled 1, but so this is.
This is tangled 1,
and so is this 2.
% block-1 ends here

All the best,
Tom

Thomas S. Dye, Ph.D.
T. S. Dye & Colleagues, Archaeologists, Inc.
Phone: (808) 529-0866 Fax: (808) 529-0884
http://www.tsdye.com



[-- Attachment #1.2: Type: text/html, Size: 4150 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
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-10-31 18:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=28BF59BE-7FF8-4DFB-BD6E-A224D9A133BA@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    /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).