Re: Patch upload and LSR

Marc Hohl hohlart.de> writes: > The testing process works fine on my local > machine, but 'make doc' fails due to some > syntax changes in the snippets. For example, > defaultBarType = "empty" will not work once > the patch is applied. > > and I wonder if these changes should be included > *in*

PATCH: Countdown to 20120918

For 20:00 MDT Tuesday September 18 Enhancement: Issue 2612 : Reverting previous: Excessive warnings for negative-spanning line spanner. - R 6492126 Issue 2793

Re: Sets TabVoice Stem height to ##f (issue 6303065)

mike apollinemike.com apollinemike.com> writes: > >> > On 2012/06/12 12:49:45, dak wrote: > >> > > http://codereview.appspot.com/6303065/diff/10003/lily/grob.cc > >> > > File lily/grob.cc (right): > >> > > > >> > > > > http://codereview.appspot.com/6303065/diff/10003/lily/grob.cc#newcode472 > >>

Re: Fix for /Documentation/snippets/text#text-center-text-below-hairpin-dynamics

2012/9/12 Thomas Morley : > Hi, > > please have a look at the fix for > http://lilypond.org/doc/v2.16/Documentation/snippets/text#text-center-text-below-hairpin-dynamics > imported from LSR: > http://lsr.dsi.unimi.it/LSR/Item?id=233 > making possible to add DynamicText to the NoteColumn where the H

Re: [GLISS] - alternative viewpoint

2012/9/16 David Kastrup : > This is the developer list, after all. Hey, I have the Dragon Book in my bedside table, I can give a language to my daughter for her birthday, and still find some things difficult. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com __

Patch upload and LSR

Hello list, I am still working on the barline interface ... The testing process works fine on my local machine, but 'make doc' fails due to some syntax changes in the snippets. For example, defaultBarType = "empty" will not work once the patch is applied. So I looked at http://lilypond.org/doc

Re: Gets vertical skylines from grob stencils (issue 5626052)

http://codereview.appspot.com/5626052/diff/114002/lily/skyline.cc File lily/skyline.cc (right): http://codereview.appspot.com/5626052/diff/114002/lily/skyline.cc#newcode111 lily/skyline.cc:111: if (start_height != end_height) Does anyone know the reason for this change? For some unusual input (

Re: [GLISS] non-timed or non-musical events "z" "y"

Werner LEMBERG writes: >> \tempo does not have "optional arguments" but rather several quite >> different forms of argument lists, and then some rather weird form >> of numeric range echoed nowhere else in the syntax. > > BTW, could you suggest a better syntax for \tempo which looks > similar to

Re: [GLISS] - alternative viewpoint

Janek Warchoł writes: > Hi, > > On Sat, Sep 15, 2012 at 10:20 AM, David Kastrup wrote: >> Yup. Here is my multi-stage plan for that: > > Great! It's inspiring to see such a big plan :) > >> b) our C++ engravers announce to the type system (and via that, to the >> documentation) which context p

Re: [GLISS] - alternative viewpoint

Janek Warchoł writes: > On Sat, Sep 15, 2012 at 11:35 AM, David Kastrup wrote: >> >> You mean, currently we basically see the default error message from the >> parser generator. Improving this involves basically accepting errors in >> input and acting on them by putting out hand-tailored messag

Re: [GLISS] - alternative viewpoint

On Sat, Sep 15, 2012 at 11:35 AM, David Kastrup wrote: > > You mean, currently we basically see the default error message from the > parser generator. Improving this involves basically accepting errors in > input and acting on them by putting out hand-tailored messages. > > Currently, the parser

Re: [GLISS] - alternative viewpoint

Hi, On Sat, Sep 15, 2012 at 10:20 AM, David Kastrup wrote: > Yup. Here is my multi-stage plan for that: Great! It's inspiring to see such a big plan :) > b) our C++ engravers announce to the type system (and via that, to the > documentation) which context properties they read, modify and writ

Re: [GLISS] - alternative viewpoint

On Fri, Sep 14, 2012 at 6:56 PM, Phil Holmes wrote: > What does get me more concerned is how hard it is to find some of the > correct ways of tweaking output. Using voice.SomeValue (or is it > Voice.someValue) when it should be staff.Somevalue (or was it > Staff.someValue) frequently results in n

Re: GOP2-5 - GLISS discussions

On Fri, Sep 14, 2012 at 10:05 PM, Marc Hohl wrote: > The whole discussion reminds me of the way songs are written in the > music band I play – David, do you remind the story? I think I told it > even before Graham arrived, so it was just you, Janek, and my wife > at Waltrop listening to my clumsy

info reader and lilypond snippets

Today I've noticed that `Selected Snippets' sections, if viewed with the TTY info viewer, only show the code example but not the description text. It seems that a snippet's `texidoc' block is dropped if not in TeX or HTML mode while the *.texi files are generated. Can this be fixed somehow?

useless `See also' index entries

Folks, not sure whether this has been already reported. Looking at http://lilypond.org/doc/v2.17/Documentation/notation/lilypond-index.html I see around 600 completely useless entries containing `See also'. This problem doesn't exist in the PDF version. In case this can't be easily fixed

Re: glissando in LP 2.16

[CCing devel instead of user, since this is a development contribution.] > you find attached 8 files: one .txt file containing seven > documentation entries and seven .ly files for each entry. I've now edited your contribution; attached is a patch. Documentation team, please comment and integra