From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Lilypond
Date: Sun, 21 Aug 2011 18:14:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1108211754440.2153@nqv-gnoyrg.tngrjnl.2jver.arg> (raw)
In-Reply-To: <4822756A-A54B-4C4F-968A-9AEFB75B1F16@fiee.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 837 bytes --]
On Sun, 21 Aug 2011, Henning Hraban Ramm wrote:
> Current version doesn’t work at all:
> - it writes the buffer with doubled filename and extension parts, i.e. from
> foo.tex "foo-foo-temp-lilypond.tmp.tmp", but looks for
> "foo-temp-lilypond.tmp".
The \savebuffer command has changed!!!
\starttext
\startbuffer[abc]
test
\stopbuffer
\savebuffer[abc][name.ext]
\stoptext
now creates a file \jobname-name.ext, rather than name.ext.
I'll provide a work around.
> - even if I rename the buffer file, LilyPond isn’t run.
>
> t-filter > current filter : lilypond
> t-filter > base file : test1-temp-lilypond
> t-filter > input file : test1-temp-lilypond.tmp
> t-filter > output file :
> t-filter > command :
With the latest version, I also get this. Strange.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2011-08-21 22:14 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 ` Aditya Mahajan [this message]
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
-- 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=alpine.LNX.2.02.1108211754440.2153@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).