> Anyway, I tested the code and am unfortunately getting errors with
> 2.19.65. Here's the log file
Hi Robert,
as with any code for another LilyPond version, you should run convert-ly
first. Within Frescobaldi this is very easy: Tools > Update using
convert-ly…
In the case of the errors you post
2017-09-17 18:50 GMT+02:00 Robert Murdoch :
> On 17/09/2017 17:44, Thomas Morley wrote:
>> Did you try convert-ly?
> I forgot about that until I'd already sent my post, but I remembered and now
> it works perfectly. Thank you, this story is happy end.
Well, this particular one.
But honestly, th
On 17/09/2017 17:44, Thomas Morley wrote:
2017-09-17 18:28 GMT+02:00 Robert Murdoch :
Anyway, I tested the code and am unfortunately getting errors with 2.19.65.
Here's the log file:
[...]
Did you try convert-ly?
Cheers,
Harm
I forgot about that until I'd already sent my post, but I rem
2017-09-17 18:28 GMT+02:00 Robert Murdoch :
> Anyway, I tested the code and am unfortunately getting errors with 2.19.65.
> Here's the log file:
[...]
Did you try convert-ly?
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https:/
On 17/09/2017 16:50, Thomas Morley wrote:
http://lists.gnu.org/archive/html/lilypond-user/2013-12/msg01027.html
Old code, perhaps not the best one, but it _is_ possible.
Ok, I'd never suggest to put something like that into our source.
Also, I never put it in the LSR because I felt it's a too
2017-09-17 16:20 GMT+02:00 Robert Murdoch :
> For some reason my reply to Shamus Hammons' "Problems with Codas" post
> hasn't shown up after half an hour, so I'll post about codas here instead.
Meanwhile it is there, recently a lot folk complained about similiar ...
> It is practically impossible
Hi,
For some reason my reply to Shamus Hammons' "Problems with Codas" post
hasn't shown up after half an hour, so I'll post about codas here instead.
It is practically impossible to set up a coda properly in LilyPond. In
most scores I've seen, the main score and the coda section are separated
