From: David Wooten <david@farwestmillwork.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lilypond
Date: Thu, 12 Jun 2014 13:21:57 -0700 [thread overview]
Message-ID: <28A044DA-FBEA-4FBC-936B-5105A56FBAD2@farwestmillwork.com> (raw)
In-Reply-To: <BA6BFBC3-ED76-40D5-9A22-E9BA7AF3E784@fiee.net>
Right! Got it.
On Jun 12, 2014, at 10:37 AM, Henning Hraban Ramm <texml@fiee.net> wrote:
> Am 2014-06-12 um 23:00 schrieb David Wooten <david@farwestmillwork.com>:
>
>> Both examples (1st page & multipage insertion) place the snippet on its own page, e.g. this gives me a 3 page document w/ snippet on page 2:
>
> The LilyPond settings are essential, otherwise LP produces whole pages, that’s not a problem of ConTeXt.
> Please read and follow the wiki.
>
> Greetlings, Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-06-12 20:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 22:31 Lilypond David Wooten
2014-06-10 9:53 ` Lilypond Henning Hraban Ramm
2014-06-10 18:26 ` Lilypond David Wooten
2014-06-11 8:51 ` Lilypond Henning Hraban Ramm
2014-06-12 17:00 ` Lilypond David Wooten
2014-06-12 17:37 ` Lilypond Henning Hraban Ramm
2014-06-12 20:21 ` David Wooten [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-18 22:32 buffer names in MKII Mojca Miklavec
2011-08-18 21:29 ` Aditya Mahajan
2011-08-19 7:53 ` Henning Hraban Ramm
2011-08-19 15:08 ` Lilypond (Re: buffer names in MKII) Aditya Mahajan
2011-08-19 20:18 ` Lilypond Henning Hraban Ramm
2011-08-20 8:19 ` Lilypond Aditya Mahajan
2011-08-21 1:22 ` Lilypond David Wooten
2011-08-21 12:07 ` Lilypond Henning Hraban Ramm
2011-08-21 18:25 ` Lilypond Henning Hraban Ramm
2011-08-21 22:14 ` Lilypond Aditya Mahajan
2011-08-21 22:24 ` Lilypond Hans Hagen
2011-08-21 22:32 ` Lilypond Aditya Mahajan
2011-08-22 1:53 ` Lilypond Aditya Mahajan
2011-08-22 13:59 ` Lilypond Henning Hraban Ramm
2011-08-22 15:18 ` Lilypond Aditya Mahajan
2007-08-26 22:35 lilypond Hans Hagen
2007-07-03 15:59 lilypond Wolfgang Werners-Lucchini
2007-07-06 20:25 ` lilypond Henning Hraban Ramm
2007-08-27 14:28 ` lilypond Mojca Miklavec
2007-08-27 10:28 ` lilypond Steffen Wolfrum
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28A044DA-FBEA-4FBC-936B-5105A56FBAD2@farwestmillwork.com \
--to=david@farwestmillwork.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).