ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lilypond
Date: Mon, 22 Aug 2011 15:59:46 +0200	[thread overview]
Message-ID: <D318CD9A-3E46-425D-BB4A-17ACDCA25E0E@fiee.net> (raw)
In-Reply-To: <alpine.LNX.2.02.1108212114400.2153@nqv-gnoyrg.tngrjnl.2jver.arg>

Am 2011-08-22 um 03:53 schrieb Aditya Mahajan:
> @Hraban: Long story short, the filter module is working again. Can  
> you test the dev branch from the latest git version?

Thank you!
LilyPond ist called, but your approach of including the LaTeX file  
fails, since you don’t define \linebreak from:

"""
\includegraphics{test1-temp-lilypond-0-1}%
\ifx\betweenLilyPondSystem \undefined
   \linebreak
\else
   \expandafter\betweenLilyPondSystem{1}%
\fi
"""

In my test case (where I include the "one system per file" patch) I  
can \def\linebreak{\relax} and get a nice multi-page score.

Greetlings from Lake Constance!
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
___________________________________________________________________________________


  reply	other threads:[~2011-08-22 13:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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                 ` Henning Hraban Ramm [this message]
2011-08-22 15:18                   ` Lilypond Aditya Mahajan
2011-08-19  0:09 ` buffer names in MKII Aditya Mahajan
2011-08-19  7:53 ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
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           ` Lilypond David Wooten
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=D318CD9A-3E46-425D-BB4A-17ACDCA25E0E@fiee.net \
    --to=hraban@fiee.net \
    --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).