Can not install Lilypond via brew in Mac OS X Lion

I just purchased my first mac. I installed Mactux with no problem. But when I brew lilypond brew always exit with message "ghostescript" is not linked. But I 100% sure it linked. I don't know why. Anyone give me a suggestion? Many thanks, Ben Luo ___ l

Re: Source management tools for lilypond projects

Dear Urs, > It's astonishing - like reading a good book, but one written with my > specific questions in mind :-) :-) > What I will have to see in action before really being able to believe it > works in 'real life' is the merging of text files that have been changed > by more than one person

Re: Source management tools for lilypond projects

Hi Susan and Urs, On Wed, May 23, 2012 at 10:43 AM, Susan Dittmar wrote: > When you are done with your portion of work and all is in an acceptable > state again, then you can pull what others did change in the mean time from > a "master repository". This master repository is just another git > re

Directed \tweak commands in 2.15.39

Hi, with regard to the latest development release (and 7th stable release candidate), I wanted to point out a new feature that came in as a side-effect of reimplementing footnotes, an optional layout-object argument for tweaks: http://lilypond.org/doc/v2.15/Documentation/notation/the-tweak-comma

Re: Get the positions of a beam (or other grob with positions)

Hi David, i'm writing just to let you know that the function changing arpeggio length: offsetArpeggioPositions = #(define-music-function (parser location offsets) (pair?) #{ \override Arpeggio #'positions = #(lambda (grob) (let* ((func (assoc-get 'positions (cdr (ly:grob-basic-p

Re: Directed \tweak commands in 2.15.39

On Wed, May 23, 2012 at 12:23 PM, David Kastrup wrote: > > Hi, > > with regard to the latest development release (and 7th stable release > candidate), I wanted to point out a new feature that came in as a > side-effect of reimplementing footnotes, an optional layout-object > argument for tweaks: >

Re: Directed \tweak commands in 2.15.39

Janek Warchoł writes: > On Wed, May 23, 2012 at 12:23 PM, David Kastrup wrote: >> >> Hi, >> >> with regard to the latest development release (and 7th stable release >> candidate), I wanted to point out a new feature that came in as a >> side-effect of reimplementing footnotes, an optional layout

Re: Get the positions of a beam (or other grob with positions)

Janek Warchoł writes: > I wish it was possible to add context to grob name in a more > LilyPondish way (i.e. with a dot) It is conceivable as a parser extension, like 3/4 is nowadays generally read as '(3 . 4). One would turn aa.bb.cc (no spaces!) to #'(aa bb cc) in the lexer. It would likely

Re: Directed \tweak commands in 2.15.39

> with regard to the latest development release (and 7th stable > release candidate), I wanted to point out a new feature that came in > as a side-effect of reimplementing footnotes, an optional > layout-object argument for tweaks: > > http://lilypond.org/doc/v2.15/Documentation/notation/the-twea

Re: Source management tools for lilypond projects

Quoting Janek Warcho? (janek.lilyp...@gmail.com): > Actually, it is possible to pull from each other - there is no > technical need for a central "master repository" (that's what being a > distributed Version Control System means). Of course this can be > cumbersome for projects with many particip

Re: Removing initial Bar spanning two-staff system

Dominicus wrote: > > I'd like to remove the initial Bar line that spans a two-staff ChoirStaff. > How is this accomplished? > Best i could come up with was: > \override ChoirStaff.SpanBar #'transparent = ##t, but no luck. > > you can \override Score.SystemStartBracket #'transparent = ##t a

Re: Get the positions of a beam (or other grob with positions)

On Wed, May 23, 2012 at 1:02 PM, David Kastrup wrote: > Janek Warchoł writes: > >> I wish it was possible to add context to grob name in a more >> LilyPondish way (i.e. with a dot) > > It is conceivable as a parser extension, That's good news! > like 3/4 is nowadays generally read as '(3 . 4).

Re: Source management tools for lilypond projects

On Wed, May 23, 2012 at 1:09 PM, Susan Dittmar wrote: > When I pull the current (official) state of the project, I do *not* want to > debug my collegue's current work! That's OK for bugs he cannot find. But > not for things he only broke because he's just currently doing a change > there. > > So i

Re: Get the positions of a beam (or other grob with positions)

2012/5/23 Janek Warchoł : > On Wed, May 23, 2012 at 1:02 PM, David Kastrup wrote: >> Janek Warchoł writes: >> >>> I wish it was possible to add context to grob name in a more >>> LilyPondish way (i.e. with a dot) >> >> It is conceivable as a parser extension, > > That's good news! > >> like 3/4 i

Re: Directed \tweak commands in 2.15.39

Werner LEMBERG writes: >> with regard to the latest development release (and 7th stable >> release candidate), I wanted to point out a new feature that came in >> as a side-effect of reimplementing footnotes, an optional >> layout-object argument for tweaks: >> >> http://lilypond.org/doc/v2.15/D

Re: Directed \tweak commands in 2.15.39

On Wed, May 23, 2012 at 1:49 PM, David Kastrup wrote: > Werner LEMBERG writes: >> Very nice!  Great work, David.  A minor thing: In the given link I can >> see >> >>   \tweak layout-object #'grob-property value >> >> as the syntax line, mentioning that `layout-object' is optional. >> Wouldn't it

Re: Directed \tweak commands in 2.15.39

> I am not sure this syntax is familiar to non-programmers: it might > make people try using actual brackets. This is, after all, not the > Extending LilyPond reference. OK. Another possibility is specifying two lines: \tweak layout-object #'grob-property value \tweak #'grob-property value

Re: Directed \tweak commands in 2.15.39

2012/5/23 Janek Warchoł : > On Wed, May 23, 2012 at 1:49 PM, David Kastrup wrote: >> Werner LEMBERG writes: >>> Very nice!  Great work, David.  A minor thing: In the given link I can >>> see >>> >>>   \tweak layout-object #'grob-property value >>> >>> as the syntax line, mentioning that `layout-o

Re: Get the positions of a beam (or other grob with positions)

On Wed, May 23, 2012 at 1:43 PM, Thomas Morley wrote: > I tried it similar to `overrideProperty' from `music-functions-init.ly' > But I didn't manage to get rid of the ""-signs, when specifying the > coctext. Is this possible? > > \version "2.15.38" > > offsetPositions = > #(define-music-function

Re: Grace Note Thickness

Please forget question 1), my mistake. Infact, for some reason beams appears thicker in tabstaff. But what about question 2) ? 2012/5/23 Pierre Perol-Schneider > Hi Groups, > > few months ago Thoms Morley (found thanks too Google) sent this code, > wiche works fine : > > \version "2.14.2" > %\ve

Re: Get the positions of a beam (or other grob with positions)

Thomas Morley writes: > I tried it similar to `overrideProperty' from `music-functions-init.ly' > But I didn't manage to get rid of the ""-signs, when specifying the > coctext. Is this possible? > > \version "2.15.38" > > offsetPositions = > #(define-music-function (parser location name offsets)

Re: Grace Note Thickness

2012/5/23 Pierre Perol-Schneider : > Hi Groups, > > few months ago Thoms Morley (found thanks too Google) sent this code, wiche > works fine : (...) > Now I would like to understand this : > > 1) > > \version "2.15.39" > > music = \relative c' { > \grace { d,16 [des] } c4 > } > \score { >

Re: Directed \tweak commands in 2.15.39

Thomas Morley writes: > 2012/5/23 Janek Warchoł : >> On Wed, May 23, 2012 at 1:49 PM, David Kastrup wrote: >>> Werner LEMBERG writes: Very nice!  Great work, David.  A minor thing: In the given link I can see   \tweak layout-object #'grob-property value as the synt

Re: Grace Note Thickness

> BTW, what do you intend at all? In the last LilyPond Report , the comparison of Breitkopf and the "airy" Lilypond outpout, according to Janek, is something that I agree 100% for quite a long time. What I would like to do is, as a 1st step,

Re: Grace Note Thickness

See *airy.png* 2012/5/23 Pierre Perol-Schneider > > BTW, what do you intend at all? > > In the last LilyPond > Report , > the comparison of Breitkopf and the "airy" Lilypond outpout, according to > Janek, is something that I agree 100% fo

Re: \autochange between "treble^8" and treble

please reply to the list in order to let others participate and contribute! > > Is there no way to do modify the \autiochange function? > > It's so sad... I don't want to do that with manually change. > > If possible and if you know that, where is the \autiochange function file? > > I think

Re: \autochange between "treble^8" and treble

Is there no way to do modify the \autiochange function? It's so sad... I don't want to do that with manually change. If possible and if you know that, where is the \autiochange function file? I think, I can find the file and edit, and then I can use the modified function. Between treble^8 and t

How to catch the current height of a StaffGroup?

Hi, I'm trying to read out the current height of a StaffGroup, i.e. from the bottom-line of the bottom-staff up to the top-line of the top-staff. As a test I created a new BreathingSign-stencil drawing a line from top-line to bottom-line. The value for draw-line is figured out manually for now. O

Re: How to catch the current height of a StaffGroup?

No idea about Scheme, but shouldn't a standard barline have the desired length by default? Best Urs Am 23.05.2012 18:57, schrieb Thomas Morley: Hi, I'm trying to read out the current height of a StaffGroup, i.e. from the bottom-line of the bottom-staff up to the top-line of the top-staff. As

Re: Source management tools for lilypond projects

Hi, as I just stumbled over this again, a small hint concerning commits: ALWAYS add a commit message, even if it is just "intermittent state" or even "automated checkin". At least with subversion, the log will only list revisions with changes if they have a commit message. If you leave that messag

Re: How to catch the current height of a StaffGroup?

2012/5/23 Urs Liska : > but shouldn't a standard barline have the desired length by default? Of course, but the new BreathingSign-stencil is only to visualize that I've got the correct value. And a BarLine lives in Staff-context but I want the "StaffGroup-size". Trying: \override

Re: How to catch the current height of a StaffGroup?

On 23 mai 2012, at 19:19, Thomas Morley wrote: > 2012/5/23 Urs Liska : >> but shouldn't a standard barline have the desired length by default? > > Of course, but the new BreathingSign-stencil is only to visualize that > I've got the correct value. > And a BarLine lives in Staff-context but I want

Re: Voices and vocals

2012/5/23 John McWilliam : > Have you looked at my reply. I tried to post on gmane but am told my > messages are not valid due to "top posting" - what is that? I just want > people with experience to look at my snippet and give suggestions for how to > solve my problem. > > Please respond, > > John

Re: How to catch the current height of a StaffGroup?

2012/5/23 m...@apollinemike.com : > Try the buddy engraver! (...) > If you do something like \override Staff.BarLine #'my-name = #'foo in one > staff and \override Staff.BarLine #'my-name = #'bar in another and then > \override BreathingSign #'searching = #'(foo bar) then BreathingSign will > h

Re: How to catch the current height of a StaffGroup?

Thomas Morley writes: > #(define all-custom-grob-descriptions >(for-each > (lambda (x) >(let ((interfaces >(ly:assoc-get 'interfaces > (ly:assoc-get 'meta >(cdr x) > (set! interfaces (append! interfaces '(grob-mark

Re: How to catch the current height of a StaffGroup?

2012/5/23 David Kastrup : > Thomas Morley writes: > >> #(define all-custom-grob-descriptions >>    (for-each >>      (lambda (x) >>        (let ((interfaces >>                (ly:assoc-get 'interfaces >>                  (ly:assoc-get 'meta >>                    (cdr x) >>          (set! inter

Re: How to catch the current height of a StaffGroup?

Thomas Morley writes: > It was a copy/paste-error. Actually, I don't want to define a new > grob, only new properties. > > The foolowing seems to be ok, or not? > > \version "2.15.38" > > #(define (define-grob-property symbol type? description) > (if (not (equal? (object-property symbol 'backen

Re: How to catch the current height of a StaffGroup?

2012/5/23 David Kastrup : > Thomas Morley writes: > >> It was a copy/paste-error. Actually, I don't want to define a new >> grob, only new properties. >> >> The foolowing seems to be ok, or not? >> >> \version "2.15.38" >> >> #(define (define-grob-property symbol type? description) >>   (if (not (

Re: How to catch the current height of a StaffGroup?

Next try to tackle the main problem, without engraver, but same idea: Mark some grobs and read out their position. After defining a 'marker-property and applying it with 'foo and 'bar to some BarLines, I tried to color them from inside the BreathingSign-after-line-breaking-override. Works! But ev

Re: \autochange between "treble^8" and treble

On Wed, May 23, 2012 at 6:48 PM, Jonghyun Kim wrote: > Is there no way to do modify the \autiochange function? > > It's so sad... I don't want to do that with manually change. > > If possible and if you know that, where is the \autiochange function file? I think it's in scm/autochange.scm hope t

Re: Source management tools for lilypond projects

On Wed, May 23, 2012 at 7:13 PM, Susan Dittmar wrote: > Hi, > > as I just stumbled over this again, a small hint concerning commits: > ALWAYS add a commit message, even if it is just "intermittent state" or > even "automated checkin". At least with subversion, the log will only list > revisions wi

Re: Directed \tweak commands in 2.15.39

On Wed, May 23, 2012 at 3:10 PM, David Kastrup wrote: > Honestly?  Our documentation was created in lots of little bits from > different contributors at different times.  If we hope to bring it into > a reasonably more consistent state, discussing single lines and examples > is going to be ridicul

Re: Grace Note Thickness

2012/5/23 Pierre Perol-Schneider : > Dear Thomas, > > I've followed your instruction and when I code : (...) I'm not aware I gave you any instructions. :) > Problem comes with the polyphony : (...) Well, I see the problem, but I'm too tired to have any useful idea. Perhaps tomorrow. Cheers, H

Re: Directed \tweak commands in 2.15.39

Janek Warchoł writes: > On Wed, May 23, 2012 at 3:10 PM, David Kastrup wrote: >> Honestly?  Our documentation was created in lots of little bits from >> different contributors at different times.  If we hope to bring it into >> a reasonably more consistent state, discussing single lines and exam

Re: Source management tools for lilypond projects

Not sure if this was already discussed (I've been following the thread somewhat loosely), but it seems to me that git makes it a whole lot easier to handle a "build token" by virtue of the repositories being decentralized. I admit, I'm not an svn expert and it's quite likely there are some svn wor

Re: Directed \tweak commands in 2.15.39

On Thu, May 24, 2012 at 12:39 AM, David Kastrup wrote: > Janek Warchoł writes: > >> On Wed, May 23, 2012 at 3:10 PM, David Kastrup wrote: >>> Instead, it would make more sense if people opted to take care of >>> something like a chapter at a time, or the relation between two >>> chapters, and br