<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.gnu.lilypond.devel">
    <title>gmane.comp.gnu.lilypond.devel</title>
    <link>http://blog.gmane.org/gmane.comp.gnu.lilypond.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54495"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54489"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54485"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54475"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54470"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54469"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54468"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54467"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54459"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54448"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54441"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54437"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54434"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54423"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54422"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54416"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54414"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54409"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54371"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54370"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54495">
    <title>PATCHES: Countdown for June 21 - 06:00 GMT</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54495</link>
    <description>&lt;pre&gt;*Countdown -- June 21 -- 06:00 GMT* *
* *
* *
* *
*





3411 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3411&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup push Patch: Mostly cosmetic 
simplifications in woodwind diagrams and library





3413 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3413&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup countdown Patch: Remove patches from elisp
3412 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3412&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement Jean-Charles M countdown Patch: Use &amp;lt; at &amp;gt;dots{} instead of 
... in manuals





2910 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=2910&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Ugly Keith O'Hara review problem with 'outside-staff-padding





*Patch moved to 'Needs work' this countdown* 



3255 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3255&amp;amp;q=label%3APatch-new&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Critical keith O'Hara Needs Work \with-dimensions doesn't affect the 
overall size of a TextScript   Regression

&lt;/pre&gt;</description>
    <dc:creator>James</dc:creator>
    <dc:date>2013-06-18T08:02:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54489">
    <title>NR incorrect now?</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54489</link>
    <description>&lt;pre&gt;The NR says "In accordance with standard typesetting rules, a natural sign 
is printed before a sharp or flat if a previous accidental on the same note 
needs to be canceled. To change this behavior, set the extraNatural property 
to f in the Staff context."

Following http://code.google.com/p/lilypond/issues/detail?id=1481 I believe 
this is no longer exact.  Anyone disagree?

--
Phil Holmes
&lt;/pre&gt;</description>
    <dc:creator>Phil Holmes</dc:creator>
    <dc:date>2013-06-17T13:30:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54485">
    <title>standard music font layout</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54485</link>
    <description>&lt;pre&gt;
Some interesting activities on music fonts:

  http://www.smufl.org/


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-06-16T18:41:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54475">
    <title>Documentation policy</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54475</link>
    <description>&lt;pre&gt;If you look at 
http://lilypond.org/doc/v2.17/Documentation/notation/proportional-notation 
and the third example down, there's a single piece of music repeated three 
times but with different options on spacing.  I've noticed a number of 
similar examples.  I'd find it clearer if the music were assigned to a 
variable, and the examples used that variable - it would be absolutely clear 
what was changed between the examples.  It would also save a little space. 
Is there a reason for not doing this?

--
Phil Holmes
&lt;/pre&gt;</description>
    <dc:creator>Phil Holmes</dc:creator>
    <dc:date>2013-06-16T10:13:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54470">
    <title>Clef positioning and key signatures</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54470</link>
    <description>&lt;pre&gt;If I shift the position of the clef, and make an associated change to the 
position of middle C, I'd expect the key signature to move, but it doesn't. 
Am I not doing something, doing something wrong, or is this a bug?

{ \key f \major c'1 }
{ \set Staff.clefPosition = #0 \set Staff.middleCPosition = #-4 \key f 
\major c'1 }

--
Phil Holmes

_______________________________________________
lilypond-devel mailing list
lilypond-devel&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
&lt;/pre&gt;</description>
    <dc:creator>Phil Holmes</dc:creator>
    <dc:date>2013-06-15T11:22:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54469">
    <title>Use &lt; at &gt;dots{} instead of ... in manuals (issue 10296043)</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54469</link>
    <description>&lt;pre&gt;Reviewers: dak, Trevor Daniels, Graham Percival,

Message:
Follow up of issue 3392


Description:
Use &amp;lt; at &amp;gt;dots{} instead of ... in manuals

  Web: intro and helpus
  Doc: usage, extenting and learning

Please review this at https://codereview.appspot.com/10296043/

Affected files:
   M Documentation/extending/programming-interface.itely
   M Documentation/extending/scheme-tutorial.itely
   M Documentation/included/compile.itexi
   M Documentation/included/helpus.itexi
   M Documentation/learning/common-notation.itely
   M Documentation/learning/tweaks.itely
   M Documentation/usage/lilypond-book.itely
   M Documentation/usage/running.itely
   M Documentation/usage/suggestions.itely
   M Documentation/usage/updating.itely
   M Documentation/web/introduction.itexi
&lt;/pre&gt;</description>
    <dc:creator>lilyfan&lt; at &gt;orange.fr</dc:creator>
    <dc:date>2013-06-15T10:49:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54468">
    <title>Ignoring note value when spacing notes and rests</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54468</link>
    <description>&lt;pre&gt;I'm setting a piece of late 16th century music (it's in Musica Transalpina), 
and at this time notes and rests tended to occupy a space determined by 
their fitment on the page, rather than their note value.  I've read the 
section of the NR on proportional spacing, which does exactly the opposite 
of what I want.  Is there a way to force essentially uniform spacing, 
regardless of note value?

TIA

--
Phil Holmes
&lt;/pre&gt;</description>
    <dc:creator>Phil Holmes</dc:creator>
    <dc:date>2013-06-15T10:35:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54467">
    <title>PATCHES: Countdown for June 18 - 06:00 GMT</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54467</link>
    <description>&lt;pre&gt;*Countdown -- June 18 -- 06:00 GMT* *
* *
* *
* *
*





3406 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3406&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup Push Patch: convert-ly: Flag.transparent 
and Flag.color inherit from Stem
3386 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3386&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Critical Keith O'Hara Push Output crops staff braces when produced 
with -dpreview   Regression
3383 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3383&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Defect David Kastrup Push old-straight-flag + smaller Stem.thickness 
gives no output and huge over










3411 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3411&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup countdown Patch: Mostly cosmetic 
simplifications in woodwind diagrams and library










*Patched moved from countdown* 



3255 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3255&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Critical keith O'Hara No status \with-dimensions doesn't affect the 
overall size of a TextScript   Regression

&lt;/pre&gt;</description>
    <dc:creator>James</dc:creator>
    <dc:date>2013-06-15T08:02:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54459">
    <title>Question about log file names during lilypond-book compilation formake doc</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54459</link>
    <description>&lt;pre&gt;Hello,

This morning during a patch test I had a patch fail during make doc.

The error log refers to a snippet name, which I know is generated fresh
each time.

However when I grep part of the snippet name that includes the snippet
number I come up (in this case anyway) with a few different files

so find . | grep snippet-names-1703404056

gives me:

./show-3255/out/lybook-db/snippet-names-1703404056-violin-1.notes
./show-3255/out/lybook-db/snippet-names-1703404056.ly
./show-3255/out/lybook-db/snippet-names-1703404056.log
./show-3255/out/lybook-testdb/snippet-names-1703404056-violin-1.notes
./show-3255/out/lybook-testdb/snippet-names-1703404056.ly
./show-3255/out/lybook-testdb/snippet-names-1703404056.log

This list includes the *.log file where I find the error message.

However, the error message doesn't necessarily tell me (at least that
clearly) where the error occurred and more often than not it is very hard
to pin down when using multi core make.

But in this case, I can see that the snippet number is very specific and
while the *.ly file just points to a few dozen other explicit *.ly files,
does the fact that this list contains *violin* as part of the output mean
anything that might help in this case (just as a for instance)?

I cannot find any *.ly file with violin-1 so was wondering where this file
is generated from or if it is always generated as part of lilypond-book
when it builds doc and so I'd _always_ see this *violin-1.notes file.

Thanks for any insights.

James
_______________________________________________
lilypond-devel mailing list
lilypond-devel&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
&lt;/pre&gt;</description>
    <dc:creator>James</dc:creator>
    <dc:date>2013-06-13T10:00:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54448">
    <title>Accidental not changing colour</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54448</link>
    <description>&lt;pre&gt;2 years ago I was provided with the following code. The idea 
was to change de colour when having an  accidental. This in the 
new version is not working. 

Can anybody help?

Thanks

________________________________________
\version "2.16.0"
\include "color.ly"

staffViolin = \new Staff {

\coloraccidentals

.....

}

\score{
&amp;lt;&amp;lt;
\staffViolin
&amp;gt;&amp;gt;
}

_______________________
color.ly

\version "2.16.0"

#(define (accidentals? note symbol)
(let ((p (ly:music-property note 'pitch)))
(and (ly:pitch? p)
(equal? (ly:pitch-alteration p) symbol))))

coloraccidentals = #(define-music-function (parser location music) (ly:music?)
(music-map
 (lambda (event)
   (if (eq? 'EventChord (ly:music-property event 'name))
       (map (lambda (note)
      (if (accidentals? note SHARP)
  (ly:music-set-property! note 'tweaks (list (cons 'color red))) note)
      (if (accidentals? note FLAT)
  (ly:music-set-property! note 'tweaks (list (cons 'color cyan))) note))
    (ly:music-property event 'elements))) event) music))
&lt;/pre&gt;</description>
    <dc:creator>Evian</dc:creator>
    <dc:date>2013-06-12T20:36:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54441">
    <title>Images from Liedboek with attribution</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54441</link>
    <description>&lt;pre&gt;Hi,

I put some images up at the public url

    https://plus.google.com/b/109917054452640897824/109917054452640897824/posts/jPRaUgF34ma

and I hope to get more publicity and possibly a donation for LilyPond.
This is a major publication.  There are three separate books, besides
this one there is one for choir and one for organ/piano accompaniment.

Currently, 140,000 copies are being printed.  1st (40,000) and
2nd (50,000) editions are already sold out.  3rd edition (50,000)
with many corrections is planned for mid-July.

Jan

&lt;/pre&gt;</description>
    <dc:creator>Jan Nieuwenhuizen</dc:creator>
    <dc:date>2013-06-12T18:09:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54437">
    <title>PATCHES: Countdown for June 15 - 06:00 GMT</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54437</link>
    <description>&lt;pre&gt;*Countdown -- June 12 -- 06:00 GMT* *
* *
* *
* *
*










3403 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3403&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Enhancement Benko Pal push Patch: follow up issue 2470: make 
Completion_rest_engraver aware of completionUnit
3402 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3402&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup push Patch: Completion_heads_engraver 
should declare input property completionUnit
3401 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3401&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Defect David Kastrup push Parser error with void function in music list





3406 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3406&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup countdown Patch: convert-ly: 
Flag.transparent and Flag.color inherit from Stem
3386 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3386&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Critical Keith O'Hara countdown Output crops staff braces when 
produced with -dpreview   Regression
3383 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3383&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Defect David Kastrup countdown old-straight-flag + smaller 
Stem.thickness gives no output and huge over
3255 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3255&amp;amp;q=label%3APatch-countdown&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Summary%20Modified&amp;gt; 
Critical keith O'Hara countdown \with-dimensions doesn't affect the 
overall size of a TextScript   Regression

&lt;/pre&gt;</description>
    <dc:creator>James</dc:creator>
    <dc:date>2013-06-12T07:32:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54434">
    <title>LilyPond developer meeting Waltrop 2013</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54434</link>
    <description>&lt;pre&gt;
As announced in January, I'd like to offer a developer meeting in
Waltrop this year again.  Due to the limited meeting and accommodation
space (limit is about 20 participants) and the time frame, things like
introductory courses for LilyPond would not make much sense: the focus
will be on having discussions, getting serious work done, figuring out
where to go next, and so on.

I sincerely hope that the topic of releasing 2.18 will _not_ be relevant
any more and we can instead make some progress on the next steps.
Things that might warrant working on are

Guilev2 (seriously)
Markup redesign
Page breaker
MusicXML discussions
Discussions about EU project feasibility (I tried getting something
organized a few months ago, but it basically died from lack of immediate
recognizable interest from commercial entities).

Reports about the last meeting can be found at
&amp;lt;URL:http://news.lilynet.net/?The-LilyPond-Report-28&amp;gt;.  Information
about travel and place (please don't get confused by last year's dates!)
is still at &amp;lt;URL:http://news.lilynet.net/?LilyPond-meeting-in-Waltrop&amp;gt;.

The date this time around will be August 2013, Friday 16th to Tuesday
20th, with the possibility to arrive Thursday 15th late in the day for
people who'd otherwise miss stuff early Friday.

The proposed date coincides with the "Dattelner Kanalfest"
&amp;lt;URL:http://www.kanalfest.de/&amp;gt; which is the big competition (next town)
of the "Waltroper Parkfest" we had running parallel to the conference
last year.  It still provides a reasonably close festival and
entertainment for potentially not-just-LilyPond interested attendants or
accompaniment, though with more focus on music and less on small arts
like jugglers and stuff.

But since it is next town, it will not suck dry external accommodation
in Waltrop like the Parkfest did last year.  So it should be easier for
people preferring to stay at some hotel or similar to find something not
too far away.  Camping on the ground and sleep-ins are of course
possible like last year and I expect most participants to make use of
that.

As mentioned above, most travellers will aim for Dortmund (through bus
or train) though some international travellers will likely have
Düsseldorf as their first destination in Germany.

&lt;/pre&gt;</description>
    <dc:creator>David Kastrup</dc:creator>
    <dc:date>2013-06-11T20:11:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54423">
    <title>Busy Developers' Summary 10: we have a blog!</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54423</link>
    <description>&lt;pre&gt;Hi,

it's been a while since the previous summary - sorry for that (keep in
mind that anyone can write them, don't feel shy about it!).

So, this one will span a month and starts with some old stuff:

David is truly heroic in his struggle to get PostScript rendering as
consistent as possible (issue 2658).  If i were him, i'd probably blow
my computer up already, and had sent death threats to people
responsible for this hideous situation.  He had paused the work to
make sure that he won't loose his sanity, but i'm sure he'll go back
to it when the time comes.  I'm already using one of his patches in my
custom LilyPond build and i'm very satisfied by the results. Kudos to
David!

Work is (was?) being done on better supporting point-and-click,
particularly on Windows:
http://lists.gnu.org/archive/html/lilypond-devel/2013-05/msg00027.html
but also on Linux:
http://code.google.com/p/lilypond/issues/detail?id=3354

Again, there was some discussion about issues blocking stable release:
http://lists.gnu.org/archive/html/lilypond-devel/2013-06/msg00031.html

Frescobaldi 2.0.10 has been released

Urs Liska sent a revised version of his paper about benefits of using
text input in music publishing, something that can have a significant
infulence on LilyPond acceptance in academic circles:
http://lists.gnu.org/archive/html/lilypond-user/2013-06/msg00136.html

LilyPond blog was launched by Janek Warchoł on June 2nd!  It is
currently located at https://lilypondblog.wordpress.com but there are
plans to move it to another location (our own domain).  There are 10
posts already, the last one being an interview with Urs Liska (who
suggested the blog name).  Expected posting rate in the near future is
2 posts per week - please read us and comment!  Our motivation to
write interesting content increases when we see comments and visits :)
And btw, *everyone* is invited to contribute to the blog.  Don't feel
shy about it; you don't have to write an academic paper as a post :)
Anything interesting about LilyPond and music engraving will be
accepted.
Of course i hope that you will find the blog extremely interesting :D

best,
Janek

_______________________________________________
lilypond-devel mailing list
lilypond-devel&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
&lt;/pre&gt;</description>
    <dc:creator>Janek Warchoł</dc:creator>
    <dc:date>2013-06-10T16:15:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54422">
    <title>Using change staff in tight spaces leads to wrongly positioned noteswith duplet in crossing notes</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54422</link>
    <description>&lt;pre&gt;I first saw this in a score I was producing for real (thanks to Harm for 
pointing it out) and have managed to pare it down to a usable, though not 
small, example.  In the example I've been forced to prevent line breaks in 
order to replicate what is actually happening.  Should I just go ahead and 
raised a bug report?


\version "2.17.9"
\pointAndClickOff
#(set-global-staff-size 18)

\new Score \with { \override NonMusicalPaperColumn #'line-break-permission = 
##f }
  {
  &amp;lt;&amp;lt;
    \new Staff {   \clef "treble"
      \key e\major
      \time 9/8
      \autoBeamOff
      b'8  b' b'  b'  b'  b'  b'  b' b' |  % 1
      b'4. b'4. b'4.  |  % 2
      b'1 b'8 |
    }
    \new PianoStaff &amp;lt;&amp;lt;
      \new Staff = "RH"  \with {
        \override VerticalAxisGroup #'staff-staff-spacing = #'((padding . 
5))
      }
      {
        \autoBeamOff
        \clef "treble"
        \key e\major
        \time 9/8
        \times 3/2 {  \voiceOne  \change Staff = LHLayer  fis,32 (  [  cis32 
fis32 \voiceTwo  \change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  } 
\times 3/2 {  \voiceOne  \change Staff = LHLayer  fis,32 (  [  cis32 fis32 
\voiceTwo  \change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  }  \times 
3/2 {  \voiceOne  \change Staff = LHLayer  fis,32 (  [  cis32 fis32 
\voiceTwo  \change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  }   |  % 
15
        \times 3/2 {  \voiceOne  \change Staff = LHLayer  e,32 (  [  a,32 
cis32 \voiceTwo  \change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  } 
\times 3/2 {  \voiceOne  \change Staff = LHLayer  e,32 (  [  a,32 cis32 
\voiceTwo  \change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  }  \times 
3/2 {  \voiceOne  \change Staff = LHLayer  e,32 (  [  a,32 cis32 \voiceTwo 
\change Staff = RH  a32 cis'32 fis'32 gis'32 a'32 )  ]  }   |  % 16
        b'1 b'8 |
      }
      \new Staff = "LHLayer"
      {
        \autoBeamOff
        \clef "bass"
        \key e\major
        \time 9/8
        s2.  s4. |  % 1
        s2.  s4. |  % 2
        b,4 b, b, b, b'8 | % High b at end spaces staves wider - can be 
hidden if needed.
      }
    &amp;gt;&amp;gt;  % Pianostaff end
  &amp;gt;&amp;gt; % Music end
}


--
Phil Holmes

_______________________________________________
lilypond-devel mailing list
lilypond-devel&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
&lt;/pre&gt;</description>
    <dc:creator>Phil Holmes</dc:creator>
    <dc:date>2013-06-10T09:38:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54416">
    <title>markup: give the padding functions effect in skyline spacing; issue3255 (issue 9295044)</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54416</link>
    <description>&lt;pre&gt;The code looks reasonable, at least to me :-)  Thanks for working on
this.


https://codereview.appspot.com/9295044/diff/11001/input/regression/text-script-vertical-skylines.ly
File input/regression/text-script-vertical-skylines.ly (right):

https://codereview.appspot.com/9295044/diff/11001/input/regression/text-script-vertical-skylines.ly#newcode6
input/regression/text-script-vertical-skylines.ly:6: spacing reservation
of a stencil, while &amp;lt; at &amp;gt;code{with-dimensions} completely
This is hard to understand IMHO.  What about

   &amp;lt; at &amp;gt;code{pad-around} computes the (smallest) bounding box of a stencil
and pads this box by the given amount.  &amp;lt; at &amp;gt;code{with-dimensions}
completely...

https://codereview.appspot.com/9295044/
&lt;/pre&gt;</description>
    <dc:creator>lemzwerg&lt; at &gt;googlemail.com</dc:creator>
    <dc:date>2013-06-09T19:37:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54414">
    <title>unsubscribing from -devel</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54414</link>
    <description>&lt;pre&gt;Hi all,

after a lot of considering pros and cons and being realistic about the
amount of time left to spend on development, I decided to unsubscribe
from this list :-(

My last remarkable contribution is about 9 months ago, and all attempts
to getting into lilypond again (not only visible on -devel, but also
in private emails) showed me that this will not work properly in my
current situation.

Instead of just composing and fiddling with computers, I realized
that I have to *play* music which (at least to me) seems much more
satisfying compared to computer work.

Moreover, my job claims for more time, and then there is my family ...

The last weeks' so-called work on lilypond was merely deleting the 
incoming mails without really having time to read it, so staying
subscribed does not really make sense at all.

I will stay subscribed on -user (after all, lilypond *is* great, so I'll 
use it in the future and I'll try to help users getting along
with it) and my email address will stay valid, so feel free to contact
me if you think there is something going on where I could be of some
help.

Thanks for all your patience, help and ideas! You are a great community.

All the best,

Marc
&lt;/pre&gt;</description>
    <dc:creator>Marc Hohl</dc:creator>
    <dc:date>2013-06-09T14:23:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54409">
    <title>PATCHES: Countdown for June 12 - 06:00</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54409</link>
    <description>&lt;pre&gt;Hello,

*Countdown -- June 12 -- 06:00 GMT* *
* *
* *
* *
*





3399 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3399&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Make parenthesized dynamics 
snippet more versatile
3398 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3398&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Format 
inserting-score-fragments snippet nicer in the wake of issue 3187
3397 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3397&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Snippet 
creating-double-digit-fingerings fights windmills
3395 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3395&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Let Flag grob inherit color 
and transparent from its stem by default
3394 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3394&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Let compound-time-signatures 
snippet use \compoundMeter
3392 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3392&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup push Patch: Use &amp;lt; at &amp;gt;dots{} instead of ... 
in notation manual where appropriate





3404 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3404&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Enhancement marc&amp;lt; at &amp;gt;hohlart.de countdown Patch: Small corrections to 
the scheme reformatting patch.
3403 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3403&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Enhancement Benko Pal countdown Patch: follow up issue 2470: make 
Completion_rest_engraver aware of completionUnit
3402 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3402&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Enhancement David Kastrup countdown Patch: Completion_heads_engraver 
should declare input property completionUnit
3401 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3401&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Defect David Kastrup countdown Parser error with void function in 
music list





3383 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3383&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Defect David Kastrup review old-straight-flag + smaller 
Stem.thickness gives no output and huge over










*Patches moved to 'Waiting' this countdown* 



3393 
&amp;lt;http://code.google.com/p/lilypond/issues/detail?id=3393&amp;amp;q=label%3APatch-review&amp;amp;sort=patch&amp;amp;colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary%20Modified&amp;gt; 
Documentation David Kastrup waiting Patch: Let 
chant-or-psalms-notation snippet use \hide and \undo


&lt;/pre&gt;</description>
    <dc:creator>James</dc:creator>
    <dc:date>2013-06-09T07:29:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54371">
    <title>Snippet creating-double-digit-fingerings fights windmills (issue9973043)</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54371</link>
    <description>&lt;pre&gt;LGTM

https://codereview.appspot.com/9973043/
&lt;/pre&gt;</description>
    <dc:creator>graham&lt; at &gt;percival-music.ca</dc:creator>
    <dc:date>2013-06-06T21:27:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54370">
    <title>Format inserting-score-fragments snippet nicer in the wake of issue3187 (issue 9705045)</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54370</link>
    <description>&lt;pre&gt;I think the original version was more general, but if it produces ugly
output due to a bug then I guess I can't complain about this change.

https://codereview.appspot.com/9705045/
&lt;/pre&gt;</description>
    <dc:creator>graham&lt; at &gt;percival-music.ca</dc:creator>
    <dc:date>2013-06-06T21:26:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54369">
    <title>Make parenthesized dynamics snippet more versatile (issue 10008043)</title>
    <link>http://comments.gmane.org/gmane.comp.gnu.lilypond.devel/54369</link>
    <description>&lt;pre&gt;LGTM

https://codereview.appspot.com/10008043/
&lt;/pre&gt;</description>
    <dc:creator>graham&lt; at &gt;percival-music.ca</dc:creator>
    <dc:date>2013-06-06T21:24:18</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.gnu.lilypond.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.gnu.lilypond.devel</link>
  </textinput>
</rdf:RDF>
