Re: error while running make check (g++ 4.7.0): missing include of unistd.h

> I wanted to run regression tests and compare before and after a change. > However, I obtained the error given below after make -j8 CPU_COUNT=8 check > > I suspect this is because I am compiling with gcc/g++ 4.7.0 (coming > with Fedora 17) and its release notes say: > "Avoid polluting the global n

PATCH: Countdown to 20120731

For 20:00 MDT Tuesday July 31 (It can't be the end of July already: I haven't had time for June!) Defect: Issue 1650 : using multiple \header in a block prints only the latest items - R 6445053

Re: Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes.

David Kastrup writes: > Except that \-o can be a MARKUPCOMMAND but not a DASHED_KEY_WORD which > can't start with a dash as first character after the backslash. A > DASHED_KEY_WORD can contain digits, but this is mostly useless since you > can't use them except in INITIAL mode. > >>> One consequ

Re: Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes.

David Kastrup writes: > Graham Percival writes: > >> On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote: > >>> Being able to access every definition equally >>> well in every lexer mode is also an advantage. The word definition is >>> palindromic: iff a character sequence is a wo

Re: Set indent based on instrument name (issue 6457049)

David Kastrup writes: > "Phil Holmes" writes: > >> - Original Message - >> From: >> To: ; >> Cc: ; >> Sent: Sunday, July 29, 2012 9:16 PM >> Subject: Re: Set indent based on instrument name (issue 6457049) >> >> >>> On 2012/07/29 18:20:16, PhilEHolmes wrote: My first attempt at

Re: Set indent based on instrument name (issue 6457049)

"Phil Holmes" writes: > - Original Message - > From: > To: ; > Cc: ; > Sent: Sunday, July 29, 2012 9:16 PM > Subject: Re: Set indent based on instrument name (issue 6457049) > > >> On 2012/07/29 18:20:16, PhilEHolmes wrote: >>> My first attempt at coding in LilyPond. Treat me gently.

Re: Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes.

Graham Percival writes: > On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote: >> >> Forwarding this from the lilypond-auto list since this review concerns >> an important syntax change. GLISS material, in a manner. Consider it a >> proposal for word and command syntax across _all_ l

Re: Set indent based on instrument name (issue 6457049)

- Original Message - From: To: ; Cc: ; Sent: Sunday, July 29, 2012 9:16 PM Subject: Re: Set indent based on instrument name (issue 6457049) On 2012/07/29 18:20:16, PhilEHolmes wrote: My first attempt at coding in LilyPond. Treat me gently... I think we should be able to do bette

Re: Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes.

On Sun, Jul 29, 2012 at 10:15:10PM +0200, David Kastrup wrote: > > Forwarding this from the lilypond-auto list since this review concerns > an important syntax change. GLISS material, in a manner. Consider it a > proposal for word and command syntax across _all_ lexer modes. What's a "lexer mod

Re: Set indent based on instrument name (issue 6457049)

On 2012/07/29 18:20:16, PhilEHolmes wrote: My first attempt at coding in LilyPond. Treat me gently... I think we should be able to do better than just counting characters in a string. It should be possible calculating physical string width, shouldn't it? http://codereview.appspot.com/6457049

Re: Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes.

Forwarding this from the lilypond-auto list since this review concerns an important syntax change. GLISS material, in a manner. Consider it a proposal for word and command syntax across _all_ lexer modes. Reasonably simple, and somewhat surprisingly not requiring any changes in the entire .ly co

Set indent based on instrument name (issue 6457049)

Reviewers: dak, Graham Percival, Message: My first attempt at coding in LilyPond. Treat me gently... Description: An attempt to set the line indent based upon the instrument name. The simple use of instrumentName.length() to add to the indent seems odd, but works in practice. Not tested with

Re: Syntax change: REAL requires at least one digit before decimal point (issue 6446048)

This looks nice. Cleaner code, and continues to accept -.3\cm, for now. http://codereview.appspot.com/6446048/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: GOP2-3 - GLISS or not

Han-Wen Nienhuys writes: > On Tue, Jul 24, 2012 at 6:09 AM, Graham Percival > wrote: >> This summer hasn't been going as I'd hoped -- heh, who am I >> kidding, this whole year hasn't been going as I'd hoped. Anyway, >> we seem to have radically different concepts of what "input >> stabilization

Re: Email from Phil's patchy

Am 29.07.2012 11:16, schrieb David Kastrup: Marc Hohl writes: Am 29.07.2012 10:10, schrieb David Kastrup: Now it is true that we probably did not have a formal discussion of this in any rate, and you are probably quite keeping with some sort of de-facto standard and are in the unlucky positi

Re: Patchy email

Marc Hohl writes: > Am 28.07.2012 14:08, schrieb David Kastrup: >> [...] >> >> One thing that occured to me is that this contains a whole lot of public >> functions without any DOC string. No idea whether this might cause a >> problem for the documentation run, but it certainly is not much of a

Re: Email from Phil's patchy

Marc Hohl writes: > Am 29.07.2012 10:10, schrieb David Kastrup: > >> Now it is true that we probably did not have a formal discussion of >> this in any rate, and you are probably quite keeping with some sort >> of de-facto standard and are in the unlucky position of standing next >> when I am wak

Re: Patchy email

Am 28.07.2012 14:08, schrieb David Kastrup: [...] One thing that occured to me is that this contains a whole lot of public functions without any DOC string. No idea whether this might cause a problem for the documentation run, but it certainly is not much of a help for humans understanding the

Re: LilyPond developer&user meeting in Waltrop, August 24th to 28th

Rodolfo Zitellini writes: > Hi All! > is the meeting open to all users? Yes. We need to keep track of the head count and have to cater for accommodation/food accordingly, but that does not seem like much of a problem right now. > I would be very interested in coming, as I would love to learn a

Re: Email from Phil's patchy

Am 29.07.2012 10:10, schrieb David Kastrup: Marc Hohl writes: Am 29.07.2012 08:12, schrieb David Kastrup: "Phil Holmes" writes: Sorry, Marc. To do this completely, you will need to add the changed file to snippets/new. The files in snippets get over-written when we import from the LSR, s

Re: Email from Phil's patchy

Marc Hohl writes: > Am 29.07.2012 08:12, schrieb David Kastrup: >> "Phil Holmes" writes: >> >>> Sorry, Marc. To do this completely, you will need to add the changed >>> file to snippets/new. The files in snippets get over-written when we >>> import from the LSR, so this update would be lost.

Re: Email from Phil's patchy

Am 29.07.2012 08:12, schrieb David Kastrup: "Phil Holmes" writes: Sorry, Marc. To do this completely, you will need to add the changed file to snippets/new. The files in snippets get over-written when we import from the LSR, so this update would be lost. However, to make current git compile