From: Martyn Jago <martyn.jago@btinternet.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-lilypond
Date: Sat, 2 Jul 2011 14:04:52 +0100 [thread overview]
Message-ID: <4049C1C7-EA7C-44C7-87F7-80B9A512A7A1@btinternet.com> (raw)
In-Reply-To: <87vcvllpxh.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Hi
On 1 Jul 2011, at 20:27, Eric Schulte wrote:
>>>
> I can't reproduce this problem, for example the following works for me
> on the latest version of Org-mode. I think perhaps you may not be on
> the latest git HEAD.
>
> Thanks again for this great contribution -- Eric
>
> ** define a block with a name for noweb expansion
> :PROPERTIES:
> :tangle: yes
> :noweb: yes
> :END:
>
> #+source: simple(something="something")
> #+begin_src emacs-lisp
> something
> #+end_src
>
> another block including the first block
> #+begin_src emacs-lisp
> <<simple(something="something else")>>
> #+end_src
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte/
OK - It appears I was getting the differing results since I wasn't
passing in default parameters to my ruby blocks being called by
noweb...
was...
#+srcname: gen_arpeggio(key,root)
now...
#+srcname: gen_arpeggio(key="c",root="c")
Regards
Martyn
[-- Attachment #2: Type: text/html, Size: 1708 bytes --]
next prev parent reply other threads:[~2011-07-02 13:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:00 ob-lilypond Martyn Jago
2011-06-27 18:53 ` ob-lilypond Eric Schulte
2011-06-28 9:38 ` ob-lilypond Martyn Jago
2011-06-28 10:07 ` ob-lilypond Bastien
2011-06-28 10:21 ` ob-lilypond Bastien
2011-06-28 20:45 ` ob-lilypond Eric Schulte
2011-06-28 23:07 ` ob-lilypond Bastien
2011-06-29 0:41 ` ob-lilypond Eric Schulte
2011-06-29 17:07 ` ob-lilypond Martyn Jago
2011-06-29 21:15 ` ob-lilypond Eric Schulte
2011-06-30 6:38 ` ob-lilypond Martyn Jago
2011-06-30 18:10 ` ob-lilypond Eric Schulte
2011-07-01 12:01 ` ob-lilypond Christian Moe
2011-07-06 8:13 ` [BABEL][PATCH] ob-lilypond basic mode - was ob-lilypond Martyn Jago
2011-07-06 13:20 ` Eric Schulte
2011-07-01 13:43 ` ob-lilypond Martyn Jago
2011-07-01 19:27 ` ob-lilypond Eric Schulte
2011-07-02 13:04 ` Martyn Jago [this message]
2011-06-28 13:38 ` ob-lilypond Cameron Horsburgh
2011-06-28 16:46 ` ob-lilypond Martyn Jago
2011-06-28 12:11 ` ob-lilypond Christian Moe
2011-06-28 13:18 ` ob-lilypond David O'Toole
2011-06-28 17:06 ` ob-lilypond Martyn Jago
2011-06-28 18:51 ` ob-lilypond Christian Moe
2011-06-28 19:00 ` ob-lilypond Michael Brand
2011-06-28 20:00 ` ob-lilypond Christian Moe
2011-06-28 21:19 ` ob-lilypond Martyn Jago
-- strict thread matches above, loose matches on Subject: below --
2015-03-25 12:49 ob-lilypond pls
2015-03-26 9:20 ` ob-lilypond pls
2015-03-29 21:27 ` ob-lilypond Nick Dokos
2015-03-30 9:20 ` ob-lilypond Patrick L. Schmidt
2015-03-26 9:26 ob-lilypond Patrick L. Schmidt
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=4049C1C7-EA7C-44C7-87F7-80B9A512A7A1@btinternet.com \
--to=martyn.jago@btinternet.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).