Re: [proposal] easy triplets and tuplets - Draft 3

On Wed, Oct 10, 2012 at 12:00 AM, David Kastrup wrote: >> I'm not sure about the validity of your conclusion. Writing tuplets >> is such a central element of inputting music that a special treatment >> is probably justified, even at the cost of hardwiring. > > We are talking about writing \tuplet

PATCH: Countdown to 20121011

For 20:00 MDT Thursday October 11th Documentation: Issue 2858 : Document \shape music function - R 6561064 Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's

Re: Context.Grob considered as symbol list

On 12-10-09 12:59 PM, David Kastrup wrote: Since this patch series is a bit humongous for reviewing in a single Rietveld review and it would take two months to get every patch in sequence through an individual review, I am putting this series out as an experiment to the list. Let's see how we fa

Re: Clefs and transposition [was: Re: [proposal] easy triplets and tuplets - Draft 3]

On 10/10/2012 12:08 AM, Joseph Rushton Wakeling wrote: Yes, definitely a bad idea. Use 8va. brackets instead when you want to send everything up an octave like that. It was fine for _you_ because you wrote it and knew what you wanted anyway, but it would have probably been confusing for an

Clefs and transposition [was: Re: [proposal] easy triplets and tuplets - Draft 3]

On 10/09/2012 05:23 PM, Janek Warchoł wrote: As for transposing clefs, i play guitar a bit myself, and i have once typeset a piece using both G and G_8 clefs. Maybe it was a bad idea, but for me it was perfectly fine. Yes, definitely a bad idea. Use 8va. brackets instead when you want to

Re: [proposal] easy triplets and tuplets - Draft 3

Werner LEMBERG writes: >> In contrast, : is being used for chord and tremolo notation. It has >> no relation to music function arguments. The price for using it >> would be making \tuplet a reserved word specially treated in the >> parser and dealing with the interference of : with its other >>

Re: [proposal] easy triplets and tuplets - Draft 3

On Tue, Oct 9, 2012 at 11:30 PM, Werner LEMBERG wrote: >>> much happier with >>> \tuplet 3:2 { } >>> meaning the same thing as >>> \times 2/3 { } >> >> I think I like this idea. > > Me too. However, this requires surgery in the parser, so I think this > feature gets postponed until someone (heh

Re: [proposal] easy triplets and tuplets - Draft 3

> In contrast, : is being used for chord and tremolo notation. It has > no relation to music function arguments. The price for using it > would be making \tuplet a reserved word specially treated in the > parser and dealing with the interference of : with its other > meanings in the parser, and

Re: [proposal] easy triplets and tuplets - Draft 3

On Tue, Oct 9, 2012 at 5:36 PM, David Kastrup wrote: > Janek Warchoł writes: >> i've found a reason why i could support "reversed" tuplet ratio: if we >> decide to allow arbitrary integer durations (so that a3 would mean a >> third of the whole note), it would make more sense to have { a3 b6 } >>

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

Werner LEMBERG wrote >> \accidentalStyle StaffGroup.voice > > This is my preferred form. However, some time ago we decided (more or > less) to say e.g. > > \clef "bass" > > In the light of your syntax improvements/simplifications, shouldn't we > start to use > > \clef bass > > instead, ma

Re: [proposal] easy triplets and tuplets - Draft 3

>> much happier with >> \tuplet 3:2 { } >> meaning the same thing as >> \times 2/3 { } > > I think I like this idea. Me too. However, this requires surgery in the parser, so I think this feature gets postponed until someone (hehe, David :-) has time to analyze possible side effects. Wern

Re: Still alive

Hey Mike! On Tue, Oct 9, 2012 at 10:19 AM, m...@mikesolomon.org wrote: > Hey list, > > Just a quick ping to let you know that I'm not dead - I've been swamped w/ > work recently and just got engaged so I'm planning out a wedding (w00t!). Whoah, you're FAST! Congratulations!! :) When and where

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

I'm just skimming the discussion (the patch is big and non-trivial, so i will have problems reviewing it), but i spotted one interesting sentence... On Tue, Oct 9, 2012 at 10:38 AM, wrote: > We can get rid of a _lot_ of #' style thingies with this patch series. A!!! So this is the patch i'

Re: [proposal] easy triplets and tuplets - Draft 3

Graham Percival writes: > On Tue, Oct 09, 2012 at 09:45:09AM +0200, Francisco Vila wrote: >> So, \tuplet y/x with the exact meaning of \times x/y is less confusing >> because it's not "times" vs "time" anymore, and the straightforward >> fraction is just "music without the maths". So, I predict a

Re: [proposal] easy triplets and tuplets - Draft 3

On Tue, 9 Oct 2012, Graham Percival wrote: On Tue, Oct 09, 2012 at 09:45:09AM +0200, Francisco Vila wrote: So, \tuplet y/x with the exact meaning of \times x/y is less confusing because it's not "times" vs "time" anymore, and the straightforward fraction is just "music without the maths". So,

Re: [proposal] easy triplets and tuplets - Draft 3

On Tue, Oct 09, 2012 at 09:45:09AM +0200, Francisco Vila wrote: > So, \tuplet y/x with the exact meaning of \times x/y is less confusing > because it's not "times" vs "time" anymore, and the straightforward > fraction is just "music without the maths". So, I predict a widespread > adoption. Do we

[PATCH 10/16] Add symbol-list-or-music? predicate

This is of interest for commands like \hide which accept either music (to see an override) or a grob specification like Accidental or Voice.Accidental. --- scm/c++.scm |5 + scm/lily.scm |1 + 2 files changed, 6 insertions(+) diff --git a/scm/c++.scm b/scm/c++.scm index d627481..12c3

[PATCH 06/16] Allow LilyPond strings to stand in for symbols when parsing

Bare words and quote-enclosed words meeting word syntax can now be used when a function argument expects to see a symbol. --- lily/parser.yy | 384 +++- 1 file changed, 239 insertions(+), 145 deletions(-) diff --git a/lily/parser.yy b/lily/pars

[PATCH 04/16] Factor SCM_IDENTIFIER out from embedded_scm_arg*

SCM_IDENTIFIER indicates "active Scheme" introduced with $ that is subject to copying and reinterpretation. While the parser had its own *_IDENTIFIER category for everything interpreted specially, the fallback SCM_IDENTIFIER itself never needed special or different treatment from material generate

[PATCH 09/16] Allow the string "xxx.yyy" to parse as a symbol list

This changes the parser to let xxx.yyy be a valid way of specifying a function argument required to be #'(xxx yyy). --- lily/parser.yy | 48 ++-- 1 file changed, 34 insertions(+), 14 deletions(-) diff --git a/lily/parser.yy b/lily/parser.yy index 6a08

[PATCH 12/16] Make \alterBroken, \hide, \omit, \overrideProperty, \shape take unquoted Context.Grob specs

This changes the syntax of the named commands to accept Voice.Accidental and similar specifications without any quoting. --- ly/music-functions-init.ly | 100 +++- 1 file changed, 44 insertions(+), 56 deletions(-) diff --git a/ly/music-functions-init.ly b/

[PATCH 01/16] Assignments can't contain literal lyric music (wrong lexer mode)

Since assignments can't happen in lyrics mode (only in INITIAL mode or the initial music mode), there is no point in supporting non-mode-switching items on the right side of assignments that can only occur in lyrics mode. --- lily/parser.yy |1 - 1 file changed, 1 deletion(-) diff --git a/lil

[PATCH 16/16] Let \overrideProperty accept nested properties

--- ly/music-functions-init.ly | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/ly/music-functions-init.ly b/ly/music-functions-init.ly index ef93fab..c32645a 100644 --- a/ly/music-functions-init.ly +++ b/ly/music-functions-init.ly @@ -712,10 +712,10 @@ of

[PATCH 02/16] parser.yy: FRACTION does not require a closed expression before it

FRACTION items can't trail any other valid expression without separating '*' or similar, so the argument list before them does not need to be of "closed" type. --- lily/parser.yy |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lily/parser.yy b/lily/parser.yy index 19

[PATCH 14/16] convert-ly rule for \alterbroken, \accidentalStyle, \overrideProperty

This is required since not all of the old call forms can be automatically recognized anymore, in particular not when the Scheme-only form #"Context.GrobName" is being used. --- python/convertrules.py | 13 + 1 file changed, 13 insertions(+) diff --git a/python/convertrules.py b/pyth

Context.Grob considered as symbol list

Since this patch series is a bit humongous for reviewing in a single Rietveld review and it would take two months to get every patch in sequence through an individual review, I am putting this series out as an experiment to the list. Let's see how we fare.

[PATCH 03/16] parser.yy: make is_regular_identifier match the lexer definition

is_regular_identifier checks now for valid identifiers employing the definition of words that is also used in the lexer: letters, and characters outside of the ASCII range, interspersed with single - and _ characters. --- lily/parser.yy | 27 +++ 1 file changed, 15 insert

[PATCH 13/16] Change \accidentalStyle to get a symbol list as argument

This changes the syntax of \accidentalStyle to accept specs like Voice.piano-cautionary . --- ly/property-init.ly | 29 + 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/ly/property-init.ly b/ly/property-init.ly index 3a88098..28a13e3 100644 --- a/ly/p

[PATCH 07/16] Add symbol-list? predicate

--- scm/c++.scm |3 +++ scm/lily.scm |1 + 2 files changed, 4 insertions(+) diff --git a/scm/c++.scm b/scm/c++.scm index 444a3e9..d627481 100644 --- a/scm/c++.scm +++ b/scm/c++.scm @@ -48,6 +48,9 @@ (define-public (boolean-or-symbol? x) (or (boolean? x) (symbol? x))) +(define-publi

[PATCH 11/16] Replace the rather fuzzy list-or-symbol? with symbol-list-or-symbol?

list-or-symbol? was previously used in the meaning of symbol-list-or-symbol? only, and there is no point in not checking the list members for actually being symbols, in order to avoid ugly surprises later. --- ly/music-functions-init.ly |2 +- ly/property-init.ly|2 +- scm/c++.scm

[PATCH 08/16] Allow property and grob paths to be constructed from strings

--- lily/parser.yy | 242 1 file changed, 175 insertions(+), 67 deletions(-) diff --git a/lily/parser.yy b/lily/parser.yy index 270961f..6a087d8 100644 --- a/lily/parser.yy +++ b/lily/parser.yy @@ -381,6 +381,7 @@ If we give names, Bison c

[PATCH 05/16] Let \accidentalStyle detect its optional context argument by looking at its letter case

This is a fishy stopgap measure to let \accidentalStyle able to distinguish #'Voice "default" from "default" alone while we generate symbols from from #'Voice as well as "default". If the first letter is uppercase, the symbol is considered to be a context specification. --- ly/property-init.ly |

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

http://codereview.appspot.com/6635050/diff/7002/ly/music-functions-init.ly File ly/music-functions-init.ly (right): http://codereview.appspot.com/6635050/diff/7002/ly/music-functions-init.ly#newcode105 ly/music-functions-init.ly:105: (ly:input-warning location (_ "not a spanner name, `~a'") name

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

LGTM. http://codereview.appspot.com/6635050/diff/7002/ly/music-functions-init.ly File ly/music-functions-init.ly (right): http://codereview.appspot.com/6635050/diff/7002/ly/music-functions-init.ly#newcode105 ly/music-functions-init.ly:105: (ly:input-warning location (_ "not a spanner name, `~a'

Re: [proposal] easy triplets and tuplets - Draft 3

Janek Warchoł writes: > wow, many more emails arrived! Let me send my thoughts written in the > meantime, and go back offline for a few hours. > > i've found a reason why i could support "reversed" tuplet ratio: if we > decide to allow arbitrary integer durations (so that a3 would mean a > third

Re: [proposal] easy triplets and tuplets - Draft 3

Hi, wow, many more emails arrived! Let me send my thoughts written in the meantime, and go back offline for a few hours. i've found a reason why i could support "reversed" tuplet ratio: if we decide to allow arbitrary integer durations (so that a3 would mean a third of the whole note), it would

Re: Still alive

Ian Hulin writes: > On 09/10/12 09:19, m...@mikesolomon.org wrote: >> Hey list, >> >> Just a quick ping to let you know that I'm not dead - I've been >> swamped w/ work recently and just got engaged so I'm planning out a >> wedding (w00t!). > > CONGRATULATIONS TO YOU BOTH >

Re: Still alive

On 09/10/12 09:19, m...@mikesolomon.org wrote: > Hey list, > > Just a quick ping to let you know that I'm not dead - I've been swamped w/ > work recently and just got engaged so I'm planning out a wedding (w00t!). CONGRATULATIONS TO YOU BOTH (to Mike (Han) Solo and Prince

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

Werner LEMBERG writes: >> \accidentalStyle StaffGroup.voice > > This is my preferred form. However, some time ago we decided (more or > less) to say e.g. > > \clef "bass" > > In the light of your syntax improvements/simplifications, shouldn't we > start to use > > \clef bass > > instead, mak

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

> \accidentalStyle StaffGroup.voice This is my preferred form. However, some time ago we decided (more or less) to say e.g. \clef "bass" In the light of your syntax improvements/simplifications, shouldn't we start to use \clef bass instead, making data in double quotes really user string

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

On 2012/10/09 10:03:59, t.daniels_treda.co.uk wrote: d...@gnu.org: Tuesday, October 09, 2012 9:38 AM > I think I'll prepare a radical convert-ly-only patch on top of this > patch series that demonstrates what "now valid" syntax we _could_ be > using/advertising as input if we wanted to. It'

Re: [Lilypond-auto] Patchy report

Il giorno mar, 09/10/2012 alle 09.57 +0200, David Kastrup ha scritto: > John Mandereau writes: > > > Hi, > > > > I quote some of the logs below... > > Il giorno mar, 09/10/2012 alle 00.33 +, grenoui...@lilynet.net ha > > scritto: > >> 21:58:01 (UTC) Begin LilyPond compile, previous commit at

Re: [proposal] easy triplets and tuplets - Draft 3

Benkő Pál writes: > 2012/10/9 David Kastrup : >> Benkő Pál writes: >> >>> 2012/10/9 David Kastrup : I don't really think that people consider \times and \scaleDurations as closely related (and their naming choice is also totally different), so I don't think that there will be much

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

d...@gnu.org: Tuesday, October 09, 2012 9:38 AM > Here is the rub: what we are currently talking about is a choice between > several convert-ly rules that all lead to valid programs after this > change. > > Whether you write > \override TextSpanner #'(bound-details left stencil-align-dir-y) = #

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 David Kastrup : > Benkő Pál writes: > >> 2012/10/9 David Kastrup : >>> I don't really think that people consider \times and \scaleDurations as >>> closely related (and their naming choice is also totally different), so >>> I don't think that there will be much of an opportunity confusing

Re: [proposal] easy triplets and tuplets - Draft 3

On 2012-10-09 11:14, Francisco Vila wrote:> 2012/10/9 Benkő Pál : >> 2012/10/9 Francisco Vila : >>> When I learned how to read music, triplets were taught to me as >>> "always shrinking" groups and you see a "3" but there is an implicit >>> "2" so we have 3:2. Only the numerator is printed by con

Re: Still alive

"m...@mikesolomon.org" writes: > On 9 oct. 2012, at 11:39, Trevor Daniels wrote: > >> >> m...@mikesolomon.org wrote Tuesday, October 09, 2012 9:19 AM >> >>> Just a quick ping to let you know that I'm not dead - I've been >>> swamped w/ work recently and just got engaged so I'm planning out a >

Re: Still alive

m...@mikesolomon.org: Tuesday, October 09, 2012 10:29 AM On 9 oct. 2012, at 11:39, Trevor Daniels wrote: >> >> m...@mikesolomon.org wrote Tuesday, October 09, 2012 9:19 AM >> >>> Just a quick ping to let you know that I'm not dead - I've been swamped w/ >>> work recently >>> and just got eng

Re: Still alive

On 9 oct. 2012, at 11:39, Trevor Daniels wrote: > > m...@mikesolomon.org wrote Tuesday, October 09, 2012 9:19 AM > >> Just a quick ping to let you know that I'm not dead - I've been swamped w/ >> work recently and just got engaged so I'm planning out a wedding (w00t!). > > Congratulations!

Re: [proposal] easy triplets and tuplets - Draft 3

Benkő Pál writes: > 2012/10/9 David Kastrup : >> The concept used for printing/grouping tuplets is different than the >> concept used for scaling the time. That's what makes \times such a >> confusing interface. >> >> The pure scaling alone is available as \scaleDurations. I have no beef >> wit

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 Benkő Pál : > 2012/10/9 Francisco Vila : >> When I learned how to read music, triplets were taught to me as >> "always shrinking" groups and you see a "3" but there is an implicit >> "2" so we have 3:2. Only the numerator is printed by convention. >> >> Thus, if you write >> >> \times 2

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 David Kastrup : > The concept used for printing/grouping tuplets is different than the > concept used for scaling the time. That's what makes \times such a > confusing interface. > > The pure scaling alone is available as \scaleDurations. I have no beef > with it using 2/3 as input, and

Re: [proposal] easy triplets and tuplets - Draft 3

Francisco Vila writes: > 2012/10/9 David Kastrup : >> Francisco Vila writes: >> >>> 2012/10/9 Keith OHara : Currently, everyone who thinks of a triplet as a 3:2 ratio, 3 notes in the usual time for 2, suffers similar confusion when trying to remember \times 2/3. Triplets are usua

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 Francisco Vila : > When I learned how to read music, triplets were taught to me as > "always shrinking" groups and you see a "3" but there is an implicit > "2" so we have 3:2. Only the numerator is printed by convention. > > Thus, if you write > > \times 2/3 { b16 b b b b b } > > or > >

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 David Kastrup : > Francisco Vila writes: > >> 2012/10/9 Keith OHara : >>> Currently, everyone who thinks of a triplet as a 3:2 ratio, 3 notes in the >>> usual time for 2, suffers similar confusion when trying to remember \times >>> 2/3. Triplets are usually written with a simple 3, but

Re: Still alive

m...@mikesolomon.org wrote Tuesday, October 09, 2012 9:19 AM > Just a quick ping to let you know that I'm not dead - I've been swamped w/ > work recently and just got engaged so I'm planning out a wedding (w00t!). Congratulations! Does she _really_ know what she's letting herself in for ;) >

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

On 2012/10/09 08:14:55, t.daniels_treda.co.uk wrote: : Tuesday, October 09, 2012 8:36 AM > so I'd crank open another convert-ly rule to turn those into > \accidentalStyle piano-cautionary > as well. Which makes for worse backward-compatibility of scores. > > What do people prefer to see? A

Re: [proposal] easy triplets and tuplets - Draft 3

On Mon, 8 Oct 2012, Keith OHara wrote: Martin Tarenskeen zonnet.nl> writes: I am not in favour of allowing different commands \times 2/3 and \tuplet3/2 to do the same job. My voice would go to: just keep \times x/y the wayit is. I can't see what makes 3/2 easier than 2/3. And having the ch

Still alive

Hey list, Just a quick ping to let you know that I'm not dead - I've been swamped w/ work recently and just got engaged so I'm planning out a wedding (w00t!). I'll be back in the swing of things around mid-November if not sooner. Cheers, MS ___ lilypon

Re: [proposal] easy triplets and tuplets - Draft 3

Francisco Vila writes: > 2012/10/9 Keith OHara : >> Currently, everyone who thinks of a triplet as a 3:2 ratio, 3 notes in the >> usual time for 2, suffers similar confusion when trying to remember \times >> 2/3. Triplets are usually written with a simple 3, but 4-note-tuplets are >> often desig

Re: [proposal] easy triplets and tuplets - Draft 3

David Kastrup writes: > Graham Percival writes: > >> On Mon, Oct 08, 2012 at 11:49:39PM +0100, Trevor Daniels wrote: >>> >>> David Kastrup wrote Monday, October 08, 2012 10:45 PM >>> >>> > Thomas Morley writes: >>> > >>> >>> In this case, i >>> >>> think that \tuplet 2/3 is better than \tupl

Re: Make arguments like Context.GrobName accessible as symbol lists(issue 6635050)

: Tuesday, October 09, 2012 8:36 AM > On 2012/10/09 05:04:50, lemzwerg wrote: >> http://codereview.appspot.com/6635050/diff/1/Documentation/de/notation/pitches.itely#newcode1529 >> Documentation/de/notation/pitches.itely:1529: \accidentalStyle >> StaffGroup."voice" >> This looks strange. I don't

Re: [proposal] easy triplets and tuplets - Draft 3

Graham Percival wrote Tuesday, October 09, 2012 12:12 AM > On Mon, Oct 08, 2012 at 11:49:39PM +0100, Trevor Daniels wrote: >> >> David Kastrup wrote Monday, October 08, 2012 10:45 PM >> >> > Thomas Morley writes: >> > >> >>> In this case, i >> >>> think that \tuplet 2/3 is better than \tuple

Re: [proposal] easy triplets and tuplets - Draft 3

Martin Tarenskeen writes: > On Mon, 8 Oct 2012, Trevor Daniels wrote: > >> >> David Kastrup wrote Monday, October 08, 2012 10:45 PM >> >> >>> Thomas Morley writes: >>> [...] > So, i believe that LilyPond shouldn't always follow her users' > intuition, even if they are professional m

Re: [Lilypond-auto] Patchy report

John Mandereau writes: > Hi, > > I quote some of the logs below... > Il giorno mar, 09/10/2012 alle 00.33 +, grenoui...@lilynet.net ha > scritto: >> 21:58:01 (UTC) Begin LilyPond compile, previous commit at >> c7a3623a056891d48b13fe14fd6ee042ac666822 >> 21:58:27 Merged staging, now at:

Re: [proposal] easy triplets and tuplets - Draft 3

"Keith OHara" writes: > duplet = > #(define-music-function (parser location d music) > ((ly:duration? #f) ly:music? ) > (if d > #{\tuplet 2 $d $music #} > #{\tuplet 2 $music #} )) Just a note here: this can be done quite more concisely by writing duplet = #(define-music-function

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 Keith OHara : > Currently, everyone who thinks of a triplet as a 3:2 ratio, 3 notes in the > usual time for 2, suffers similar confusion when trying to remember \times > 2/3. Triplets are usually written with a simple 3, but 4-note-tuplets are > often designated 4:3 for clarity, while Li

Re: Make arguments like Context.GrobName accessible as symbol lists (issue 6635050)

Reviewers: lemzwerg, Message: On 2012/10/09 05:04:50, lemzwerg wrote: LGTM, without testing, and without really understanding the change. However, simplifications and generalizations are always a good thing. http://codereview.appspot.com/6635050/diff/1/Documentation/de/notation/pitches.itel

Re: Doc: improve documentation of Bézier curves (2858) (issue 6561064)

On 2012/10/09 05:44:52, J_lowe wrote: Are there too many 'subs' here? No. This is the standard level 5 heading. See http://www.lilypond.org/doc/v2.17/Documentation/contributor/sectioning-commands I only mention it because the headings are bold _italic_ which really jars on the eye when it'