Re: Two possible "ugly bugs"

2013-10-23 Thread Gilberto Agostinho
Hi Keith,

Thanks for your reply, for the workarounds and for the report. Also, I
totally understand your point concerning my 2)

Take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Two-possible-ugly-bugs-tp152775p152858.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Two possible "ugly bugs"

2013-10-23 Thread Gilberto Agostinho
Hi Phil,

Thanks for your reply. As I am new to bug reporting, I sometimes still get
confused about it (all my other reports have been filled by others after I
posted them in the User forum, or someone directly asked me to post
something at the bug tracker). I will always report bugs via the gmane
interface here, never directly.

Take care,
Gilberto



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Two-possible-ugly-bugs-tp152775p152857.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Two possible "ugly bugs"

2013-10-22 Thread Keith OHara
Gilberto Agostinho  gmail.com> writes:

> 1) Some ugly positioning when using \pitchedTrill: 

This was from an intentional change to place things as close as they fit
  http://code.google.com/p/lilypond/issues/detail?id=2527
but it should have come with padding.

I added http://code.google.com/p/lilypond/issues/detail?id=3630
A good workaround is
 \override TrillPitchGroup #'horizon-padding = #0.10


> 2) This one I am a bit less sure if it is not happening due to some 
misuse 
> of mine. I am trying to get completely flat beams by using \override 
> Beam.concaveness = #+inf.0 (as far as I understand, the higher the value 
of 
> the concaveness the flatter are the beams). So it works well for almost 
> every group of notes, EXCEPT when there is a note and a rest beamed 
> together: 

> {  \override Beam.concaveness = #+inf.0 
> \time 12/8 
>   a'8[ r d'] e8[ r r] a,8[ r r] a'''8[ r r] } 

I hesitate to enter a bug report for this.
The 'concaveness' is meant to describe the pattern of note-heads where 
traditionally we prefer horizontal beams.  The rest moves in response to 
the beam, so for a beam between a single note and rest I am not surprised 
that 'concaveness'  has no effect -- the single note cannot have a concave 
pattern so 'concaveness' is not checked.

Maybe Beam.damping = +inf.0 should make the beam horizontal for a rest and 
note beamed together (it does not work currently).  
You can use
  \once\override Beam.positions = #'(0 . 0)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond


Re: Two possible "ugly bugs"

2013-10-21 Thread Phil Holmes
"Gilberto Agostinho"  wrote in message 
news:loom.20131021t190155-...@post.gmane.org...
Here are two possible little bugs (of type ugly) that do not look well 
IMO.

If you give me green light, I would happily add them to our Issue Tracker
myself.



Please don't.  If you do want to help out with bug handling, we would 
welcome your assistance as a member of the Bug Squad, and would add you to 
the tracker as a member to allow you to add bugs correctly.


--
Phil Holmes
Bug Squad 




___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond