PATCH: Countdown to 20121007

For 20:00 MDT Sunday October 7 Enhancement: Issue 2874 : Patch: Provide an \un function for turning overrides and sets into reverts and unsets - R 6588067 Issue 2875

Re: [talk] easy tuplets

"m...@mikesolomon.org" writes: > On 27 sept. 2012, at 19:38, Joseph Rushton Wakeling > wrote: > >> On 25/09/12 18:03, James wrote: >>> PAH! >>> >>> I bet Mike Solo would eat Ferneyhough for breakfast >> >> If you mean Mike Solomon then yes, his scores engraved with Lilypond >> are mightily imp

Re: allowing \f and \F

Graham Percival writes: > On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote: >> Graham Percival writes: >> >> > For example, what about my hated idea of splitting namespaces of >> > music fuctions and identifiers? I'm not fond of perl, but >> > something like this is unambiguous: >

[GLISS] syntax "features" nobody ever heard of.

xxx #'j #'k #'l = 7 #(format #t "xxx = ~a\n" xxx) xxx = #'() xxx #'j #'k #'l = 7 #(format #t "xxx = ~a\n" xxx) There is a bunch of stuff of that sort, most of that not really part of a reasonable framework, and unused to boot. -- David Kastrup ___ l

[proposal] easy triplets and tuplets - was [talk] easy tuplets

This is a proposal to move the triplet/tuplet discussion forward. There will be new commands to supplement (or eventually replace) the current \times command. 1. \tuplet n/m {} % does what \times does, but not so easily confused with \time % command. 2. \triplet {} % shorthand for current % \t

Patchy report

21:58:01 (UTC) Begin LilyPond compile, previous commit at 38a4081efa4a8ee2f5da780ca0ed2991627afc46 21:58:13 From git.savannah.gnu.org:/srv/git/lilypond 66f9cbc..e5a609e translation -> translation 21:58:30 Merged staging, now at:38a4081efa4a8ee2f5da780ca0ed2991627afc46 21:58:32

Re: Uses horizontal skylines in accidental placement (issue 6489086)

On Fri, Sep 28, 2012 at 8:56 AM, wrote: > http://codereview.appspot.com/6489086/diff/11/lily/accidental-placement.cc#newcode377 > lily/accidental-placement.cc:377: Real offset = > -ape->horizontal_skylines_[RIGHT].distance (left_skyline); > Both Mike and Janek thought the accidentals needed a bit

Re: Issue 2859: Provide \hide and \omit functions for transparent and void glyphs (issue 6575048)

On Wed, Oct 3, 2012 at 10:05 PM, wrote: > > Here are a few other suggestions: > 120 Moby Thesaurus words for "annihilate": [...] Let's call it \slay. After that we only need to create a Dragon grob and we'll have a fairy-tale. ;) ___ lilypond-deve

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

On Thu, Oct 4, 2012 at 4:57 PM, David Kastrup wrote: > Janek Warchoł writes: > >> On Thu, Oct 4, 2012 at 10:28 AM, David Kastrup wrote: >>> One rather sobering consequence is that any command accepting a grob >>> specification will _not_ be able to take a proper string generated in >>> Scheme us

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

Janek Warchoł writes: > On Thu, Oct 4, 2012 at 10:28 AM, David Kastrup wrote: >> [..] >> So if we want to avoid this kind of fallacy, there are a few ways out. >> I decided to take a reasonably safe route by foregoing lookahead for '.' >> unless explicitly told so. How does a function tell Lily

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

On Thu, Oct 4, 2012 at 10:28 AM, David Kastrup wrote: > [..] > So if we want to avoid this kind of fallacy, there are a few ways out. > I decided to take a reasonably safe route by foregoing lookahead for '.' > unless explicitly told so. How does a function tell LilyPond to look > for a string se

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

Werner LEMBERG writes: >> As a consequence of the current inconsistent \override syntax I >> already complained about recently, you will then also be able to >> write >> >> \override Bottom.TextSpanner bound-details left text = "rit." > > This I would probably drop (if possible). The dot shows

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

> As a consequence of the current inconsistent \override syntax I > already complained about recently, you will then also be able to > write > > \override Bottom.TextSpanner bound-details left text = "rit." This I would probably drop (if possible). The dot shows a hierarchy far better than a sp

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

Werner LEMBERG writes: >> \override Bottom.TextSpanner #'(bound-details left text) = "rit." >> >> as >> >> \override Bottom.TextSpanner bound-details.left.text = "rit." > > I like this. Actually, the recently unified word syntax plays a bit into it as well since otherwise "bound-details" wou

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

> \override Bottom.TextSpanner #'(bound-details left text) = "rit." > > as > > \override Bottom.TextSpanner bound-details.left.text = "rit." I like this. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mail

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

James writes: > On 4 October 2012 09:28, David Kastrup wrote: >> > .. > >> >> Using the symbol list form would have the advantage that >> >> \override TextSpanner #'(bound-details left text) = "rit." >> >> could equivalently be expressed as >> >> \override TextSpanner bound-details.left.

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

Hello, On 4 October 2012 09:28, David Kastrup wrote: > .. > > Using the symbol list form would have the advantage that > > \override TextSpanner #'(bound-details left text) = "rit." > > could equivalently be expressed as > > \override TextSpanner bound-details.left.text = "rit." > > and

Re: verify regression tests

Am 02.10.2012 23:24, schrieb Janek Warchoł: Hi Marc, On Sun, Sep 30, 2012 at 9:14 PM, Marc Hohl wrote: I got strange results with the regression tests, and studying the CG more carefully, I spotted some differences: http://lilypond.org/doc/v2.17/Documentation/contributor/regtest-comparison s

Re: [GLISS] turn xxx.yyy into ("xxx" "yyy")

Warming up a previous discussion because of new insights/ongoing work. David Kastrup writes: > Jan Nieuwenhuizen writes: > >> Werner LEMBERG writes: >> if we write xxx in LilyPond, this is considered to be a string. I want xxx.yyy.zzz to be a list of strings ("xxx" "yyy" "zzz"). >>>