Re: Feature request: Display bezier control-points
Hello,
On 4 May 2012 01:31, Urs Liska wrote:
> Am 04.05.2012 02:08, schrieb David Nalesnik:
>
>> Hi Urs,
>>
>> > It would be a really valuable feature if one could let LilyPond
>> display
>> > the control-points of a bezier curve.
>> > I would imagine something like a cross or a point at the middle two
>> > control-points.
>>
>>
>> I think this would be very helpful, so that you can visualize exactly what
>> these control-points are that you're setting. (It must be a common
>> misconception that they are points on the actual curve.)
>>
>> I'm not sure what impact this may have on the layout, but you could do
>> something like the following:
>>
>> \version "2.15.37"
>>
>> #(define (make-cross-stencil coords)
>> (ly:stencil-add
>> (make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
>> (+ (car coords) 0.2) (+ (cdr coords) 0.2))
>> (make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
>> (+ (car coords) 0.2) (- (cdr coords) 0.2
>>
>> #(define display-control-points
>> (lambda (grob)
>> (let ((stencil (ly:slur::print grob))
>> (cps (ly:grob-property grob 'control-points)))
>> (ly:stencil-add stencil
>> (make-cross-stencil (second cps))
>> (make-cross-stencil (third cps))
>> \relative c'' {
>> \override Slur #'stencil = #display-control-points
>> c( d e f)
>> }
>>
>> Hope you find this helpful!
>
> Wow, extremely!
> Of course I would prefer to have this built-in.
> And as you I can't really judge if this has side effects.
> But this really _is_ helping to find suitable values for the control-points.
>
> * Although I know bezier curves from vector graphics software, I also
> was convinced that the 'control-points' were four points on the
> curve that define its shape.
> * In fact the first and last are such points, whereas the middle two
> 'control-points' are the 'handles'.
> -> Is this explained somewhere?
http://lilypond.org/doc/v2.14/Documentation/notation-big-page.html#modifying-ties-and-slurs
?
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Hi Harm,
> how about:
>
> \version "2.14.2"
>
> #(define (make-cross-stencil coords)
> (ly:stencil-add
> (make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
> (+ (car coords) 0.2) (+ (cdr coords) 0.2))
> (make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
> (+ (car coords) 0.2) (- (cdr coords) 0.2
>
> #(define (display-control-points line)
> (lambda (grob)
> (let ((stencil (ly:slur::print grob))
> (cps (ly:grob-property grob 'control-points)))
>
> (ly:stencil-add stencil
> (ly:stencil-in-color
> (make-cross-stencil (second cps))
> 1 0 0)
> (ly:stencil-in-color
> (make-cross-stencil (third cps))
> 1 0 0)
> (if (eq? line #t)
> (make-line-stencil 0.05 (car (second cps)) (cdr (second cps))
> (car (third cps)) (cdr (third cps)))
> empty-stencil)
> )
> )))
>
> \relative c'' {
> \override Slur #'stencil = #(display-control-points #t)
> c2( d e f)
> }
>
Looks great! Makes this even more fun to play around with :)
-David
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Hi Urs, >> But this really _is_ helping to find suitable values for the >> control-points. >> > I'm very glad to hear this! > >> * Although I know bezier curves from vector graphics software, I >>also was convinced that the 'control-points' were four points on >>the curve that define its shape. >> > Initially I did too... > * In fact the first and last are such points, whereas the middle two >>'control-points' are the 'handles'. >>-> Is this explained somewhere? >> * From seeing the crosses I now realize that (when using your >>function) all four offsets are relative to LilyPond's original >>decision. >>Well, if you think about it, that's quite obvious, but I always >>assumed that if I change one offset the other control-points would >>be affected accordingly. >>But in fact they aren't. So if I for example raise the endpoint of >>a slur, the third control-point may well get below the slur. >>This makes me understand the seemingly strange behaviour of the >>slurs when fiddling with the offsets. > > * -> Probably it'll greatly improve my 'tweaking experience', even >>if I have seen this only once, not to speak if I manage to include >>this in a real-life workflow ... >>So, many thanks once more, David! >> > You're very welcome! I've been playing around with it a bit myself, and I'm becoming more and more convinced that something like this would be a very useful feature. You can also use it to show you the effect of changing other properties. For example, you can see the effects of overriding 'height-limit and 'eccentricity. I'm finding it very instructive. At least one thing, which I did do right now: > I compiled one score with and without your cross setting, and comparing > the two pdfs with Alt-Tab showed that the layout was perfectly identical - > except for the additional crosses. > So obviously the crosses are added after LilyPond decides about the layout. > I'm very glad to hear this! My worry was that the crosses might push staves further apart in extreme situations. Thanks for trying this out! -David ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Hi Urs,
> I would be very happy about one or two more features (that I unfortunately
> can't implement myself:
> - highlight (and separate from the music) the crosses through a color
> - possibly adding a connecting (very thin) line, making it even more
> intuitive
>
> Best
> Urs
how about:
\version "2.14.2"
#(define (make-cross-stencil coords)
(ly:stencil-add
(make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
(+ (car coords) 0.2) (+ (cdr coords) 0.2))
(make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
(+ (car coords) 0.2) (- (cdr coords) 0.2
#(define (display-control-points line)
(lambda (grob)
(let ((stencil (ly:slur::print grob))
(cps (ly:grob-property grob 'control-points)))
(ly:stencil-add stencil
(ly:stencil-in-color
(make-cross-stencil (second cps))
1 0 0)
(ly:stencil-in-color
(make-cross-stencil (third cps))
1 0 0)
(if (eq? line #t)
(make-line-stencil 0.05 (car (second cps)) (cdr (second cps))
(car (third cps)) (cdr (third cps)))
empty-stencil)
)
)))
\relative c'' {
\override Slur #'stencil = #(display-control-points #t)
c2( d e f)
}
HTH,
Harm
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Am 04.05.2012 02:31, schrieb Urs Liska:
Am 04.05.2012 02:08, schrieb David Nalesnik:
Hi Urs,
> It would be a really valuable feature if one could let LilyPond
display
> the control-points of a bezier curve.
> I would imagine something like a cross or a point at the middle two
> control-points.
I think this would be very helpful, so that you can visualize exactly
what these control-points are that you're setting. (It must be a
common misconception that they are points on the actual curve.)
I'm not sure what impact this may have on the layout, but you could
do something like the following:
\version "2.15.37"
#(define (make-cross-stencil coords)
(ly:stencil-add
(make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
(+ (car coords) 0.2) (+ (cdr coords) 0.2))
(make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
(+ (car coords) 0.2) (- (cdr coords) 0.2
#(define display-control-points
(lambda (grob)
(let ((stencil (ly:slur::print grob))
(cps (ly:grob-property grob 'control-points)))
(ly:stencil-add stencil
(make-cross-stencil (second cps))
(make-cross-stencil (third cps))
\relative c'' {
\override Slur #'stencil = #display-control-points
c( d e f)
}
Hope you find this helpful!
Wow, extremely!
Of course I would prefer to have this built-in.
And as you I can't really judge if this has side effects.
But this really _is_ helping to find suitable values for the
control-points.
* Although I know bezier curves from vector graphics software, I
also was convinced that the 'control-points' were four points on
the curve that define its shape.
* In fact the first and last are such points, whereas the middle two
'control-points' are the 'handles'.
-> Is this explained somewhere?
* From seeing the crosses I now realize that (when using your
function) all four offsets are relative to LilyPond's original
decision.
Well, if you think about it, that's quite obvious, but I always
assumed that if I change one offset the other control-points would
be affected accordingly.
But in fact they aren't. So if I for example raise the endpoint of
a slur, the third control-point may well get below the slur.
This makes me understand the seemingly strange behaviour of the
slurs when fiddling with the offsets.
* -> Probably it'll greatly improve my 'tweaking experience', even
if I have seen this only once, not to speak if I manage to include
this in a real-life workflow ...
So, many thanks once more, David!
I'll test this together with your new offset function (I intended to
do it this very evening, but it has become sooo late now (here in
Central Europe) ...
At least one thing, which I did do right now:
I compiled one score with and without your cross setting, and comparing
the two pdfs with Alt-Tab showed that the layout was perfectly identical
- except for the additional crosses.
So obviously the crosses are added after LilyPond decides about the layout.
So tomorrow I will incorporate all this into my set-up (in a way that in
'draft mode' display-control-points is active by default)
I would be very happy about one or two more features (that I
unfortunately can't implement myself:
- highlight (and separate from the music) the crosses through a color
- possibly adding a connecting (very thin) line, making it even more
intuitive
Best
Urs
Best
Urs
-David
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Am 04.05.2012 02:08, schrieb David Nalesnik:
Hi Urs,
> It would be a really valuable feature if one could let LilyPond
display
> the control-points of a bezier curve.
> I would imagine something like a cross or a point at the middle two
> control-points.
I think this would be very helpful, so that you can visualize exactly
what these control-points are that you're setting. (It must be a
common misconception that they are points on the actual curve.)
I'm not sure what impact this may have on the layout, but you could do
something like the following:
\version "2.15.37"
#(define (make-cross-stencil coords)
(ly:stencil-add
(make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
(+ (car coords) 0.2) (+ (cdr coords) 0.2))
(make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
(+ (car coords) 0.2) (- (cdr coords) 0.2
#(define display-control-points
(lambda (grob)
(let ((stencil (ly:slur::print grob))
(cps (ly:grob-property grob 'control-points)))
(ly:stencil-add stencil
(make-cross-stencil (second cps))
(make-cross-stencil (third cps))
\relative c'' {
\override Slur #'stencil = #display-control-points
c( d e f)
}
Hope you find this helpful!
Wow, extremely!
Of course I would prefer to have this built-in.
And as you I can't really judge if this has side effects.
But this really _is_ helping to find suitable values for the control-points.
* Although I know bezier curves from vector graphics software, I also
was convinced that the 'control-points' were four points on the
curve that define its shape.
* In fact the first and last are such points, whereas the middle two
'control-points' are the 'handles'.
-> Is this explained somewhere?
* From seeing the crosses I now realize that (when using your
function) all four offsets are relative to LilyPond's original decision.
Well, if you think about it, that's quite obvious, but I always
assumed that if I change one offset the other control-points would
be affected accordingly.
But in fact they aren't. So if I for example raise the endpoint of a
slur, the third control-point may well get below the slur.
This makes me understand the seemingly strange behaviour of the
slurs when fiddling with the offsets.
* -> Probably it'll greatly improve my 'tweaking experience', even if
I have seen this only once, not to speak if I manage to include this
in a real-life workflow ...
So, many thanks once more, David!
I'll test this together with your new offset function (I intended to do
it this very evening, but it has become sooo late now (here in Central
Europe) ...
Best
Urs
-David
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request for the mailing list
On Wed, May 02, 2012 at 11:36:09AM +0200, Dona Mommsen wrote: > I accidentally flooded the mailing list with several messages > because my first post as a new user did not came through. > There was no difference whether I tried to post directly or via the > gmane web-interface. > Maybe adding a little waring on the mailing list website would be > helpful, like: «first posts may take longer because they are > moderated» I just realised that when you said "mailing list website" you might have been referring to this web page: https://lists.gnu.org/mailman/listinfo/lilypond-user I'm not sure that the Lilypond developers are able to change the text of that page. What we can do is to edit the Contact page on the Lilypond website, here: http://www.lilypond.org/contact.html Please bear that in mind when you create your documentation suggestion. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
On Thu, May 3, 2012 at 7:08 PM, David Nalesnik wrote: > Hi Urs, > > > It would be a really valuable feature if one could let LilyPond display >> > the control-points of a bezier curve. >> > I would imagine something like a cross or a point at the middle two >> > control-points. >> > > I think this would be very helpful, so that you can visualize exactly what > these control-points are that you're setting. (It must be a common > misconception that they are points on the actual curve.) > Of course, you can use the slur tweak tool in LilyPondTool! -David ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
Hi Urs,
> It would be a really valuable feature if one could let LilyPond display
> > the control-points of a bezier curve.
> > I would imagine something like a cross or a point at the middle two
> > control-points.
>
I think this would be very helpful, so that you can visualize exactly what
these control-points are that you're setting. (It must be a common
misconception that they are points on the actual curve.)
I'm not sure what impact this may have on the layout, but you could do
something like the following:
\version "2.15.37"
#(define (make-cross-stencil coords)
(ly:stencil-add
(make-line-stencil 0.1 (- (car coords) 0.2) (- (cdr coords) 0.2)
(+ (car coords) 0.2) (+ (cdr coords) 0.2))
(make-line-stencil 0.1 (- (car coords) 0.2) (+ (cdr coords) 0.2)
(+ (car coords) 0.2) (- (cdr coords) 0.2
#(define display-control-points
(lambda (grob)
(let ((stencil (ly:slur::print grob))
(cps (ly:grob-property grob 'control-points)))
(ly:stencil-add stencil
(make-cross-stencil (second cps))
(make-cross-stencil (third cps))
\relative c'' {
\override Slur #'stencil = #display-control-points
c( d e f)
}
Hope you find this helpful!
-David
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request for the mailing list
On Wed, May 02, 2012 at 11:36:09AM +0200, Dona Mommsen wrote: > > I accidentally flooded the mailing list with several messages > because my first post as a new user did not came through. > > Maybe adding a little warning on the mailing list website would be helpful Thanks for the bug report, Dona. In situations like this, where you see a need for a small change to the documentation, it is really helpful if you create a Documentation Suggestion, as described here: http://www.lilypond.org/doc/v2.15/Documentation/contributor/documentation-suggestions Once you have done this, send it to bug-lilypond and we'll create a tracker for it. By doing this you greatly simplify the task for the documentation team. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Feature request: Display bezier control-points
On Thu, May 3, 2012 at 7:14 PM, Urs Liska wrote:
> Sorry if I should be asking for something that is already possible, but at
> least I don't know of it ...
>
> Tweaking slurs and similar curves is a matter of trial and error, although
> David's functions that expect offsets instead of hardcoded control-points
> greatly simplify it.
>
> It would be a really valuable feature if one could let LilyPond display
> the control-points of a bezier curve.
> I would imagine something like a cross or a point at the middle two
> control-points.
>
> It should be settable through e.g.
>\paper { display-control-points = ##t }
> (like annotate-spacing)
>
> Is that of general interest?
> And does it look complicated?
>
> Best
> Urs
Greetings, Urs and list members :
Your request for an enhancement has been submitted as issue 2510 :
http://code.google.com/p/lilypond/issues/detail?id=2510
Enjoy your music writing/transcribing/playing,
Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Feature request: Display bezier control-points
Sorry if I should be asking for something that is already possible, but
at least I don't know of it ...
Tweaking slurs and similar curves is a matter of trial and error,
although David's functions that expect offsets instead of hardcoded
control-points greatly simplify it.
It would be a really valuable feature if one could let LilyPond display
the control-points of a bezier curve.
I would imagine something like a cross or a point at the middle two
control-points.
It should be settable through e.g.
\paper { display-control-points = ##t }
(like annotate-spacing)
Is that of general interest?
And does it look complicated?
Best
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Something strange
Karol Majewski writes: > OK, Janek. Thanks for the tip. I've compiled the files with debug-skylines > set to true and now it's clear that there is a difference. Just take a look > at the at the attachment (the red line was drawn by me). > > I've also noticed one more thing: After putting my *.ly file into > LilyPond\usr\bin directory, I've compiled it in two different ways: > - by clicking left_mouse_button twice > - by entering from cmd: lilypond --pdf filename.ly > > Using the first method, I got the wrong position of this dynamic mark (too > high), but with the second method, it's position was fine! Tell you what: my guess is that you are calling two different versions of LilyPond installed on your system. Usually lilypond mentions, when called, which version it is. Do both ways of calling report the same version? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Something strange
OK, Janek. Thanks for the tip. I've compiled the files with debug-skylines set to true and now it's clear that there is a difference. Just take a look at the at the attachment (the red line was drawn by me). I've also noticed one more thing: After putting my *.ly file into LilyPond\usr\bin directory, I've compiled it in two different ways: - by clicking left_mouse_button twice - by entering from cmd: lilypond --pdf filename.ly Using the first method, I got the wrong position of this dynamic mark (too high), but with the second method, it's position was fine! 2012/5/3 Janek Warchoł > On Thu, May 3, 2012 at 6:52 PM, Karol Majewski > wrote: > > Hi there! > > > > I've noticed very strange behavior from LilyPond. So what I do is: > > 1.create *.pdf from my *.ly file > > 2.copy this *.ly file to another directory > > 3.create *.pdf from my *.ly file in this new directory > > > > It's hard to belive, but despite both *.ly files are exactly the same > (they > > are in different directories), the output in pdf is diferent! And the > > difference applies to position of the dynamic mark. > > looks very interesting. Could you compile them with debug-skylines > option? (add #(ly:set-option 'debug-skylines #t) to your source) > > Maybe your file \includes something from a relative path? > > cheers, > Janek > <>___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Something strange
On Thu, May 3, 2012 at 6:52 PM, Karol Majewski wrote: > Hi there! > > I've noticed very strange behavior from LilyPond. So what I do is: > 1.create *.pdf from my *.ly file > 2.copy this *.ly file to another directory > 3.create *.pdf from my *.ly file in this new directory > > It's hard to belive, but despite both *.ly files are exactly the same (they > are in different directories), the output in pdf is diferent! And the > difference applies to position of the dynamic mark. looks very interesting. Could you compile them with debug-skylines option? (add #(ly:set-option 'debug-skylines #t) to your source) Maybe your file \includes something from a relative path? cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Something strange
Karol Majewski writes: > Hi there! > > I've noticed very strange behavior from LilyPond. So what I do is: > 1.create *.pdf from my *.ly file > 2.copy this *.ly file to another directory > 3.create *.pdf from my *.ly file in this new directory > > It's hard to belive, but despite both *.ly files are exactly the same > (they are in different directories), the output in pdf is diferent! > And the difference applies to position of the dynamic mark. I have no > idea why is this happening Are you sure this is dependent on the directory, or can you get different results in the same directory on multiple runs? If it does depend on the directories, does it make a difference if the path name of the directory does not differ in the length of its subdirectory names (and assuming those contain only ASCII characters)? Does you .ly file meddle with Scheme? -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Something strange
Hi there! I've noticed very strange behavior from LilyPond. So what I do is: 1.create *.pdf from my *.ly file 2.copy this *.ly file to another directory 3.create *.pdf from my *.ly file in this new directory It's hard to belive, but despite both *.ly files are exactly the same (they are in different directories), the output in pdf is diferent! And the difference applies to position of the dynamic mark. I have no idea why is this happening <>___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Special characters in path using lilypond-book with Texshop engine
On Wed, May 02, 2012 at 09:59:46PM +0200, Nicola Vitacolonna wrote: > > On 2 May 2012, at 11:33 , Dona Mommsen wrote: > > > Hi, > > > > I'm using > > ??? Lilypond-book (v.2.14.2) with TeXShop (v2.43) on Mac OS X (v10.7.3). > > > > with Nicola Vitacolonna's engine for TexShop > > > > http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-engines-texshop > > > >> The engine(s) cannot handle special characters in the path names, even > >> when they do not appear in a relative path > > [???] > > However, I don't now if this is an issue due to lilypond-book or due to the > > TexShop engine. > > > My TeXShop engine is a very simple tcsh script that sets some environment > variables then calls the lilypond executable. To confirm that the problem is > lilypond you may run it directly from the Terminal, passing a full or > relative path. > > From the results of your tests, however, I think that it is possible to > modify my engine so that it works with arbitrary paths. I???ll try to look > into it during the weekend. Thanks for picking that up, Nicola. If you find that the problem lies with Lilypond please let us know and the bug-squad deal with it. Until then, we'll treat this report as evidence of a limitation of your TexShop engine, rather than a bug in either your engine or Lilypond. Cheers, Colin. -- Colin Hall ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: uniform-stretching results in too much space after barline
Hi,
On Thu, May 3, 2012 at 7:56 AM, James wrote:
> I couldn't work out what your first attachment (with the slur) had to
> do with the PDF, bt anyway try
Looks that i seriously failed to explain myself.
The small png was a real-life example of a triplet spacing problem
i've encountered. It was a screenshot from a score i'm working on.
I've figured out that when i use uniform-stretching, the problem with
bad triplets goes away, but there are some side-effects. I had to
post some example code to demonstrate these side-effects - this was
the code in my message, and the output of this code was attached as
pdf. The example was atrificial and contrived, but it demostrated the
problem: setting uniform-stretching to ##t results in too much space
after the barlines.
> (basically change the \time an add a ragged right) and it seems
> counterintuitive, but the two are definitely different in this regard.
> To be perfectly honest I like the space, and when you cram the notes
> in the space does seem to be even - try repeat unfold 32 for
> instance. I cannot see any difference - if that matters.
Sorry, but i don't understand what you mean at all.
Since my example was artificial, changing anything can break it
(meaning that the example will no longer demonstrate the problem).
Your code doesn't solve the problem, it is simply not affected by the
bug.
A simplified snippet below. I also think this may qualify as a bug,
so i'm cross-posting to bugreports.
cheers,
Janek
\version "2.15.36"
\markup "uniform-stretching results in too much space after barline"
\score {
\repeat unfold 16 gis'8
\layout {
ragged-right = ##f
\override Score.SpacingSpanner #'uniform-stretching = ##t
}
}
\markup "compile this to see how the output should look like:"
\score {
\repeat unfold 16 gis'8
\layout {
ragged-right = ##f
}
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Special characters in path using lilypond-book with Texshop engine
On 2 May 2012, at 11:33 , Dona Mommsen wrote: > Hi, > > I'm using > ➙ Lilypond-book (v.2.14.2) with TeXShop (v2.43) on Mac OS X (v10.7.3). > > with Nicola Vitacolonna's engine for TexShop > > http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-engines-texshop > >> The engine(s) cannot handle special characters in the path names, even when >> they do not appear in a relative path > […] > However, I don't now if this is an issue due to lilypond-book or due to the > TexShop engine. My TeXShop engine is a very simple tcsh script that sets some environment variables then calls the lilypond executable. To confirm that the problem is lilypond you may run it directly from the Terminal, passing a full or relative path. From the results of your tests, however, I think that it is possible to modify my engine so that it works with arbitrary paths. I’ll try to look into it during the weekend. Regards, Nicola ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Special characters in path using lilypond-book with Texshop engine
Hi,
I'm using
➙ Lilypond-book (v.2.14.2) with TeXShop (v2.43) on Mac OS X (v10.7.3).
with Nicola Vitacolonna's engine for TexShop
http://users.dimi.uniud.it/~nicola.vitacolonna/home/content/lilypond-engines-texshop
> The engine(s) cannot handle special characters in the path names, even when
> they do not appear in a relative path. I had a subfolder ./Exemples with the
> Lilypond files, but the path further up contained french special characters,
> so I ran into «file not found» troubles.
The test example (below) is taken from Nicola's website. However, I replaced
the the included file with test.ly (standard test file from lilypond).
The test case works flawless
ok 1. when the file is in the same directory, or
ok 2. in a subdirectory when there is no special character in the entire path.
failed 3. The test case fails when there are special characters in the path. I
have a parent directory named Flûte-à-bec that causes a "File not found error"
(see screenshot of console below)
However, I don't now if this is an issue due to lilypond-book or due to the
TexShop engine.
Thanks in advance for looking into this.
Have a great time,
Dona
> % !TEX encoding = UTF-8 Unicode
> % !TEX TS-program = LilyPond-Book
>
> \documentclass[a4paper]{article}
>
> \begin{document}
>
> Documents for \verb+lilypond-book+ may freely mix music and text.
> For example,
>
> \begin{lilypond}
> \relative c' {
> c2 g'2 \times 2/3 { f8 e d } c'2 g4
> }
> \end{lilypond}
>
> Options are put in brackets.
>
> \begin[fragment,quote,staffsize=26,verbatim]{lilypond}
> c'4 f16
> \end{lilypond}
>
> Larger examples can be put into a separate file, and introduced with
> \verb+\lilypondfile+.
>
> \lilypondfile[quote,noindent]{test.ly}
>
> (If needed, replace screech-boink.ly by any .ly file you put in the same
> directory as this file.)
>
> \end{document}
> \end
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Feature request for the mailing list
Hi, I accidentally flooded the mailing list with several messages because my first post as a new user did not came through. There was no difference whether I tried to post directly or via the gmane web-interface. Maybe adding a little waring on the mailing list website would be helpful, like: «first posts may take longer because they are moderated» Thanks in advance, Dona ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
