maxosx support for 10.4 to 10.7, test binaries
There are darwin-ppc and darwin-x86 binaries here: http://lilypond.org/~graham/ There is one report that the x86 version fails to work on 10.5.8, which seems odd since I would have expected more complaints if that was the case. If you have a mac, could you check those binaries? Make sure you download the right version for your architecture. There's some comments here: http://code.google.com/p/lilypond/issues/detail?id=1919 Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Jazz Chord Symbols
Look for the pop-chords.ly file which has a lot of these modifications already. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Jazz Chord Symbols
Hi, This may be a FAQ but I can't find definitive answers by googling. I'm looking for more control over chord symbols. For the most part - what I'm looking for is something close to what we see in the Real Book. But that's actually in handwriting, so some changes would obviously be wanted or needed for a LilyPond-engraved output. The thing is - With LilyPond we seem to have the Ignatzek and alternate chord styles. These are both pretty far off from what I'm used to. Is there a way to create a new "set" of symbols for rendering chords? In particular, I have these requirements: o 6th, 7th, 9th, etc. chords would have the "7" at the same font size as the Chord letter. e.g. "C7" should not have the 7 in superscript. o Minor would use `-' instead of `m'. o Major 7th would look like "Gma7" - no superscript. o Extra Tensions on a chord would be added as superscipt. e.g. - "Fma7#11" would have the "#11" in superscript. - "C7b5" would have the \flat 5 in superscript. - "A-7b5" would have the \flat 5 in superscript. - However "B9" and "E-11" should have NO superscript. o Multiple tensions would be stacked in a column to the right. - C7#9/b9/b13 would have the 3 tensions stacked, next to the 7 in the small superscript-size text. - A7sus2/sus4 would have those suspensions stacked. o Inverted chords, e.g. "A/C#" would be written as shown here, but the bottom of the "A" would be close to the top of the "C". So they aren't exactly in-line. The intent is to try and mimic the way these are typically written. o Polychords e.g. "G over F" would be written with a horizontal bar between both letters. And there's probably a lot more... Any help or direction towards this end would be great. Thanks, Louis ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: placement sostenuto
On Sun, Sep 25, 2011 at 6:24 PM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
> Hi David,
>
> thanks a lot!
>
You're welcome!
>
> I added ls as an argument to the definition to get the possibility to
> access different alists in polyphonic situations:
>
Good idea.
One thought I had is that someone using this might want to be able to
override all the settings without specifying a list of articulations. So in
that case you could use this:
\version "2.14.2"
#(define ls-1 '(
("staccato" . ((color . (0 1 0))(padding . 0.5)))
("accent" . ((font-size . 4)(color . (1 0 0
("tenuto" . ((rotation . (45 0 0)) (padding . 2)(font-size . 10)))
("staccatissimo" . ((padding . -10) (color . (0 0 1
))
#(define ls-2 '(
("staccato" . ((color . (0 1 0
("accent" . ((font-size . 4)(color . (0 1 0))(padding . 1.5)))
("tenuto" . ((rotation . (-45 0 0)) (padding . 2)(font-size . 10)))
("staccatissimo" . ((padding . -10) (color . (0 0 1
("coda" . ((color . (0 0 1
))
#(define ((custom-script-tweaks ls) grob)
(let* ((type (ly:prob-property (assoc-ref (ly:grob-properties grob)
'cause) 'articulation-type))
(tweaks (assoc-ref ls type)))
(if tweaks
(for-each (lambda (x) (ly:grob-set-property! grob (car x) (cdr x)))
tweaks)
'(
one =
\relative c'' {
f1--
f1--
\override Voice.Script #'before-line-breaking = #(custom-script-tweaks
ls-1)
f-. f-| f-> f-> f-- f-|
\revert Script #'before-line-breaking
f-> f-.
}
two =
\relative c' {
f1--->
f1--
\override Voice.Script #'before-line-breaking = #(custom-script-tweaks
ls-2)
f-. f-| f-> f-> f---> f-|
%\revert Script #'before-line-breaking
f-> f-.\coda
}
\new Staff <<
\new Voice { \voiceOne \one }
\new Voice { \voiceTwo \two }
>>
Best,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: placement sostenuto
Hi David,
2011/9/25 David Nalesnik
>
> You could change the function to map ly:grob-set-property! onto the alist
> if a match is found:
>
> \version "2.14.2"
>
> #(define ls '(
> ("staccato" . ((color . (0 1 0
> ("accent" . ((font-size . 4)(color . (1 0 0
> ("tenuto" . ((rotation . (45 0 0)) (padding . 2)))
> ("staccatissimo" . ((padding . -10) (color . (0 0 1
> ))
>
> #(define ((custom-script-tweaks type) grob)
>(map
> (lambda (arg)
>(let ((lst (assoc-ref ls arg)))
> (if (equal? arg (ly:prob-property (assoc-ref (ly:grob-properties
> grob) 'cause) 'articulation-type))
> (for-each (lambda (x) (ly:grob-set-property! grob (car x) (cdr
> x))) lst)
> '(
> type))
>
>
> \relative c'' {
> f1--
> f1--
> \override Script #'before-line-breaking =
> #(custom-script-tweaks '("staccato" "tenuto" "accent"
> "staccatissimo"))
>
> f-. f-| f-> f-> f-- f-|
>
> \revert Script #'before-line-breaking
> f-> f-.
> }
>
thanks a lot!
I added ls as an argument to the definition to get the possibility to access
different alists in polyphonic situations:
\version "2.14.2"
#(define ls-1 '(
("staccato" . ((color . (0 1 0))(padding . 0.5)))
("accent" . ((font-size . 4)(color . (1 0 0
("tenuto" . ((rotation . (45 0 0)) (padding . 2)(font-size . 10)))
("staccatissimo" . ((padding . -10) (color . (0 0 1
))
#(define ls-2 '(
("staccato" . ((color . (0 1 0
("accent" . ((font-size . 4)(color . (0 1 0))(padding . 1.5)))
("tenuto" . ((rotation . (-45 0 0)) (padding . 2)(font-size . 10)))
("staccatissimo" . ((padding . -10) (color . (0 0 1
("coda" . ((color . (0 0 1
))
#(define ((custom-script-tweaks type ls) grob)
(map
(lambda (arg)
(let ((lst (assoc-ref ls arg)))
(if (equal? arg (ly:prob-property (assoc-ref (ly:grob-properties
grob) 'cause) 'articulation-type))
(for-each (lambda (x) (ly:grob-set-property! grob (car x) (cdr
x))) lst)
'(
type))
one =
\relative c'' {
f1--
f1--
\override Voice.Script #'before-line-breaking =
#(custom-script-tweaks '("staccato" "tenuto" "accent" "staccatissimo")
ls-1)
f-. f-| f-> f-> f-- f-|
\revert Script #'before-line-breaking
f-> f-.
}
two =
\relative c' {
f1--->
f1--
\override Voice.Script #'before-line-breaking =
#(custom-script-tweaks '("staccato" "tenuto" "accent" "staccatissimo"
"coda") ls-2)
f-. f-| f-> f-> f---> f-|
%\revert Script #'before-line-breaking
f-> f-.\coda
}
\new Staff <<
\new Voice { \voiceOne \one }
\new Voice { \voiceTwo \two }
>>
Thanks,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: High-level users?
MuseScore seems to work for simple scores. For the sort of things I do it doesn't work yet anyway. But I belive would be good to have a free and robust alternative to finale and on top of that integrated with lilypond. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Beaming (was Re: Adding an 8 bellow the treble clef)
W dniu 25 września 2011 23:33 użytkownik Carl Sorensen napisał: > > On 9/25/11 2:48 PM, "Janek Warchoł" wrote: >> Our beaming really needs some improvements. > > Please post the problems you are aware of, Sure, i'm working on the report for some time now (it's a thorough report, just like my ties report - which is work-in-progress too). Would you like to see it now or when it's finished? > and I'll give you whatever > estimate I can about how hard they will be to fix. I guess they will be very hard to fix properly... But i hope to be wrong :) thanks, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: High-level users?
2011/9/25 Hilary Snaden : > On 2011-09-25 11:13, Janek Warchoł wrote: >> >> 2011/9/24 Graham Percival: >>> >>> On Sat, Sep 24, 2011 at 03:24:18PM +0200, Janek Warchoł wrote: For what it's worth, i really *really* think that LilyPond and MuseScore should be integrated. >>> >>> What does that mean? >>> >>> - better lilypond export for musescore: go ahead and send patches >>> there. >>> - lilypond import for musescore: go ahead and send patches there. >> >> No, i mean *a lot* more. Therefore it's too big for me to handle >> alone - that's why i'm aksing who's interested in it. There'd be no >> point in writing my thoughts on this topic down and sending them to >> the list if noone would be interested. > > The last time I tried Musescore (with part of a project I was working rather > slowly on with LilyPond) it was far too unstable to be usable. When was it? > Since then > I've learned more about LilyPond and become faster at coding, and haven't > felt a need to try MuseScore again. Maybe MuseScore has improved since then, > and maybe MuseScore and LilyPond can be made to talk to one another better, > but I'd really really hate to see LilyPond become in any way dependent on > point-and-click systems. Of course i don't mean this. It should always be possible to use Lily from a text interface. cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Beaming (was Re: Adding an 8 bellow the treble clef)
On 9/25/11 2:48 PM, "Janek Warchoł" wrote: > Our beaming really needs some improvements. Please post the problems you are aware of, and I'll give you whatever estimate I can about how hard they will be to fix. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: High-level users?
On 2011-09-25 11:13, Janek Warchoł wrote: 2011/9/24 Graham Percival: On Sat, Sep 24, 2011 at 03:24:18PM +0200, Janek Warchoł wrote: For what it's worth, i really *really* think that LilyPond and MuseScore should be integrated. What does that mean? - better lilypond export for musescore: go ahead and send patches there. - lilypond import for musescore: go ahead and send patches there. No, i mean *a lot* more. Therefore it's too big for me to handle alone - that's why i'm aksing who's interested in it. There'd be no point in writing my thoughts on this topic down and sending them to the list if noone would be interested. The last time I tried Musescore (with part of a project I was working rather slowly on with LilyPond) it was far too unstable to be usable. Since then I've learned more about LilyPond and become faster at coding, and haven't felt a need to try MuseScore again. Maybe MuseScore has improved since then, and maybe MuseScore and LilyPond can be made to talk to one another better, but I'd really really hate to see LilyPond become in any way dependent on point-and-click systems. In fact, I think they should remain as separate as, say, LilyPond and Emacs. -- Hilary ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
2011/9/25 Kieren MacMillan : > Hi Nick, > >> And BTW, the "8" is by default not properly centred under the bottom of the >> loop of the clef. I normally use >> \override Staff.OctavateEight #'X-offset = #0.6 >> to get it to where it looks correct. > > Good to see another obsessive-compulsive engraver on the list… ;) > I also think it's too small, so I tweak the font size as well. Count me in! I think it's too thin.* And perhaps it shouldn't be italic, i've seen mostly roman 8s. So, let's fix it? :) cheers, Janek * if you're interested, i've probably never seen any Lily score without some nitpicks that could be corrected... Our beaming really needs some improvements. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
Hi Nick, > And BTW, the "8" is by default not properly centred under the bottom of the > loop of the clef. I normally use > \override Staff.OctavateEight #'X-offset = #0.6 > to get it to where it looks correct. Good to see another obsessive-compulsive engraver on the list… ;) I also think it's too small, so I tweak the font size as well. Best, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
On 26/09/11 06:06, Kieren MacMillan wrote: Hi Alberto, Is there any standard way to, using lilypond, add an 8 bellow a treble clef, meaning that it should be sang an octave bellow? \clef "treble_8" And BTW, the "8" is by default not properly centred under the bottom of the loop of the clef. I normally use \override Staff.OctavateEight #'X-offset = #0.6 to get it to where it looks correct. Nick ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
2011/9/25 Alberto Simões : > Hello, Jenek, > > On 25/09/2011 21:22, Janek Warchoł wrote: >> >> Transposed clefs are discussed in Notation Reference ( >> >> http://lilypond.org/doc/v2.15/Documentation/notation/displaying-pitches#clef >> ). Since you have missed that information, maybe we should make it >> more visible. Do you think that we should add information about >> treble_8 clef here: >> http://lilypond.org/doc/v2.15/Documentation/learning/simple-notation ? >> Or maybe somewhere else? >> >> thanks in advance, >> Janek > > I think it was my "lazy" fault :) > I thought it to be something non standard, and gone searching directly in > the snippets repository :-/ Aha, ok. thanks, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
Dear Alberto,
You can do it this way:
{ \clef "treble_8" c'1 }
Hello
>
> Is there any standard way to, using lilypond, add an 8 bellow a treble
> clef, meaning that it should be sang an octave bellow?
>
> Thank you
> Alberto
> --
> Alberto Simoes
> CEHUM
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
Hello, Jenek, On 25/09/2011 21:22, Janek Warchoł wrote: Transposed clefs are discussed in Notation Reference ( http://lilypond.org/doc/v2.15/Documentation/notation/displaying-pitches#clef ). Since you have missed that information, maybe we should make it more visible. Do you think that we should add information about treble_8 clef here: http://lilypond.org/doc/v2.15/Documentation/learning/simple-notation ? Or maybe somewhere else? thanks in advance, Janek I think it was my "lazy" fault :) I thought it to be something non standard, and gone searching directly in the snippets repository :-/ Thanks -- Alberto Simoes CEHUM ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
Hi Alberto, 2011/9/25 Alberto Simões : > > On 25/09/2011 21:06, Kieren MacMillan wrote: >> >>> Is there any standard way to, using lilypond, add an 8 bellow a treble >>> clef, meaning that it should be sang an octave bellow? >> >> \clef "treble_8" > > Thats even simpler than what I found using google jut now :) > > \set Staff.clefPosition = #0 > \set Staff.clefOctavation = #0 > \set Staff.middleCPosition = #-4 Transposed clefs are discussed in Notation Reference ( http://lilypond.org/doc/v2.15/Documentation/notation/displaying-pitches#clef ). Since you have missed that information, maybe we should make it more visible. Do you think that we should add information about treble_8 clef here: http://lilypond.org/doc/v2.15/Documentation/learning/simple-notation ? Or maybe somewhere else? thanks in advance, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
On 25/09/2011 21:06, Kieren MacMillan wrote: Hi Alberto, Is there any standard way to, using lilypond, add an 8 bellow a treble clef, meaning that it should be sang an octave bellow? \clef "treble_8" Thats even simpler than what I found using google jut now :) \set Staff.clefPosition = #0 \set Staff.clefOctavation = #0 \set Staff.middleCPosition = #-4 Thanks -- Alberto Simoes CEHUM ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Adding an 8 bellow the treble clef
Hi Alberto, > Is there any standard way to, using lilypond, add an 8 bellow a treble clef, > meaning that it should be sang an octave bellow? \clef "treble_8" Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Adding an 8 bellow the treble clef
Hello Is there any standard way to, using lilypond, add an 8 bellow a treble clef, meaning that it should be sang an octave bellow? Thank you Alberto -- Alberto Simoes CEHUM ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: placement sostenuto
Hi Harm,
On Sun, Sep 25, 2011 at 1:01 PM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
> 2011/9/24 David Nalesnik
>
>>
>> I don't know if I've gotten at the name of the articulation in the best
>> way, but this works. One drawback is that there can only be one override of
>> 'after-line-breaking at a time.
>>
>
> 'before-line-breaking works too (see code below).
>
Aha -- good to know!
> [ . . . ] I'd prefer to store several properties in an alist, but I
> couldn't figure out how to read-out and call.
>
> p.e.:
> #(define ls '(
> ("staccato" . ((color . (1 0 0
> ("accent" . ((font-size . 4)(color . (1 0 0
> ("tenuto" . ((rotation . (45 0 0
> ("staccatissimo" . ((padding . -10) (color . (1 0 0
> ))
>
> Any idea?
>
You could change the function to map ly:grob-set-property! onto the alist if
a match is found:
\version "2.14.2"
#(define ls '(
("staccato" . ((color . (0 1 0
("accent" . ((font-size . 4)(color . (1 0 0
("tenuto" . ((rotation . (45 0 0)) (padding . 2)))
("staccatissimo" . ((padding . -10) (color . (0 0 1
))
#(define ((custom-script-tweaks type) grob)
(map
(lambda (arg)
(let ((lst (assoc-ref ls arg)))
(if (equal? arg (ly:prob-property (assoc-ref (ly:grob-properties
grob) 'cause) 'articulation-type))
(for-each (lambda (x) (ly:grob-set-property! grob (car x) (cdr
x))) lst)
'(
type))
\relative c'' {
f1--
f1--
\override Script #'before-line-breaking =
#(custom-script-tweaks '("staccato" "tenuto" "accent"
"staccatissimo"))
f-. f-| f-> f-> f-- f-|
\revert Script #'before-line-breaking
f-> f-.
}
-David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: placement sostenuto
Hi David
2011/9/24 David Nalesnik
> Hi Harm,
>
>>
> Thanks for the insight!
>
> So then you could do something like this:
>
I tried, but without success. :)
\version "2.14.2"
>
> #(define (padding-for-tenuto x)
>(lambda (grob)
> (if (equal? "tenuto" (ly:prob-property (assoc-ref (ly:grob-properties
> grob) 'cause) 'articulation-type))
> (ly:grob-set-property! grob 'padding x)
> '(
>
> #(define (custom-articulation-padding type x)
>(lambda (grob)
> (if (equal? type (ly:prob-property (assoc-ref (ly:grob-properties
> grob) 'cause) 'articulation-type))
> (ly:grob-set-property! grob 'padding x)
> '(
>
> \relative c'' {
> \once \override Script #'after-line-breaking = #(padding-for-tenuto
> 0.75)
> f1--
> f1--
> \override Script #'after-line-breaking = #(custom-articulation-padding
> "accent" 1)
> f->
> f->
> \revert Script #'after-line-breaking
> f->
> }
>
> I don't know if I've gotten at the name of the articulation in the best
> way, but this works. One drawback is that there can only be one override of
> 'after-line-breaking at a time.
>
'before-line-breaking works too (see code below).
> So, if you want multiple changes to default values -- a change to tenuto, a
> change to accent, etc. -- these should be added as conditions to the
> function. The second function lets you plug in the name of the articulation
> you want to override.
>
I did it this way:
\version "2.14.2"
#(define my-script-alist '(
("staccato" . (font-size . 15))
("accent" . (font-size . 4))
("tenuto" . (rotation . (45 0 0)))
("staccatissimo" . (padding . 2))
))
#(define ((custom-script-tweaks type) grob)
(map (lambda (arg)
(let ((lst (assoc-ref my-script-alist arg)))
(if (equal? arg (ly:prob-property (assoc-ref (ly:grob-properties
grob) 'cause) 'articulation-type))
(ly:grob-set-property! grob (car lst) (cdr lst))
'(
type))
#(define (custom-articulation-tweaks type property x)
(lambda (grob)
(if (equal? type (ly:prob-property (assoc-ref (ly:grob-properties grob)
'cause) 'articulation-type))
(ly:grob-set-property! grob property x)
'(
\relative c'' {
f1--
f1--
\override Script #'after-line-breaking =
#(custom-articulation-tweaks "accent" 'color red)
\override Script #'before-line-breaking =
#(custom-script-tweaks '("staccato" "tenuto" "accent"
"staccatissimo"))
f-. f-| f-> f-> f-- f-|
\revert Script #'after-line-breaking
\revert Script #'before-line-breaking
f-> f-.
}
To override "accent" I used the second function with 'before-line-breaking.
I'd prefer to store several properties in an alist, but I couldn't figure
out how to read-out and call.
p.e.:
#(define ls '(
("staccato" . ((color . (1 0 0
("accent" . ((font-size . 4)(color . (1 0 0
("tenuto" . ((rotation . (45 0 0
("staccatissimo" . ((padding . -10) (color . (1 0 0
))
Any idea?
Best,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: preprocessing an included file with system command
On Sun, Sep 25, 2011 at 1:08 PM, Karl Hammar wrote: > One does not really want macros nor preprocessors, since it munges > up error reporting. > Which one does not want them? :-) Seriously, I understand and, to a great extent, sympathize with that point of view -- especially when it involves incorporating macros into program code. OTOH, a little text substitution, used judiciously, is very often the simplest approach for working around the inelegant corners that occur in even the best designed languages. I'm speaking of making life a little simpler for LilyPond users, a large fraction of whom are savvy programmers. Speaking for myself, I'm pretty certain I can make good choices about when and when not to use macros. Cheers, Mike ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: preprocessing an included file with system command
Mike:
0173 140 57
> On Sun, Sep 25, 2011 at 6:34 AM, Dmytro O. Redchuk
> wrote:
> > On Sat 24 Sep 2011, 23:52 Michael Ellis wrote:
> >> On Sat, Sep 24, 2011 at 4:28 PM, Graham Percival
> >> > or m4 or python, I'd do this:
> >> > # mylily.sh
> >> > cp $1 /tmp
> >> > sed '...' /tmp/$1 > /tmp/$1-processed.ly
> >> > lilypond /tmp/$1-processed.ly
> >> > mv /tmp/$1-processed.ly .
> > Often it can be done with something like this (within bash script;
> > windows equivalent is also quite possible):
> >
> > sed '...' < $1 | lilypond -o ${1%%.ly} -
...
> But I think the larger question is whether future versions of Lily
> should support some form of text macro.
...
One does not really want macros nor preprocessors, since it munges
up error reporting.
Regards,
/Karl Hammar
---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: preprocessing an included file with system command
On Sun, Sep 25, 2011 at 6:34 AM, Dmytro O. Redchuk
wrote:
> On Sat 24 Sep 2011, 23:52 Michael Ellis wrote:
>> On Sat, Sep 24, 2011 at 4:28 PM, Graham Percival
>> > or m4 or python, I'd do this:
>> > # mylily.sh
>> > cp $1 /tmp
>> > sed '...' /tmp/$1 > /tmp/$1-processed.ly
>> > lilypond /tmp/$1-processed.ly
>> > mv /tmp/$1-processed.ly .
> Often it can be done with something like this (within bash script;
> windows equivalent is also quite possible):
>
> sed '...' < $1 | lilypond -o ${1%%.ly} -
>
>> I normally do my LilyPond work with LilyPondTool and have grown quite
>> accustomed to its conveniences. Using a wrapper script would mean
>> having to alter my LilyPondTool options to specify the wrapper script
>> instead of invoking LilyPond directly -- but I often use LilyPond for
>> tasks other than audio transcriptions and don't want to have to keep
>> changing my LilyPondTool options.
> I would, probably, try to write shell script, which takes $PPID and checks if
> the parent is LilypondTool or like that. Not tested .)
>
> Anyway, your question is still interesting. I can't help here, sorry.
>
Thanks, Dmytro. For my immediate problem I think I'm going to save
the Transcribe! output with some distinct extension and write a
watcher process that detects changes in files with that extension and
automatically runs my preprocessing to produce a file with a .inc
extension that I'll include in my .ly file.
But I think the larger question is whether future versions of Lily
should support some form of text macro. Perhaps we could have
something analogous to music functions like
mymacro = #(define-immediate-function ( args ) (predicates ) ( body ))
...
\mymacro args
with a guarantee that (body) will be executed before normal parsing
and that the return value would be injected in the file as though it
were the result of \include.
Cheers,
Mike
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: preprocessing an included file with system command
On Sat 24 Sep 2011, 23:52 Michael Ellis wrote:
> On Sat, Sep 24, 2011 at 4:28 PM, Graham Percival
> > or m4 or python, I'd do this:
> > # mylily.sh
> > cp $1 /tmp
> > sed '...' /tmp/$1 > /tmp/$1-processed.ly
> > lilypond /tmp/$1-processed.ly
> > mv /tmp/$1-processed.ly .
Often it can be done with something like this (within bash script;
windows equivalent is also quite possible):
sed '...' < $1 | lilypond -o ${1%%.ly} -
> I normally do my LilyPond work with LilyPondTool and have grown quite
> accustomed to its conveniences. Using a wrapper script would mean
> having to alter my LilyPondTool options to specify the wrapper script
> instead of invoking LilyPond directly -- but I often use LilyPond for
> tasks other than audio transcriptions and don't want to have to keep
> changing my LilyPondTool options.
I would, probably, try to write shell script, which takes $PPID and checks if
the parent is LilypondTool or like that. Not tested .)
Anyway, your question is still interesting. I can't help here, sorry.
--
Dmytro O. Redchuk
Bug Squad
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: High-level users?
2011/9/24 Graham Percival : > On Sat, Sep 24, 2011 at 03:24:18PM +0200, Janek Warchoł wrote: >> For what it's worth, i really *really* think that LilyPond and >> MuseScore should be integrated. > > What does that mean? > > - better lilypond export for musescore: go ahead and send patches > there. > - lilypond import for musescore: go ahead and send patches there. No, i mean *a lot* more. Therefore it's too big for me to handle alone - that's why i'm aksing who's interested in it. There'd be no point in writing my thoughts on this topic down and sending them to the list if noone would be interested. cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
