Re: simplify previous patch-set by special casing 2-line staves (issue 6506090)

On 2012/09/14 06:16:57, benko.pal wrote: main argument: I can't guess why the user chose a specific way of manipulating the staff and how (s)he interprets it, If the user writes \override #'staff-space = #0.5 he wants to scale things. If he writes \override #'line-positions = #'(-2 -1 0 1 2

Issues warning for empty note column extents (issue 6499105)

LGTM http://codereview.appspot.com/6499105/diff/1/lily/stem.cc File lily/stem.cc (left): http://codereview.appspot.com/6499105/diff/1/lily/stem.cc#oldcode814 lily/stem.cc:814: if (lh && robust_scm2int (lh->get_property ("duration-log"), 0) < 1) Removing this looks extremely sensible. It does c

Re: grob-object information

Am 11.09.2012 20:48, schrieb m...@mikesolomon.org: On 11 sept. 2012, at 17:48, Marc Hohl wrote: Hello list, for my work on the volta bracket inclusion for the new bar line interface, I need to know how the bars are ordered in (ly:grob-object grob 'bars). Please see the attached file. For th

Re: simplify previous patch-set by special casing 2-line staves (issue 6506090)

>> "dots in outer spaces" was inspired by your comment >> http://codereview.appspot.com/6488097#msg7 > > I was talking about a tab staff with larger staff-space, but with just > two staff-positions for each line. > > Anyone writing #'line-positions = #'(-10 -2 6 14) would be planning to > put a lot

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

On Thu, Sep 13, 2012 at 11:39:52PM +0200, David Kastrup wrote: > Graham Percival writes: > > I think we need to decide what direction we want the syntax to > > move in (or indeed, decide not to change the syntax at all!). > > I don't see the point in the repeated threats of locking me out from >

GOP2-5 - GLISS discussions

http://lilypond.org/~graham/gop/gop_6.html ** Summary We’ve gone over the same arguments a number of times, so let’s try to resolve them. Fluff will go on a new mailing lilypond-quacks mailing list. Serious proposals, if any, will go to lilypond-devel. Anybody with a serious proposal must be fami

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

> \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 the current definition, but avoid

laissez-vibrer-tie-beam.ly

Hey all, In the past couple days I've been getting changes in laissez-vibrer-tie-beam.ly almost every time I run the regtests on at least two different seemingly unrelated patch sets. Can anyone confirm this behavior? Cheers, MS ___ lilypond-devel ma

Re: simplify previous patch-set by special casing 2-line staves (issue 6506090)

Looks better than what is currently in master. On 2012/09/11 21:03:13, benko.pal wrote: "dots in outer spaces" was inspired by your comment http://codereview.appspot.com/6488097#msg7 I was talking about a tab staff with larger staff-space, but with just two staff-positions for each line. Any

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

Graham Percival writes: > On Thu, Sep 13, 2012 at 11:23:43PM -0300, Han-Wen Nienhuys wrote: >> On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup wrote: >> > Take a look at the \tempo command. Everybody and their dog tells me >> > that this is just what a musician wants in syntax. Whenever I do >>

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

On Thu, Sep 13, 2012 at 11:23:43PM -0300, Han-Wen Nienhuys wrote: > On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup wrote: > > Take a look at the \tempo command. Everybody and their dog tells me > > that this is just what a musician wants in syntax. Whenever I do > > significant work on the parse

PATCH: Countdown to 20120916

For 20:00 MDT Sunday September 16 Enhancement: Issue 2834 : Patch: Remove "Brace found at end of markup." warning in lexer - R 6506106 Issue 2717

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

On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup wrote: > Take a look at the \tempo command. Everybody and their dog tells me > that this is just what a musician wants in syntax. Whenever I do > significant work on the parser, \tempo pitches in with a few dozen > reduce/reduce errors and takes an

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

Graham Percival writes: > On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote: >> I am working hard to get expressions like { s4 s\< s1 s\! } parseable >> and recognizable without context, and obliterate the need to write - for >> anything except accent shorthands. This is pretty much

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

Graham Percival writes: > On Thu, Sep 13, 2012 at 08:56:26PM +0200, David Kastrup wrote: >> > Graham's and my suggestions are very restrictive, and we are just >> > playing around with possible syntax forms. >> >> How about considering how they are supposed to translate to and from >> Scheme? >

Outdated help2man; avoiding needing to "build" help2man.pl

In stepmake/stepmake/help2man-rules.make, I ran across the following: # We must invoke the generated $(outdir)/help2man script instead of # the help2man.pl source, which means that the scripts/build directory # must be built first. # # From the perlrun man-page: # # If the #! line does not c

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

>> David, please relax. I've typeset hundreds of pages with lilypond, >> including complicated piano and organ music; I don't lightly >> suggest syntactic stuff just to annoy you. > > We are getting most certainly nowhere if people don't even bother > understanding the technical points of my repl

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

On Thu, Sep 13, 2012 at 08:56:26PM +0200, David Kastrup wrote: > > Graham's and my suggestions are very restrictive, and we are just > > playing around with possible syntax forms. > > How about considering how they are supposed to translate to and from > Scheme? Woah. Is the syntax supposed to s

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

On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote: > I am working hard to get expressions like { s4 s\< s1 s\! } parseable > and recognizable without context, and obliterate the need to write - for > anything except accent shorthands. This is pretty much unavoidable if > you want to ge

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

Werner LEMBERG writes: >> [...] >> >> This is a quantum leap backwards in making LilyPond and Scheme >> expressions and variables and functions and arguments in the parser >> work and combine in a predictable manner. >> >> I am working hard on stopping the Scheme layer from being something >> ent

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

> [...] > > This is a quantum leap backwards in making LilyPond and Scheme > expressions and variables and functions and arguments in the parser > work and combine in a predictable manner. > > I am working hard on stopping the Scheme layer from being something > entirely different and interacting i

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

> I think there's still a need for a "event > after the previous duration", i.e. > >c'1-{ s4 s\< s2 <>\! } >c'1-{ s4 s\< s2 z\! } Mhmm. If we have -{ ... } with duration() + duration() + ... duration() = duration() then can have an arbitrary duration, which is ignored, a

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

Graham Percival writes: > I don't follow this. If we can produce an unambiguous "expansion" > of >c'1-<< s4 s\< s2 z\! >> > into ><< { c'1 } { s4 s\< s2 z\! } >> > then surely it can be expressed as music functions. \displayLilyMusic would have no chance reconstructing the input. The m

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

On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote: > Werner LEMBERG writes: > > >>> Actually, if we have -{ ... }, we don't need `z' at all: > >>> > >>> c'1-{ s4 s\< s2 s\! } This is a little bit unclear, since the final s\! would have the same duration as the previous s2, and thu

Re: [GLISS] differentiating pre/post/neutral commands

Francisco Vila writes: > 2012/9/13 Graham Percival : >> IIRC, the old style in lilypond was: >> (c c) > > Students whish this came back, I think. No matter how many times I > insist on it, they always ^H^H^H^H usually fail to remember the > correct form c( c) > > I find funny that the solution

Re: [GLISS] differentiating pre/post/neutral commands

2012/9/13 Graham Percival : > IIRC, the old style in lilypond was: > (c c) Students whish this came back, I think. No matter how many times I insist on it, they always ^H^H^H^H usually fail to remember the correct form c( c) I find funny that the solution they figured out to remember it, is the

Re: Git translation branch policy change: merge with and from stable/2.16

2012/9/13 John Mandereau : > I think the message that started this thread stated it clearly: "From > now on, translation branch at the repository on Savannah should no > longer be merged with master and into staging; instead, it should be > merged with stable/2.16." Well, right. >> but now I hav

Re: Git translation branch policy change: merge with and from stable/2.16

Il giorno gio, 13/09/2012 alle 10.44 +0200, Francisco Vila ha scritto: > 2012/9/8 Francisco Vila : > > Hi John, > > as things are today, can we keep doing the usual merges of > > translation-->staging and master-->translation? > > > > I still had no response, I think the message that started this

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

Werner LEMBERG writes: >>> Actually, if we have -{ ... }, we don't need `z' at all: >>> >>> c'1-{ s4 s\< s2 s\! } >>> >>> fully does the job, by registering the fact that a final `s' comes at >>> a moment which is equal the anchor's duration (sloppily formulated). >> >> If it does, so does >>

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

>> Actually, if we have -{ ... }, we don't need `z' at all: >> >> c'1-{ s4 s\< s2 s\! } >> >> fully does the job, by registering the fact that a final `s' comes at >> a moment which is equal the anchor's duration (sloppily formulated). > > If it does, so does > > << c'1 { s4 s\< s2 s\! } >>

Re: Git translation branch policy change: merge with and from stable/2.16

2012/9/13 Francisco Vila : > therefore if we want to > sync our translations to master, we have no way of knowing what to > translate and what not to. Sorry, I meant 'If we want to sync our translations with stable, after merging master (which is development branch) into translation we'll have n

Re: Git translation branch policy change: merge with and from stable/2.16

2012/9/8 Francisco Vila : > Hi John, > as things are today, can we keep doing the usual merges of > translation-->staging and master-->translation? > I still had no response, but now I have a request. The translation branch is still in 'stable' status. I think it should be kept so for a while, i.e

Re: 2.17.2 regtests

On 13 sept. 2012, at 10:17, David Kastrup wrote: > "m...@mikesolomon.org" writes: > >> On 13 sept. 2012, at 08:31, David Kastrup wrote: >> >>> "m...@mikesolomon.org" writes: >>> Just a note that Les Nereides will go back to its old state w/ the revert of the fix for 2801. I stil

Re: 2.17.2 regtests

- Original Message - From: "Keith OHara" To: ; "Phil Holmes" Sent: Thursday, September 13, 2012 3:14 AM Subject: Re: 2.17.2 regtests On Wed, 12 Sep 2012 12:59:25 -0700, Phil Holmes wrote: From: "Keith OHara" These changes are expected and explained in tracker issues 2493 N

Re: 2.17.2 regtests

"m...@mikesolomon.org" writes: > On 13 sept. 2012, at 08:31, David Kastrup wrote: > >> "m...@mikesolomon.org" writes: >> >>> Just a note that Les Nereides will go back to its old state w/ the >>> revert of the fix for 2801. I still need help debugging it, >>> especially w/ advice about profil

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

Graham Percival writes: > On Thu, Sep 13, 2012 at 07:29:35AM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > With that view (which is evidently not universal), it seems natural to >> > me to write the pitch and duration first, and then all the other >> > "special bits" that occur

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

Werner LEMBERG writes: >> I rather suggest to handle the -{ ... } construct specially, for >> example, to allow only `s' and Graham's proposed `z', together with >> constructions which work like articulations. > > Actually, if we have -{ ... }, we don't need `z' at all: > > c'1-{ s4 s\< s2 s\!

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

Graham Percival writes: > On Thu, Sep 13, 2012 at 07:18:50AM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > Here's a few imaginary ways of writing the same music: >> > \at 4 \< \at 1 \! c'1 >> > c'1 y4 y\< y z\! >> > c'1-<< y4 y\< y z\! >> >> > c'1-{ s4 s\< s2 z\! } >> >