Re: modern-straight-flag and convert-ly

robert edge projectmalam...@gmail.com writes: Using a newly installed version of 2.16 on Linux x86-64 convert-ly is changing: \override Stem #'flag = #modern-straight-flag to: \override Flag #'print = #modern-straight-flag which does not produce the correct output and does not generate

Re: modern-straight-flag and convert-ly

David Kastrup d...@gnu.org wrote in message news:87zjx1y7l8@fencepost.gnu.org... robert edge projectmalam...@gmail.com writes: Using a newly installed version of 2.16 on Linux x86-64 convert-ly is changing: \override Stem #'flag = #modern-straight-flag to: \override Flag #'print =

Re: modern-straight-flag and convert-ly

Phil Holmes m...@philholmes.net writes: I'd like Mike to corroborate that this should be #'stencil, and then we need to check at least our own code base for bad occurences. I have no really good plan how to deal with files that have already been broken by that rule. git grep -e Flag

Re: \powerChords produces superscript 5 that is too large

2013/4/14 Eluze elu...@gmail.com: Greg Swinford wrote I'm not top posting. \version 2.14.2 newPowerChordSymbol = { c g -\markup { \super 5 } } chExceptions = #( append ( sequential-music-to-chord-exceptions newPowerChordSymbol #t) ignatzekExceptions) music = \chordmode {c:7

Re: \powerChords produces superscript 5 that is too large

2013/4/14 Thomas Morley thomasmorle...@googlemail.com BTW, Greg refers to 2.14.2, though, it's the same with 2.17.15. I think it's a legitimate feature request. And I lean to agree with him. Thanks Greg and Harm, added the issue: https://code.google.com/p/lilypond/issues/detail?id=3314

Google code hosting: some problem with status updating

Bug Squad The tracker keeps listing issues marked as verified as issues to be verified. Are you experiencing the same? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \powerChords produces superscript 5 that is too large

Thomas Morley wrote 2013/4/14 Eluze lt; eluzew@ gt;: Greg Swinford wrote I'm not top posting. \version 2.14.2 newPowerChordSymbol = { c g -\markup { \super 5 } } chExceptions = #( append ( sequential-music-to-chord-exceptions newPowerChordSymbol #t) ignatzekExceptions)

Re: Google code hosting: some problem with status updating

Federico Bruni fedel...@gmail.com wrote in message news:CAPjDBpqjiOA2ghfmQ8Z=rdfjsp8xpvgo_0-z6hdmf1kytih...@mail.gmail.com... Bug Squad The tracker keeps listing issues marked as verified as issues to be verified. Are you experiencing the same? Yes - it looks like the status as recorded on

Re: point and click implementation

Phil Holmes m...@philholmes.net wrote in message news:kk988a$5qc$1...@ger.gmane.org... ArnoldTheresius arnold.we...@siemens.com wrote in message news:1365684685208-144321.p...@n5.nabble.com... and there are at least some *fundamental* enhancement requests for lilypad. I'm not sure if they're

Re: Google code hosting: some problem with status updating

Federico Bruni-5 wrote Bug Squad The tracker keeps listing issues marked as verified as issues to be verified. Are you experiencing the same? indeed! Eluze -- View this message in context:

Re: Google code hosting: some problem with status updating

Federico Bruni fedel...@gmail.com writes: Bug Squad The tracker keeps listing issues marked as verified as issues to be verified. Are you experiencing the same? I've seen this kind of lag occasionally for various status changes. When updates to the respective databases are not (as usual)

Re: point and click implementation

Phil Holmes m...@philholmes.net writes: The lilypad delivered with 2.17.16 is now updated to be the one in GitHub. I've got an updated version on my PC that supports the Find function better - the found string is highlighted and the window scrolls to the string that's been found. I'll likely

-dpreview doesn't take brackets into account

As you can see in this example: http://lilypond.org/ly-examples/tab-example.png the bottom part of the bracket has been cut off because of -dpreview. Can you change -dpreview so that brackets are taken into account? Thanks Federico ___ bug-lilypond

Re: point and click implementation

David Kastrup d...@gnu.org wrote in message news:874nf9xkf1@fencepost.gnu.org... Phil Holmes m...@philholmes.net writes: The lilypad delivered with 2.17.16 is now updated to be the one in GitHub. I've got an updated version on my PC that supports the Find function better - the found string

Re: -dpreview doesn't take brackets into account

2013/4/14 Federico Bruni fedel...@gmail.com: As you can see in this example: http://lilypond.org/ly-examples/tab-example.png the bottom part of the bracket has been cut off because of -dpreview. Can you change -dpreview so that brackets are taken into account? I think this isn't as simple as

Re: point and click implementation

2013/4/14 Phil Holmes m...@philholmes.net: David Kastrup d...@gnu.org wrote in message Could you doublecheck that the region is not off-by-one? The textedit links have changed the column definition with If I use this test file: {c4 d e f g a b c} Then clicking on the first note brings

Re: point and click implementation

Janek Warchol janek.lilyp...@gmail.com wrote in message news:CANYDDpoL0Ciag6MHc=zhpruktn+g75fhhhufrmsvrda2fvs...@mail.gmail.com... 2013/4/14 Phil Holmes m...@philholmes.net: David Kastrup d...@gnu.org wrote in message Could you doublecheck that the region is not off-by-one? The textedit links

Re: point and click implementation

Phil Holmes m...@philholmes.net writes: David Kastrup d...@gnu.org wrote in message news:874nf9xkf1@fencepost.gnu.org... Phil Holmes m...@philholmes.net writes: The lilypad delivered with 2.17.16 is now updated to be the one in GitHub. I've got an updated version on my PC that supports

Re: \powerChords produces superscript 5 that is too large

2013/4/14 Eluze elu...@gmail.com: what's the intention to make the 5 bigger than the other numbers? Eluze I found http://lilypond-s-support-for-tablatures.3383434.n2.nabble.com/Power-chords-td5524246.html#a5524246 and https://codereview.appspot.com/2686041/ but no discussion about the size.