Re: Eliminates pure-print-callbacks list (issue 7300082)

It does looks reasonable to put the promise that a stencil does not change with line-spacing, near the definiton fo the stencil, rather than in a separate list. Just one question. If we override the stencil \override NoteHead #'stencil = #stencil-notehead then formerly LilyPond would avoid draw

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

The reorganization looks reasonable. { g4\> g'_"pico" g' g\! } Assuming for simplicity that this is set in one line, one VerticalAxisGroup contains all the graphical objects as 'elements'. At some point the Y-offset of TextScript "pico" is evaluated, calling aligned_side() and then calc_out

PATCH: Countdown to 20130219 - 19:00 GMT

*Countdown – 20130216 – 12:00 GMT* * * * * * * * * * * 3165<http://code.google.com/p/lilypond/issues/detail?id=3165&q=label%3APatch-countdown&sort=patch&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified> Enhancement David Kastrup push Patch: Mul

Re: Standardizes use of empty extents in pure heights and skylines. (issue 7310075)

Joe disallowed buildings of zero width in his skylines for reasons given only as "avoiding numerical inaccuracies". Could be something like depending on the +/- sign of 0.0, or depending on advancement through loops when we increment by a building width. It seems a bit better, for consistency, t

Conflicting dots and rests with partcombine and lyrics

Hello! I'm typesetting a SATB score on two staves. I want to use partcombine so that I can write the parts for each voice the way they supposed to be sung. It's well known that partcombine doesn't work with the lyrics, so I tried this workaround by Daniel E. Moctezuma http://comments.gm

Re: Coding practices

> Quite a good source of good coding is the Linux kernel IMHO. And probably most of the GNU projects, e.g. `Emacs' or `coreutils'. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Coding practices

> I would suggest to code like that Chinese programmer, so that any > questions regarding the code will get a plausible "Let's see, what > was I thinking here? Wait, I remember this was a bit more complex, > be back in a minute." reply, with your "partner" actually being able > to be back in a min

Re: Coding practices

Han-Wen Nienhuys writes: > On Sat, Feb 16, 2013 at 3:46 PM, David Kastrup wrote: > >> I was talking about "reasonable documenting and coding practice". >> That does not involve how to structure things. As I said, we are >> talking about post-1960s Pascal coding, and he tried his best to >> stil

Re: Coding practices

Le 16 févr. 2013 à 15:15, m...@mikesolomon.org a écrit : > I've heard from friends that Google has codified standards for how code > should be written. What are these standards like? Style guides for Google-originated open-source projects ___

Re: Coding practices

On Sat, Feb 16, 2013 at 3:15 PM, m...@mikesolomon.org wrote: Rather than letting this continue to be problematic, I'd like to establish a sort of GLISS for LilyPond coding style. We would discuss certain conventions in the codebase to see where commonalities lie in the codebas

Re: Coding practices

On Sat, Feb 16, 2013 at 3:46 PM, David Kastrup wrote: >>> If you want an example of reasonable documenting and coding practice, >>> take tex.web (it is public domain), run it through weave and pdftex >>> and peruse significant extracts of the resulting PDF. >> >> While tex.web is a beautiful examp

Re: Coding practices

Han-Wen Nienhuys writes: > On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: > >> If you want an example of reasonable documenting and coding practice, >> take tex.web (it is public domain), run it through weave and pdftex >> and peruse significant extracts of the resulting PDF. > > While t

Re: Coding practices

On 16 févr. 2013, at 16:06, Han-Wen Nienhuys wrote: > On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: >>> After reading over David's most recent e-mails to the list, it is >>> clear to me that there is a coding-practice debt in LilyPond. >>> Standards of how and when to do certain things

Re: Coding practices

On Fri, Feb 15, 2013 at 10:44 PM, David Kastrup wrote: >> After reading over David's most recent e-mails to the list, it is >> clear to me that there is a coding-practice debt in LilyPond. >> Standards of how and when to do certain things are not shared across >> all programmers, and things that s

Re: Coding practices

On 15 févr. 2013, at 23:44, David Kastrup wrote: > "m...@mikesolomon.org" writes: > >> Hey all, >> >> After reading over David's most recent e-mails to the list, it is >> clear to me that there is a coding-practice debt in LilyPond. >> Standards of how and when to do certain things are not sha

Re: [Lilypond-auto] Issue 3182 in lilypond: Patch: Defuse the obfuscated Scheme programming contest

Marc Hohl writes: > Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com: >> Status: Started >> Owner: d...@gnu.org >> Labels: Type-Enhancement Patch-new >> >> New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme >> programming contest >> http://code.google.com/p/lilypond/issues/de

Re: Standardizes use of empty extents in pure heights and skylines. (issue 7310075)

https://codereview.appspot.com/7310075/diff/12001/lily/separation-item.cc File lily/separation-item.cc (right): https://codereview.appspot.com/7310075/diff/12001/lily/separation-item.cc#newcode156 lily/separation-item.cc:156: // If these two uses of inf combine, leave the empty extent. The descr