Re: Help with positioning coda glyph

[Patrick McCarty]

On 2009-09-16, Tim McNamara wrote:
> 
> On Sep 16, 2009, at 9:31 AM, Robin Bannister wrote:
> 
> >Tim McNamara wrote:
> >> The first coda glyph should be at the end of bar 28
> >
> >See LSR 432.    Before the \break, add
> >\once \override Score.RehearsalMark #'break-visibility = 
> >#begin-of-line-invisible
> 
> Good grief.  But thank you, that did the job.
> 
> But it seems like a cumbersome workaround for a behavior that
> shouldn't happen in the first place.  IMHO this is precisely the
> sort of stuff that will prevent LilyPond from being an application
> for anything beyond a narrow specialist market of people willing to
> plow through hundreds of pages of documentation to write even simple
> lead sheets.

Well, it's definitely a workaround, but keep in mind that a
RehearsalMark grob is optimized for displaying "rehearsal marks"; the
default value (end-of-line-invisible) is the best option for this
case.

Since you are using the Coda symbol for the RehearsalMark text, it
makes sense that some workarounds to achieve optimal layout might be
needed.

If there was built-in support for typesetting Coda symbols, the
default settings would be different, but this support does not exist
right now.

> >> LilyPond won't put the coda glyph at the beginning of bar 31.
> >>At least not using the code provided in the documentation.
> >
> >You have put the \mark command after the first note of the triplet.
> 
> Thanks, I got that figured out but sent my reply to my original post
> back to myself (because for some reason the listserv does not set
> the reply-to header to the list, odd given that we profess to want
> the discussions to be on the list so that they are archived).  I've
> re-sent the post.

I think all of the Savannah-hosted lists have these headers, so you
might want to contact the Savannah staff if you really want to change
this.

In many email clients, it's enough to "Reply to all" or the
equivalent.


-Patrick