<?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://permalink.gmane.org/gmane.comp.gnu.lilypond.general">
    <title>gmane.comp.gnu.lilypond.general</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general</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://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82579"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82578"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82577"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82576"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82575"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82574"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82573"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82572"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82571"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82570"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82569"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82568"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82567"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82566"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82565"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82564"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82563"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82562"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82561"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82560"/>
      </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://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82579">
    <title>Re: Cross staff/cross voice arpeggio colliding with previous note</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82579</link>
    <description>&lt;pre&gt;

When you need more space between notes, you can use extra-spacing-...
Just before the note in the upper voice, ask for more space to its left
  \once \override NoteHead #'extra-spacing-width = #'(-2 . 0)

It looks like LilyPond does not notice that the arpeggio needs to move
left for the lower-staff accidental, when choosing note-spacing.
&lt;/pre&gt;</description>
    <dc:creator>Keith OHara</dc:creator>
    <dc:date>2013-05-22T18:27:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82578">
    <title>Re: Cross staff/cross voice arpeggio colliding with previous note</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82578</link>
    <description>&lt;pre&gt;Michael Rivers wrote

 if you search for /generalized-offsetter/ in this list you'll find a nice
solution!

Eluze



--
View this message in context: http://lilypond.1069038.n5.nabble.com/Cross-staff-cross-voice-arpeggio-colliding-with-previous-note-tp146197p146203.html
Sent from the User mailing list archive at Nabble.com.
&lt;/pre&gt;</description>
    <dc:creator>Eluze</dc:creator>
    <dc:date>2013-05-22T17:46:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82577">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82577</link>
    <description>&lt;pre&gt;Well, comparing the lengths of strings is a bit shortsighted, as all
four-letter words don't occupy the same space...  Revised to work with
stencil sizes, as David Kastrup suggests earlier in this thread.

Argh.
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-22T17:06:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82576">
    <title>Re: Fatal bug in strftime?</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82576</link>
    <description>&lt;pre&gt;Peter,


On Wed, May 22, 2013 at 11:07 AM, Peter Toye &amp;lt;lilypond&amp;lt; at &amp;gt;ptoye.com&amp;gt; wrote:


But the work is done--all you need to do is copy and paste what I've given
you.  If you're working with a template, add it to that.

-David
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-22T16:17:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82575">
    <title>Re: Fatal bug in strftime?</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82575</link>
    <description>&lt;pre&gt;David,

Thanks. Hardly worth the effort! I think I'll just try to ignore my allergy to leading zeroes in dates. Or not do any engraving 1-9 of the month.

I'm no LISP expert, apart from knowing that it stands for Lots of Irritating Surplus Parentheses.

Best regards,

Peter
mailto:lilypond&amp;lt; at &amp;gt;ptoye.com
www.ptoye.com

-------------------------
Monday, May 13, 2013, 2:39:51 PM, you wrote:


Hi Peter,


As a workaround, you could just use %d and check for a leading zero, replacing it with a space.  Something like this:

\header {
  title = "title"
  composer = "no-one"
  tagline = \markup {
    Engraved
    \simple #(let ((date (strftime "%d/%m/%Y" (localtime (current-time)))))
                (if (string-prefix? "0" date)
                    (string-append " " (string-drop date 1))
                    date))
    with \with-url #"http://lilypond.org/"
    \line { LilyPond \simple #(lilypond-version) (http://lilypond.org/) }
  }
}

{ c d e f }


Modifications would have to be made if you want the day in other than &lt;/pre&gt;</description>
    <dc:creator>Peter Toye</dc:creator>
    <dc:date>2013-05-22T16:07:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82574">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82574</link>
    <description>&lt;pre&gt;Hi Carl,


On Wed, May 22, 2013 at 10:36 AM, Carl Peterson &amp;lt;carlopeterson&amp;lt; at &amp;gt;gmail.com&amp;gt;wrote:


Thank you for adding this shortcut.



Yes, you can use it as much as you like.  (In fact, you could remove the
\once in your definition of `tagIt' and have it apply to every syllable.)

--David
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-22T15:53:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82573">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82573</link>
    <description>&lt;pre&gt;I'm not in a position to test this at the moment, but just for
confirmation, will this work with an arbitrary number of tagged syllables
through a Lyrics context?

ex:

tagIt = \once \override Lyrics.LyricText #'tagged = ##t

 \new Lyrics \lyricsto A {
      \tagIt This is the first phrase in my song. \break
      \tagIt This is an -- oth -- er phrase to sing. \break
      \tagIt This is a third phrase in my song. \break
      \tagIt This is the last phrase in my song.
    }

Cheers,
Carl


On Wed, May 22, 2013 at 9:02 AM, David Nalesnik &amp;lt;david.nalesnik&amp;lt; at &amp;gt;gmail.com&amp;gt;wrote:

_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>Carl Peterson</dc:creator>
    <dc:date>2013-05-22T15:36:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82572">
    <title>Cross staff/cross voice arpeggio colliding with previous note</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82572</link>
    <description>&lt;pre&gt;In this excerpt from a piece I'm typesetting, the first two arpeggios are
fine, but the third collides with the previous note in the right hand's
upper voice. Is there a way to avoid the collision?

\version "2.16.2"

global = {
  \key as \major
  \time 6/8
}

rightOne = \relative c'' {
  \global
  bes16\arpeggio( g' bes f g\arpeggio c, bes4.)\arpeggio
}

rightTwo = \relative c' {
  \global
  d4\arpeggio es8\arpeggio f16\arpeggio g bes f g bes, 
  
}

left = \relative c {
  \global
  &amp;lt;bes aes'&amp;gt;4\arpeggio &amp;lt;bes aes' c&amp;gt;8\arpeggio &amp;lt;bes aes' d&amp;gt;4.\arpeggio 
  
}

\score {
  \new PianoStaff 
  &amp;lt;&amp;lt;
    \set PianoStaff.connectArpeggios = ##t
    \new Staff = "right" \with {\consists "Span_arpeggio_engraver"} &amp;lt;&amp;lt;
\rightOne \\ \rightTwo &amp;gt;&amp;gt;
    \new Staff = "left" { \clef bass \left }
  &amp;gt;&amp;gt;
}



--
View this message in context: http://lilypond.1069038.n5.nabble.com/Cross-staff-cross-voice-arpeggio-colliding-with-previous-note-tp146197.html
Sent from the User mailing list archive at Nabble.com.
&lt;/pre&gt;</description>
    <dc:creator>Michael Rivers</dc:creator>
    <dc:date>2013-05-22T15:22:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82571">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82571</link>
    <description>&lt;pre&gt;Hi


On Tue, May 21, 2013 at 8:41 PM, David Nalesnik &amp;lt;david.nalesnik&amp;lt; at &amp;gt;gmail.com&amp;gt;wrote:

Noticed a problem.  Corrected file attached.

--David
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-22T13:02:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82570">
    <title>partcombine and bendAfter don't always play nicely</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82570</link>
    <description>&lt;pre&gt;Hi folks,

I seem to have run into a problem that has been reported once before:

https://lists.gnu.org/archive/html/lilypond-user/2010-03/msg00263.html

Consider this file:

%%%%%%%%%%%%%%%%%%%


\version "2.16.2"


First={f'2\bendAfter #-5 }

Second={d'2\bendAfter #-5 }



\score{

   &amp;lt;&amp;lt;

      \new Staff

         %\First                                   % ex. 1 Bend typeset

         %\Second                               % ex. 2 Bend typeset

          \partcombine \First \Second     % ex. 3 Bends not typeset

         %\partcombine \Second \First   % ex. 4 Bends typeset

   &amp;gt;&amp;gt;

 }

%%%%%%%%%%%%%%%%%%%

If I typeset parts First or Second individually (examples 1 and 2) without
using the partcombiner the falls are typeset as expected. Similarly, if I
use the partcombiner such that the notes don't share a stem (example 4) the
falls are typeset.

However, if I use the partcombiner so that a stem shared (example 3), the
falls are not typeset. This isn't simply an issue with the stem
though---the problem pe&lt;/pre&gt;</description>
    <dc:creator>Cameron Horsburgh</dc:creator>
    <dc:date>2013-05-22T10:53:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82569">
    <title>Re: Files from Lilypond workshop &lt; at &gt; LAC 2013</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82569</link>
    <description>&lt;pre&gt;Hi all,


David Kastrup wrote:

luis jure wrote:


So now that we have - to my relief - established that I'm not to blame for anything :) may I suggest the following:

Although I am tempted to leave things as they are (to get new Lilyponders used to the note/pitch inconsistency as early as possible), I have changed the "pitches" on page 20 of my slides to "notes". 

Reasoning:

* Let's at least be consistent within this single document
* However, I'm too lazy re-do the figure on page 13
* So "notes" it is :)

I have updated the archive with the slides and examples at
http://lac.linuxaudio.org/2013/download/lilypond_lac2013.tgz

As important as these terminology discussions are for the continued development of Lilypond, I think it is worth reminding ourselves that during the actual workshop, this did not seem to cause any confusion whatsoever.

So is the idea to simply include a link to the above .tgz archive at http://lilypond.org/publications , or would it be preferable to host a copy on lilypond.org itself&lt;/pre&gt;</description>
    <dc:creator>Florian Hollerweger</dc:creator>
    <dc:date>2013-05-22T09:09:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82568">
    <title>Re: Files from Lilypond workshop &lt; at &gt; LAC 2013</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82568</link>
    <description>&lt;pre&gt;Dear Helge,


Helge Kruse wrote:

Let's not be cynical about this: It was fully intentional, but could arguably be described as a somewhat adolescent and dated joke. Since it seems to cause offence, I have changed the "$" to a less controversial "S".



It contains a hyperlink to the actual thing, for Bill Gates' sake! :)

But there you go, I have replaced "module" with "runtime" as you suggested.



I am starting to find this discussion rather entertaining :)

But I think I have found what I believe to be a structurally /and/ typographically sound solution for this "problem" (it never seemed to be one before announcing the slides here).

All the above edits are reflected in the now updated the archive with the slides and examples at
http://lac.linuxaudio.org/2013/download/lilypond_lac2013.tgz


luis jure wrote:

Ah, music to my ears, luis, thanks! :)


Best,
flo.H
&lt;/pre&gt;</description>
    <dc:creator>Florian Hollerweger</dc:creator>
    <dc:date>2013-05-22T09:08:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82567">
    <title>Re: intractable collision of arpeggio and rest</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82567</link>
    <description>&lt;pre&gt;
On 22 May 2013, at 10:06 , David Kastrup wrote:


AND: boiling down the problem makes sure there IS a problem. Sometimes  
a problem you experience goes away when boiling down, so when you  
compile at stages in between you'll might find what caused the problem  
itself. And (ideally) that process mostly happens before you put it on  
the list.

Boiling down then also gives any helper the assurance you looked at  
the problem yourself seriously.

Regards,
Wim.
&lt;/pre&gt;</description>
    <dc:creator>Wim van Dommelen</dc:creator>
    <dc:date>2013-05-22T08:30:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82566">
    <title>Re: intractable collision of arpeggio and rest</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82566</link>
    <description>&lt;pre&gt;

It's just a matter of efficiency.  To find the problem, you need to boil
down the code to the essential part anyway.  Not doing this in advance
is only efficient if the expected number of helpers is below 1 or if
their time is to be valued less than that of the person having the
problem.  But making it easy for people to help also makes it more
satisfying for them, so it is also an advantage for the long term.

&lt;/pre&gt;</description>
    <dc:creator>David Kastrup</dc:creator>
    <dc:date>2013-05-22T08:06:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82565">
    <title>Re: intractable collision of arpeggio and rest</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82565</link>
    <description>&lt;pre&gt;Am 22.05.2013 08:59, schrieb Tom Cloyd:

The problem here with your file is that it cannot be compiled ...
[...]

... because this file is missing.

Generally, it is a good idea to try to boil the file down to the
essential parts, one or two measures that show the problem should be 
sufficient. Longer files/attachmens seem to scare potential helpers away.

Marc
&lt;/pre&gt;</description>
    <dc:creator>Marc Hohl</dc:creator>
    <dc:date>2013-05-22T07:51:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82564">
    <title>intractable collision of arpeggio and rest</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82564</link>
    <description>&lt;pre&gt;Running Lilypond 2.16.0 -

1. In the following 8 bar snippet, I am arpeggiating across the middle 
and upper voices. The arpeggio is colliding with the rest that's in the 
middle voice. I've tried about 9 ways and I cannot get the arpeggio in 
the right place. It needs to make room for that rest. Nothing works. Any 
ideas?

2. Also, is there any way to close the distance between the arpeggio and 
the notes to which it's applied? Seems like an awfully big gap; I'd like 
to lose about 30% of it.

3. Is this there any way to get more distance between the "instrument" 
line and the beginning of the score# It looks crowded to me.

Thanks for the help!

\version "2.16.0"

% (is Lilypond current version - checked 2013.05.12)

% template version 2013.05.15


\include "articulate.ly" % use the articulate.ly script (affects midi 
file - activates midi repeats, better articulation, etc.).

\include "_fingering-variables.ly" % variables needed to manage LH &amp;amp; RH 
fingering efficiently


%{NOTES -

*ToDos for this piece:
&lt;/pre&gt;</description>
    <dc:creator>Tom Cloyd</dc:creator>
    <dc:date>2013-05-22T06:59:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82563">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82563</link>
    <description>&lt;pre&gt;Hi Gregory,

Here's another version which will automatically find the longest syllable.
 You can tag any one of the lyric syllables at a given timestep.

HTH,
David
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-22T01:41:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82562">
    <title>Re: Positioning volta bracket</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82562</link>
    <description>&lt;pre&gt;
In addition to the extra-offset method, there is another way.  I
most often adjust the Y-extent of the volta bracket.  This
effectively "lies" to lilypond's typesetting engine that the
volta bracket is vertically shorter or taller than lilypond would
normally think.  This affects not only how far above the staff
the volta is placed (as you requested), it also affects how much
space lilypond will reserve above the volta and below the staff
preceding the staff with the volta (the system-system spacing
for that one line).

I have a short three-line file that I read into my text editor
when I need it:

% decreasing the first number  increases the space BELOW the volta bracket
% increasing the second number increases the space ABOVE the volta bracket
\once \override Score.VoltaBracket #'Y-extent = #'(-1.0 . 1.0)

I don't know offhand what the default is, but I usually start at
-1.0 . 1.0 and adjust from there.  That starting point is
sometimes too crowded, but I read the comments and twiddle the
values until I g&lt;/pre&gt;</description>
    <dc:creator>Jim Long</dc:creator>
    <dc:date>2013-05-21T23:56:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82561">
    <title>Re: Files from Lilypond workshop &lt; at &gt; LAC 2013</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82561</link>
    <description>&lt;pre&gt;
on 2013-05-21 at 17:04 David Kastrup wrote:


of course! it was not my intention to imply otherwise. what i was trying
to say was that using existing musical terminology to denote something
that's not quite the precise meaning, is a potential source of confusion. 

 

to be honest, i had never paid attention to this until today, when helge
pointed out the inconsistent use of the terms "note" and "pitch" in
florian's presentation (which, as you said, was just the consequence of
using lilypond's terminology, not florian's fault, of course).

it seems the terminology is now deeply ingrained in lilypond and in the
code itself, so it's not just a matter of modifying the manual here and
there. if the community (and as a user i consider myself part of it) is OK
with it, then fine. as i just said, it never bothered me.

i just think it's not ideal. and perhaps also not quite consistent with
lilypond's spirit of caring for perfection, beauty and correctness of
music notation, which is itself a manifestation of music&lt;/pre&gt;</description>
    <dc:creator>luis jure</dc:creator>
    <dc:date>2013-05-21T22:15:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82560">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82560</link>
    <description>&lt;pre&gt;
On a side note: I think it could potentially be very useful to be able to
add markers to various grobs by overriding a property to a boolean or a
string.  There's \tag but that works with music expressions.

--David
_______________________________________________
lilypond-user mailing list
lilypond-user&amp;lt; at &amp;gt;gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-21T21:47:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82559">
    <title>Re: Left align first word of lyrics</title>
    <link>http://permalink.gmane.org/gmane.comp.gnu.lilypond.general/82559</link>
    <description>&lt;pre&gt;Hi,

On Tue, May 21, 2013 at 4:32 AM, Gregory Heytings &amp;lt;ghe&amp;lt; at &amp;gt;sdf.org&amp;gt; wrote:


I'm kind of surprised that this works.

Basically, the idea is that you tag the syllable you want the column to
left-align to by overriding an invented property which I called `tagged'
for lack of any inspiration.

Right now, you need to choose the syllable you want to use for alignment.
 I don't imagine it would be difficult to determine the longest
automatically.

The materials between %%%% aren't strictly necessary.  Without them, you'll
just get a number of warnings.

Hope this helps!

\version "2.17.17"

%%%%%%%%%%%%%%%%%%%%%%

#(define (define-grob-property symbol type? description)
  (if (not (equal? (object-property symbol 'backend-doc) #f))
      (ly:error (_ "symbol ~S redefined") symbol))

  (set-object-property! symbol 'backend-type? type?)
  (set-object-property! symbol 'backend-doc description)
  symbol)

#(map
  (lambda (x)
    (apply define-grob-property x))

  `(
    (tagged ,boolean? "use this lyric syllable for a&lt;/pre&gt;</description>
    <dc:creator>David Nalesnik</dc:creator>
    <dc:date>2013-05-21T21:27:57</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.gnu.lilypond.general">
    <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.general</link>
  </textinput>
</rdf:RDF>
