ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Lilypond (Re:  buffer names in MKII)
Date: Fri, 19 Aug 2011 11:08:28 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1108191102060.14039@nqv-gnoyrg.tngrjnl.2jver.arg> (raw)
In-Reply-To: <53762C1C-F3B2-4627-8A45-0EAB68CBDC73@fiee.net>

Hi Hraban

On Fri, 19 Aug 2011, Henning Hraban Ramm wrote:

> Am 2011-08-18 um 23:29 schrieb Aditya Mahajan:
>
>> I am also thinking of providing an interface for parsing the buffer content 
>> at lua end. That will allow us to implement all the features of the gnuplot 
>> and lilypond module using the filter module. But I need some testers, as I 
>> don't use either of the programs.
>
> I don't understand what you're planning,

I am planning to add features so that you can say:

\startlilypondpreamble
   global settings
\stoplilypondpreamble

\startlilypond
the score
\stoplilypond

and get a correct output (this is more or less possible right now).

The other thing is to be able to change linespace, papersize, offset, etc 
using parameters, so that one can say:

\startlilypond[linespace=...]
  ...
\stoplilypond

This will require some lua side processing.

> but I'll do the testing for LilyPond.

Do you know how lilypond numbers its output files. In some cases I get 
filename-1.pdf sometimes not. Can I force it to always give filename-1.pdf 
or always give filename.pdf

Which OSes do you have access to?

Thanks,
Aditya
___________________________________________________________________________________
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-19 15:08 UTC|newest]

Thread overview: 17+ 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     ` Aditya Mahajan [this message]
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
2011-08-19  0:09 ` buffer names in MKII Aditya Mahajan
2011-08-19  7:53 ` Hans Hagen

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=alpine.LNX.2.02.1108191102060.14039@nqv-gnoyrg.tngrjnl.2jver.arg \
    --to=adityam@umich.edu \
    --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).