Re: Issue 2259 in lilypond: Hairpin still hits barline at line break

[lilypond]

Comment #20 on issue 2259 by address@hidden: Hairpin still hits barline  
at line break
http://code.google.com/p/lilypond/issues/detail?id=2259

Sorry for disappointing you then. LilyPond is not my only concern, because  
then I would definitely try to understand its code and make patches myself  
(it may happen anyway some day...). But if someone is into it already, then  
such fixes possibly shouldn't be a big problem. I had times when my  
feedback wasn't prompt (as in case of issue 2232), but I think I was more  
commenting (issues 2057, 2130, 2165 and now 2259) than you can see in most  
other issues. Also my initial report was using piano centered dynamics  
already, but it got into tracker w/o it (submitter apparently thought it's  
irrelevant). I agree though, that I did not cover all possible variations  
of hairpins back then (but I commented later about most of them). I didn't  
thought that broadly, but developer possibly should, because (s)he is (at  
least should be) much more aware of implementation peculiarities and its  
side effects.

All that aside, "inversely proportional"? What the heck are you talking  
about and where it comes from? Because I don't build lilypond myself as  
soon as patch is in the repo to check its result immediately? Or it's  
because I don't offer a bounty?

I appreciate all your efforts, David, really. But turning everything into a  
bounty thing isn't that good (maybe you're too much into making your  
profitable business based on LilyPond?). And I would maybe even consider  
donating some general bounty, because I think LilyPond is great, but when  
you mention it that explicitly, I'm somehow becoming more than reluctant.  
Why there isn't any donate button on the homepage in the first place?  
PayPal, AlertPay, Flattr, plain IBAN, anything. Fix that and LilyPond dev  
crew will get some donations. Maybe not as much as anyone would like it to  
be, but surely better than nothing. Unless you think that 10$/10€ or such  
on the street is not even worth bending forward, because then, well, it's  
still like nothing I guess.

That being said: I'll try to be a better bug reporter, so don't hesitate to  
poke me whenever my feedbacks aren't as complete and elaborate as they  
should (because, you know, user often just don't know that you, the dev, is  
lacking necessary information in provided report for instance). Remember  
that sometimes casual reply/question directed to reporter (like "przemoc,  
mind that centered dynamics work different that in staff, so does the image  
below looks as it should?") can do wonders. Finally CCing reporters when  
adding issue to the tracker also should be done by default, yet so far it  
happened only once (and I have to hunt issues related to my reports myself  
and star them to get any updates)!

Please keep making LilyPond better. Cheers!