Re: report a programming error when trying to align on empty parent (issue 7533046)

https://codereview.appspot.com/7533046/diff/3001/lily/self-alignment-interface.cc File lily/self-alignment-interface.cc (right): https://codereview.appspot.com/7533046/diff/3001/lily/self-alignment-interface.cc#newcode63 lily/self-alignment-interface.cc:63: programming_error ("cannot align on se

Re: Allows slurs to break at barlines. (issue 7424049)

> "At the start of the second alternative, we have an extra slur > start, the slur ends on beat 2, a phrasing slur starts on beat 3 and > at the end of the alternative, there is an extra slur end". Huh. > Works better with "detached". In this sentence, \phantom works quite nicely :-) This is st

Re: Issue 2924: Doc: \startMeasureCount and \stopMeasureCount needs documenting (issue 7678047)

LGTM https://codereview.appspot.com/7678047/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Documents make-partial-ellipse-stencil (issue 7497046)

LGTM as long as that "Paris" typo is fixed. https://codereview.appspot.com/7497046/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allows slurs to break at barlines. (issue 7424049)

David Kastrup writes: > "Trevor Daniels" writes: > >>> What kind of word would people pick when describing a score on the >>> phone? For a single occurence, "interrupted" is likely a good >>> candidate, but five times in a row something catchier would likely >>> win. Probably "split" has a sli

Re: Allows slurs to break at barlines. (issue 7424049)

"Trevor Daniels" writes: > David Kastrup wrote Wednesday, March 20, 2013 10:38 PM > > >> "m...@mikesolomon.org" writes: >> >>> On 20 mars 2013, at 09:26, Trevor Daniels wrote: >>> At the risk of prolonging the bike-shedding, here's my take. For me, the key consideration is to provid

Re: Allows slurs to break at barlines. (issue 7424049)

David Kastrup wrote Wednesday, March 20, 2013 10:38 PM > "m...@mikesolomon.org" writes: > >> On 20 mars 2013, at 09:26, Trevor Daniels wrote: >> >>> At the risk of prolonging the bike-shedding, here's my take. For >>> me, the key consideration is to provide an easily remembered name >>> that

Re: Allows slurs to break at barlines. (issue 7424049)

"m...@mikesolomon.org" writes: > On 20 mars 2013, at 09:26, Trevor Daniels wrote: > >> >> m...@mikesolomon.org >> >>> I completely agree. It's just that "fake" in English means false >> or counterfeit. It needs another word, just don't know what yet. >> unchained? free? >> >> At the risk of

Re: reorganize self_alignment_interface (issue 7768043)

Hi all, after some thinking i've come to a conclusion that we should keep this patch as is - just a simple rewrite of self-alignment-interface, without lots of new features and generalizations: they should be done in another patch. Doing so should make git history more logical: there will be a c

Re: PATCHES: Countdown foe 23 March - 12:00 GMT

Hi hackers, On Wed, Mar 20, 2013 at 8:46 PM, James wrote: > Hello, 3259 > > Janek Warchol Patch: report a programming e

Re: Caches the interior skylines of vertical axis groups and systems. (issue 7185044)

Hey all, Following up to my comment on the tracker, I'd like to not push this until everyone has had a chance to think through David's e-mails about 2.18. I anticipate this needing 2-3 months of user testing to catch and fix any bugs. Given that this is my first big patch since August, it'll li

Re: Allows slurs to break at barlines. (issue 7424049)

> Even better, how about: > > \anderston Uhmm, no. :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: Countdown foe 23 March - 12:00 GMT

Hello, *Countdown – March 23th 2013 – 19:00 GMT* * * * * * * * * 3238 Build Julien Rioux Push Patch: Fixup default prefix

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 mars 2013, at 09:26, Trevor Daniels wrote: > > m...@mikesolomon.org > >> I completely agree. It's just that "fake" in English means false or >> counterfeit. It needs another word, just don't know what yet. unchained? >> free? > > At the risk of prolonging the bike-shedding, here's

Re: Allows slurs to break at barlines. (issue 7424049)

Am 20.03.2013 19:10, schrieb Werner LEMBERG: > But there are millions of TeX users who are used to \phantom. And I > believe that a lot of Lilypond users are TeX users also. This means > that those users are already acquainted with this command and can > easily deduce what it does. I think knowi

Re: Allows slurs to break at barlines. (issue 7424049)

"m...@mikesolomon.org" writes: > Even better, how about: > > \anderston > > The Anderston pedestrian bridge is a real life example of what we're > talking about. > > http://en.m.wikipedia.org/wiki/M8_Bridge_to_Nowhere#section_3 > > I'm totally for this - it would be fantastic if people called the

Re: Allows slurs to break at barlines. (issue 7424049)

>> But TeX is separate enough from LilyPond that I actually like >> \phantom rather well for this purpose. > > Anything like phantom, fake and co doesn't sit right in > English. [...] But there are millions of TeX users who are used to \phantom. And I believe that a lot of Lilypond users are T

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 mars 2013, at 18:25, "m...@mikesolomon.org" wrote: > Sent from my iPhone > > On 20 mars 2013, at 16:38, David Kastrup wrote: > >> Werner LEMBERG writes: >> I think any further proposals should _definitely_ explain how to write the given example g f e d( \repe

Re: Allows slurs to break at barlines. (issue 7424049)

Sent from my iPhone On 20 mars 2013, at 16:38, David Kastrup wrote: > Werner LEMBERG writes: > >>> I think any further proposals should _definitely_ explain how to write >>> the given example >>> >>> g f e d( >>> \repeat { c d) e f ( } >>> \alternatives { >>> { g) a b( a \fake) } >>> { \fa

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 mars 2013, at 14:26, d...@gnu.org wrote: > Yet another possibility would be \inner but that implies a hierarchy. > More accurate would be \continued. > > https://codereview.appspot.com/7424049/ I like \interrupted Cheers, MS ___ lilypond-devel

Re: Allows slurs to break at barlines. (issue 7424049)

Werner LEMBERG writes: >> I think any further proposals should _definitely_ explain how to write >> the given example >> >> g f e d( >> \repeat { c d) e f ( } >> \alternatives { >> { g) a b( a \fake) } >> { \fake( e) d c( d \fake) } >> { \fake( d) c d( e } >> } >> d c) d c > > Hmm. It's

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 March 2013 15:01, m...@mikesolomon.org wrote: > > I don't completely follow what you're saying above - could you say it > another way? I don't follow this whole developers discussion about choosing the best command name for the users. Please correct me if I'm wrong. 1. After this has been

Re: Allows slurs to break at barlines. (issue 7424049)

> I think any further proposals should _definitely_ explain how to write > the given example > > g f e d( > \repeat { c d) e f ( } > \alternatives { > { g) a b( a \fake) } > { \fake( e) d c( d \fake) } > { \fake( d) c d( e } > } > d c) d c Hmm. It's not clear to me why lilypond can't han

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 mars 2013, at 14:52, David Kastrup wrote: > "m...@mikesolomon.org" writes: > >> On 20 mars 2013, at 14:26, d...@gnu.org wrote: >> >>> Yet another possibility would be \inner but that implies a hierarchy. >>> More accurate would be \continued. >>> >>> https://codereview.appspot.com/74240

Re: Allows slurs to break at barlines. (issue 7424049)

James writes: > Hello > > On 20 March 2013 13:40, Werner LEMBERG wrote: > > >> More accurate would be \continued. > >> > >> https://codereview.appspot.com/7424049/ > > > > I like \interrupted > > I can live with both \continued and \interrupted. > > Is that with two

Re: Allows slurs to break at barlines. (issue 7424049)

Werner LEMBERG writes: >> If the design needs it at both ends of the repeated block you could >> consider a single keyword parameter for the function, >> >> o \slurInRepeat #'begin - to appear at the end of the block and >> indicate you're starting a new, partial slur and >> >> o \slurInRepeat

Re: Allows slurs to break at barlines. (issue 7424049)

"m...@mikesolomon.org" writes: > On 20 mars 2013, at 14:26, d...@gnu.org wrote: > >> Yet another possibility would be \inner but that implies a hierarchy. >> More accurate would be \continued. >> >> https://codereview.appspot.com/7424049/ > > I like \interrupted I considered that but self-censo

Re: Allows slurs to break at barlines. (issue 7424049)

Hello On 20 March 2013 13:40, Werner LEMBERG wrote: > >> More accurate would be \continued. > >> > >> https://codereview.appspot.com/7424049/ > > > > I like \interrupted > > I can live with both \continued and \interrupted. > Is that with two 'r's or two 'p's or both? ... are you sure? James

Re: Allows slurs to break at barlines. (issue 7424049)

>> More accurate would be \continued. >> >> https://codereview.appspot.com/7424049/ > > I like \interrupted I can live with both \continued and \interrupted. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mail

Re: Allows slurs to break at barlines. (issue 7424049)

And yet another would be \silent as a sort of negative variant of \visual. https://codereview.appspot.com/7424049/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allows slurs to break at barlines. (issue 7424049)

> If the design needs it at both ends of the repeated block you could > consider a single keyword parameter for the function, > > o \slurInRepeat #'begin - to appear at the end of the block and > indicate you're starting a new, partial slur and > > o \slurInRepeat #'complete - to appear at the b

Re: Allows slurs to break at barlines. (issue 7424049)

Yet another possibility would be \inner but that implies a hierarchy. More accurate would be \continued. https://codereview.appspot.com/7424049/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-deve

Re: Allows slurs to break at barlines. (issue 7424049)

On 2013/03/20 12:35:37, Ian Hulin (gmail) wrote: \fake and \broken are concise but "feel" wrong, implying something's wrong with something else but the name doesn't describe it. Without pointing out what makes you think they feel wrong, that's not helpful. I think a function name where we've

Re: Allows slurs to break at barlines. (issue 7424049)

On 20 March 2013 12:35, wrote: > \fake and \broken are concise but "feel" wrong, implying something's > wrong with something else but the name doesn't describe it. > > I think a function name where we've got to resort to being clever maybe > indicate we're trying to solve the wrong problem: we're

Re: Allows slurs to break at barlines. (issue 7424049)

\fake and \broken are concise but "feel" wrong, implying something's wrong with something else but the name doesn't describe it. I think a function name where we've got to resort to being clever maybe indicate we're trying to solve the wrong problem: we're trying to make the name short at the exp

Re: R shorthand

Am 20.03.2013 09:55, schrieb David Kastrup: Jan-Peter Voigt writes: [...] (ly:make-duration (inexact->exact (/ (log den)(log 2))) ... That's a terribly broken thing to do. inexact->exact does not change the value one bit, only its interpretation. A number considered to be _approxima

Re: R shorthand

Jan-Peter Voigt writes: [...] > (ly:make-duration (inexact->exact (/ (log den)(log 2))) ... That's a terribly broken thing to do. inexact->exact does not change the value one bit, only its interpretation. A number considered to be _approximated_ by integer*2^power is now considered to b

Re: Allows slurs to break at barlines. (issue 7424049)

"m...@mikesolomon.org" writes: > On 20 mars 2013, at 07:50, David Kastrup wrote: > >> "m...@mikesolomon.org" writes: >> >>> The word "fake" still doesn't sit right with me... There is nothing >>> fake about the slur: >>> >>> { a \fake ( b c d ) } >> >> Mike, that code does not even make any

Re: Allows slurs to break at barlines. (issue 7424049)

m...@mikesolomon.org > I completely agree. It's just that "fake" in English means false or > counterfeit. It needs another word, just don't know what yet. unchained? > free? At the risk of prolonging the bike-shedding, here's my take. For me, the key consideration is to provide an easily

Re: R shorthand

Am 20.03.2013 02:16, schrieb David Kastrup: Kieren MacMillan writes: Hi Shane, What happens when we need an awkward length R like R1*12/8*14? I'm not sure what you mean by "awkward length"… I'm suggesting that R (with no duration given) should give you a one-measure multi-measure rest, r