Re: 64-bit Mac build of 2.20 is now available! (convert.ly issue)

[David Kastrup]

David Kastrup  writes:

> Zone Dremik  writes:
>
>>  Thank you David, Marnen, David and Carl for your excellent
>> suggestions and helpful examples. (I will definitely be using more
>> variables in the future.)
>> For the convert.ly issue, your recommendations inspired me to try
>> using BBE. The multi-file search & replace function worked very well
>> (this was with the free version of BBE, so I was very impressed).
>>
>> Further note:
>> I ran a few more of the older files through convert.ly and found
>> that it is finding & updating other instances of obsolete syntax,
>> beyond the two that are missing.
>>
>> Here is a code sample, before & after, for a successful convert.ly:
>>
>> \version "2.12.2"
>> \include "english.ly"
>>  \override LyricText #'font-shape = #'italic
>>
>> \version "2.20.0"
>> \include "english.ly"
>>  \override LyricText.font-shape = #'italic
>>
>> (A side note: By mistake, I ran the compile before convert.ly and
>> was surprised that the Lilypond 2.20 didn't reject the obsolete
>> syntax. I definitely don't have any other versions installed on this
>> machine.)
>
> Yes, overrides and reverts are properly converted.  It's the naked
> assignments that seemed too indistinctive to warrant a generic rule for
> the conversion (there was one used for one-shot conversion of LilyPond's
> own documentation where one can keep the effects in check).

Ok, it seems like (almost?) exclusively variables ending in "-spacing"
are affected here.  That should make a reasonably safe rule
comparatively easy to design.

> I have it on my to-do list to do something here for the sake of
> 2.20.1, but I'm currently laboring on getting 2.21.0 out first: that's
> also urgent.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available! (convert.ly issue)

[David Kastrup]

Zone Dremik  writes:

>  Thank you David, Marnen, David and Carl for your excellent suggestions and 
> helpful examples. (I will definitely be using more variables in the future.)
> For the convert.ly issue, your recommendations inspired me to try using BBE. 
> The multi-file search & replace function worked very well (this was with the 
> free version of BBE, so I was very impressed).
>
> Further note:
> I ran a few more of the older files through convert.ly and found that it is 
> finding & updating other instances of obsolete syntax, beyond the two that 
> are missing.
>
> Here is a code sample, before & after, for a successful convert.ly:
>
> \version "2.12.2"
> \include "english.ly"
>  \override LyricText #'font-shape = #'italic
>
> \version "2.20.0"
> \include "english.ly"
>  \override LyricText.font-shape = #'italic
>
> (A side note: By mistake, I ran the compile before convert.ly and was 
> surprised that the Lilypond 2.20 didn't reject the obsolete syntax. I 
> definitely don't have any other versions installed on this machine.)

Yes, overrides and reverts are properly converted.  It's the naked
assignments that seemed too indistinctive to warrant a generic rule for
the conversion (there was one used for one-shot conversion of LilyPond's
own documentation where one can keep the effects in check).

I have it on my to-do list to do something here for the sake of 2.20.1,
but I'm currently laboring on getting 2.21.0 out first: that's also
urgent.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 7:06 PM Marnen Laibow-Koser 
wrote:

> On Tue, Mar 17, 2020 at 6:48 PM Marnen Laibow-Koser 
> wrote:
>
>> On Tue, Mar 17, 2020 at 6:43 PM Arle Lommel 
>> wrote:
>>
>>> Glad my feedback seems to be useful.
>>>
>>> [cutting a bit here]
>>>
>>> Thanks, this makes sense.  I should be able to set the variables
>>> correctly (and actually, the lilypond "binary" in the app bundle is already
>>> a script that sets a few variables and calls the real executable, so
>>> putting a few more in there should not be a problem).
>>>
>>> I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 for
>>> this bug.  Feel free to subscribe there for updates, or to create new
>>> issues there if they're problems with the 64-bit Mac packaging rather than
>>> LilyPond itself.
>>>
>>>
>>> Great. Glad it seems solvable.
>>>
>>
>> Yeah, if it's just a question of setting a few variables, it shouldn't be
>> too hard to fix.
>>
>
> ...but that isn't the case.  Setting those variables (which were actually
> already set in my shell anyway) appears to have no effect.  Moreover, it's
> only GhostScript choking on these filenames, not LilyPond.  See the GitLab
> issue for more.
>

This issue appears related to
http://lilypond.1069038.n5.nabble.com/Ghostscript-fails-with-special-characters-in-filename-td80105.html
.  Was that ever fixed?  It's not clear from the mailing list archive.

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 64-bit Mac build of 2.20 is now available!

[David Wright]

On Wed 18 Mar 2020 at 16:18:02 (+), Zone Dremik wrote:
>  It was quite a few years ago that copied this code sample from the LilyPond 
> Notation Reference v2.18.2 webpage:
> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
> I've compiled hundreds of Lead-Sheets with it, but haven't up-dated Lilypond 
> since 2.18.2 until now.

Perhaps you could run sed over the files, if the relevant lines are
formatted reasonably consistently. Something like:

$ cat /tmp/sed.ly 
  system-system-spacing = #'((minimum-distance . 0) (basic-distance . 15) 
(padding . 9))
  markup-system-spacing #'basic-distance = #15
  top-system-spacing   #'basic-distance  =#15
  last-bottom-spacing #'basic-distance=  #15
  last-bottom-spacing #'padding=#9
$ sed -e "s/\(-spacing\)[ ]\+#'\([^ ]\+\)[ ]*=[ ]*#/\1.\2 = #/;" /tmp/sed.ly 
  system-system-spacing = #'((minimum-distance . 0) (basic-distance . 15) 
(padding . 9))
  markup-system-spacing.basic-distance = #15
  top-system-spacing.basic-distance = #15
  last-bottom-spacing.basic-distance = #15
  last-bottom-spacing.padding = #9
$ 

Cheers,
David.

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

David Kastrup  writes:

> Marnen Laibow-Koser  writes:
>
>> On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik  wrote:
>>
>>> It was quite a few years ago that copied this code sample from the
>>> LilyPond Notation Reference v2.18.2 webpage:
>>>
>>> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
>>> I've compiled hundreds of Lead-Sheets with it, but haven't up-dated
>>> Lilypond since 2.18.2 until now.
>>>
>>
>> Right, as David said, it was in fact valid syntax (which I didn’t realize)
>> but convert-ly doesn’t know about it.  D’oh!  So I guess this is under the
>> category of “known issues in convert-ly” rather than “broken build”.  Sorry
>> for the inconvenience!
>
> More like "should have known issues in convert-ly".  Analysis of what
> decisions have led there just came up yesterday.  There likely is going
> to be a fix in 2.20.1 but I cannot yet vouch what.

I may add that this is the kind of thing that happens when everybody
decides that they'll wait for "stable" releases rather than trying out
betas or prereleases.

At some point of time, problems need to get flagged.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Marnen Laibow-Koser  writes:

> On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik  wrote:
>
>> It was quite a few years ago that copied this code sample from the
>> LilyPond Notation Reference v2.18.2 webpage:
>>
>> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
>> I've compiled hundreds of Lead-Sheets with it, but haven't up-dated
>> Lilypond since 2.18.2 until now.
>>
>
> Right, as David said, it was in fact valid syntax (which I didn’t realize)
> but convert-ly doesn’t know about it.  D’oh!  So I guess this is under the
> category of “known issues in convert-ly” rather than “broken build”.  Sorry
> for the inconvenience!

More like "should have known issues in convert-ly".  Analysis of what
decisions have led there just came up yesterday.  There likely is going
to be a fix in 2.20.1 but I cannot yet vouch what.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Wed, Mar 18, 2020 at 12:18 PM Zone Dremik  wrote:

> It was quite a few years ago that copied this code sample from the
> LilyPond Notation Reference v2.18.2 webpage:
>
> http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
> I've compiled hundreds of Lead-Sheets with it, but haven't up-dated
> Lilypond since 2.18.2 until now.
>

Right, as David said, it was in fact valid syntax (which I didn’t realize)
but convert-ly doesn’t know about it.  D’oh!  So I guess this is under the
category of “known issues in convert-ly” rather than “broken build”.  Sorry
for the inconvenience!

Best,
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile

Re: 64-bit Mac build of 2.20 is now available!

[Zone Dremik]

 It was quite a few years ago that copied this code sample from the LilyPond 
Notation Reference v2.18.2 webpage:
http://lilypond.org/doc/v2.18/Documentation/notation/flexible-vertical-spacing-paper-variables
I've compiled hundreds of Lead-Sheets with it, but haven't up-dated Lilypond 
since 2.18.2 until now. On Wednesday, March 18, 2020, 11:49:29 AM EDT, 
Marnen Laibow-Koser  wrote:  
 
 

On Wed, Mar 18, 2020 at 6:49 AM David Kastrup  wrote:

Marnen Laibow-Koser  writes:
[...]


> AFAIK this was never proper syntax to begin with.  Does it compile with
> LilyPond 2.18?  I'd be surprised if it does.

It was prior to 2.18, and it was merely discouraged with 2.18 (in the
course of which all occurences got replaced).  There were good reasons
for retiring the syntax for good, but they were not accompanied by a
suitable convert-ly rule.

Huh, that’s odd, but good to know. 



So basically the complaint is valid.

But it sounds like this is an omission (I’d say a bug) in convert-ly itself, 
not necessarily an indication that this build of it is broken, right?



-- 
David Kastrup

Best,-- 
Marnen Laibow-Kosermarnen@marnen.orghttp://www.marnen.orgSent from Gmail Mobile 
 

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Marnen Laibow-Koser  writes:

> On Wed, Mar 18, 2020 at 6:49 AM David Kastrup  wrote:
>
>> Marnen Laibow-Koser  writes:
>
> [...]
>
>>
>>
>> > AFAIK this was never proper syntax to begin with.  Does it compile with
>> > LilyPond 2.18?  I'd be surprised if it does.
>>
>> It was prior to 2.18, and it was merely discouraged with 2.18 (in the
>> course of which all occurences got replaced).  There were good reasons
>> for retiring the syntax for good, but they were not accompanied by a
>> suitable convert-ly rule.
>
>
> Huh, that’s odd, but good to know.
>
>
>>
>> So basically the complaint is valid.
>
>
> But it sounds like this is an omission (I’d say a bug) in convert-ly
> itself, not necessarily an indication that this build of it is broken,
> right?

Right.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Wed, Mar 18, 2020 at 6:49 AM David Kastrup  wrote:

> Marnen Laibow-Koser  writes:

[...]

>
>
> > AFAIK this was never proper syntax to begin with.  Does it compile with
> > LilyPond 2.18?  I'd be surprised if it does.
>
> It was prior to 2.18, and it was merely discouraged with 2.18 (in the
> course of which all occurences got replaced).  There were good reasons
> for retiring the syntax for good, but they were not accompanied by a
> suitable convert-ly rule.


Huh, that’s odd, but good to know.


>
> So basically the complaint is valid.


But it sounds like this is an omission (I’d say a bug) in convert-ly
itself, not necessarily an indication that this build of it is broken,
right?


>
> --
> David Kastrup


Best,
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Davide Liessi  writes:

> Il giorno mer 18 mar 2020 alle ore 13:07 David Kastrup  ha 
> scritto:
>> It doesn't make sense to have convert-ly produce non-working code for
>> version 2.19.40 .  And convert-ly cannot promise to fix code that never
>> worked due to its combination of version statement and old syntax.
>>
>> It isn't guaranteed that you can run convert-ly multiple times for the
>> same version range without producing invalid code.
>
> Would it make sense to have the rule twice, once for the correct
> version and once for post-2.20.0?
> That would produce working code for 2.19.40, while also taking care of
> files that were diligently converted with convert-ly up to 2.20.0 (the
> invalid code in those files is not the user's error but convert-ly's).

Frankly, if you don't keep the originals when producing non-working
code, you could still reapply with the given version range.

And I don't really see the point in providing extra rules for converting
code that never could possibly have worked due to the combination of old
syntax with new \version statement.

That's sort of a bottomless pit.

> Of course provided that the applying the rule twice doesn't ruin the
> code.

At any rate, this is somewhat academical without having a rule for which
we are not certain that applying it once may ruin the code.  That was
part of the justification for not keeping the previously used rule
permanently.  And if we have such dangerous conversions, then jumping
from applying them not at all to applying them several times seems like
adding nuisance (namely people having to manually undo the effects
several times in a row).

-- 
David Kastrup
My replies have a tendency to cause friction.  To help mitigating
damage, feel free to forward problematic posts to me adding a subject
like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".

Re: 64-bit Mac build of 2.20 is now available!

[Davide Liessi]

Il giorno mer 18 mar 2020 alle ore 13:07 David Kastrup  ha 
scritto:
> It doesn't make sense to have convert-ly produce non-working code for
> version 2.19.40 .  And convert-ly cannot promise to fix code that never
> worked due to its combination of version statement and old syntax.
>
> It isn't guaranteed that you can run convert-ly multiple times for the
> same version range without producing invalid code.

Would it make sense to have the rule twice, once for the correct
version and once for post-2.20.0?
That would produce working code for 2.19.40, while also taking care of
files that were diligently converted with convert-ly up to 2.20.0 (the
invalid code in those files is not the user's error but convert-ly's).
Of course provided that the applying the rule twice doesn't ruin the code.

Davide

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Davide Liessi  writes:

> Dear David,
>
> Il giorno mer 18 mar 2020 alle ore 09:48 David Kastrup  ha 
> scritto:
>> For which version number then?  Likely the one for issue 4800?
>
> I may be wrong, but shouldn't it be for the version containing the new
> convert-ly rule (that is, by now, later than 2.20.0)?
> If a user has already used convert-ly on a file, as in Zon's case,
> then the file already has a 2.20.0 version statement and rules for
> previous versions would not be applied by a subsequent run of
> convert-ly.

It doesn't make sense to have convert-ly produce non-working code for
version 2.19.40 .  And convert-ly cannot promise to fix code that never
worked due to its combination of version statement and old syntax.

It isn't guaranteed that you can run convert-ly multiple times for the
same version range without producing invalid code.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[Davide Liessi]

Dear David,

Il giorno mer 18 mar 2020 alle ore 09:48 David Kastrup  ha 
scritto:
> For which version number then?  Likely the one for issue 4800?

I may be wrong, but shouldn't it be for the version containing the new
convert-ly rule (that is, by now, later than 2.20.0)?
If a user has already used convert-ly on a file, as in Zon's case,
then the file already has a 2.20.0 version statement and rules for
previous versions would not be applied by a subsequent run of
convert-ly.

Best wishes.
Davide

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Marnen Laibow-Koser  writes:

> On Wed, Mar 18, 2020 at 12:57 AM Zone Dremik  wrote:
>
>> Hello, convert.ly is not working as you described. Here are some code
>> excerpts.
>> Let me know if there is anything else I can send that would be helpful.
>>
>> From a file previously created with Frescobaldi 2.20 & Lilypond 2.18:
>>
>> \version "2.18.0"
>> \include "english.ly"
>> \include "Three White Gulls (Melody).ly"
>> \include "Three White Gulls (Verses).ly"
>> \include "Three White Gulls (Chords).ly"
>> \paper {
>> #(set-paper-size "letter")
>> system-system-spacing #'basic-distance = #15
>> markup-system-spacing #'basic-distance = #24
>>
> [...]
>
> AFAIK this was never proper syntax to begin with.  Does it compile with
> LilyPond 2.18?  I'd be surprised if it does.

It was prior to 2.18, and it was merely discouraged with 2.18 (in the
course of which all occurences got replaced).  There were good reasons
for retiring the syntax for good, but they were not accompanied by a
suitable convert-ly rule.

So basically the complaint is valid.

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[David Kastrup]

Thomas Morley  writes:

> Am Mi., 18. März 2020 um 07:49 Uhr schrieb Aaron Hill
> :
>>
>> On 2020-03-17 11:05 pm, Marnen Laibow-Koser wrote:
>> > AFAIK this was never proper syntax to begin with.  Does it compile with
>> > LilyPond 2.18?  I'd be surprised if it does.
>>
>> Definitely valid syntax in 2.18.2 [1]:
>>
>> 
>> \version "2.18.2"
>>
>> \paper {
>>indent = #0 ragged-right = ##f
>>system-system-spacing #'padding = #20
>> }
>>
>> { b'1 \break b'1 }
>> 
>>
>> [1]: http://lilybin.com/99jt2g/1
>>
>>
>> -- Aaron Hill
>>
>
> Yep. Though,
> system-system-spacing.padding = #20
> works as well in 2.18.2.
> Looks like there's no convert-rule for it.
>
> David?

Issue 4068.  Looks like I considered the rule too likely for false
positives to let it stay permanently.

The rationale in the issue states:

When pushed to staging, another commit reverting the convert-ly rule
will be added since we don't want to apply somewhat generic patterns
like those on unknown user-provided code when unchanged code remains
valid.

Of course, since then the "when unchanged code remains valid" bit went
out the window in issue 4800.

Maybe one would want to reintroduce a more specific version of the issue
4068 rule restricted to known variables and/or only within
\header/\layout/\paper blocks?

For which version number then?  Likely the one for issue 4800?

-- 
David Kastrup

Re: 64-bit Mac build of 2.20 is now available!

[Thomas Morley]

Am Mi., 18. März 2020 um 07:49 Uhr schrieb Aaron Hill
:
>
> On 2020-03-17 11:05 pm, Marnen Laibow-Koser wrote:
> > AFAIK this was never proper syntax to begin with.  Does it compile with
> > LilyPond 2.18?  I'd be surprised if it does.
>
> Definitely valid syntax in 2.18.2 [1]:
>
> 
> \version "2.18.2"
>
> \paper {
>indent = #0 ragged-right = ##f
>system-system-spacing #'padding = #20
> }
>
> { b'1 \break b'1 }
> 
>
> [1]: http://lilybin.com/99jt2g/1
>
>
> -- Aaron Hill
>

Yep. Though,
system-system-spacing.padding = #20
works as well in 2.18.2.
Looks like there's no convert-rule for it.

David?

Cheers,
  Harm

Re: 64-bit Mac build of 2.20 is now available!

[Aaron Hill]

On 2020-03-17 11:05 pm, Marnen Laibow-Koser wrote:

AFAIK this was never proper syntax to begin with.  Does it compile with
LilyPond 2.18?  I'd be surprised if it does.


Definitely valid syntax in 2.18.2 [1]:


\version "2.18.2"

\paper {
  indent = #0 ragged-right = ##f
  system-system-spacing #'padding = #20
}

{ b'1 \break b'1 }


[1]: http://lilybin.com/99jt2g/1


-- Aaron Hill

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Wed, Mar 18, 2020 at 12:57 AM Zone Dremik  wrote:

> Hello, convert.ly is not working as you described. Here are some code
> excerpts.
> Let me know if there is anything else I can send that would be helpful.
>
> From a file previously created with Frescobaldi 2.20 & Lilypond 2.18:
>
> \version "2.18.0"
> \include "english.ly"
> \include "Three White Gulls (Melody).ly"
> \include "Three White Gulls (Verses).ly"
> \include "Three White Gulls (Chords).ly"
> \paper {
> #(set-paper-size "letter")
> system-system-spacing #'basic-distance = #15
> markup-system-spacing #'basic-distance = #24
>
[...]

AFAIK this was never proper syntax to begin with.  Does it compile with
LilyPond 2.18?  I'd be surprised if it does.

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 64-bit Mac build of 2.20 is now available!

[Zone Dremik]

 Hello, convert.ly is not working as you described. Here are some code excerpts.
Let me know if there is anything else I can send that would be helpful.

>From a file previously created with Frescobaldi 2.20 & Lilypond 2.18:

\version "2.18.0"
\include "english.ly"
\include "Three White Gulls (Melody).ly"
\include "Three White Gulls (Verses).ly"
\include "Three White Gulls (Chords).ly"
\paper {
 #(set-paper-size "letter")
 system-system-spacing #'basic-distance = #15 
 markup-system-spacing #'basic-distance = #24
 top-margin = 5\mm
 bottom-margin = 5\mm
 

>From the convert.ly log:

convert-ly (GNU LilyPond) 2.20.0
convert-ly: Processing `'... 
Applying conversion: 2.19.2, 2.19.7, 2.19.11, 2.19.16, 2.19.22, 2.19.24, 
2.19.28, 2.19.29, 2.19.32, 2.19.40, 2.19.46, 2.19.49, 2.19.80, 2.20.0

-\version "2.18.0"
+\version "2.20.0"
 \include "english.ly"
 \include "Three White Gulls (Melody).ly"
 \include "Three White Gulls (Verses).ly"

(No other changes were made) 
This is from the Lilypond Log after compiling the above code with 2.20:

Starting lilypond 2.20.0 [Three White Gulls (Score).ly]...
Processing `/Users/Zynjanthropis/Music Typesetting/Finished Scores/Three White 
Gulls/Three White Gulls (Score).ly'
Parsing...
/Users/Zynjanthropis/Music Typesetting/Finished Scores/Three White Gulls/Three 
White Gulls (Score).ly:14:25: error: syntax error, unexpected SCM_TOKEN, 
expecting ',' or '.' or '='
 system-system-spacing 
 #'basic-distance = #15 
Interpreting music...[8][16]
Preprocessing graphical objects...
Interpreting music...
MIDI output to `Three White Gulls (Score).midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to 
`/var/folders/pk/2rfgzwtd2vj6fbn6pj30z41wgq/T//lilypond-QVR8nQ'...
Converting to `Three White Gulls (Score).pdf'...
Deleting `/var/folders/pk/2rfgzwtd2vj6fbn6pj30z41wgq/T//lilypond-QVR8nQ'...
fatal error: failed files: "/Users/Zynjanthropis/Music Typesetting/Finished 
Scores/Three White Gulls/Three White Gulls (Score).ly"
Exited with return code 1.

 On Tuesday, March 17, 2020, 02:28:33 PM EDT, Marnen Laibow-Koser 
 wrote:  
 
 On Tue, Mar 17, 2020 at 12:10 PM Zone Dremik  wrote:

 A Big Thank You to Marnen Laibow-Koser —  Mac OS 64 bit Lilypond 2.20 
downloaded, installed and is running! This is a huge relief since my skill 
level is basically; download file and drag to application folder.

The only thing not running quite as expected is convert.ly updating. It isn't 
flagging the syntax differences. It does execute without error messages and it 
changes the version number.


I thought that if it was run from the LilyPad app bundle, it would just 
silently update the whole file (I don't like that behavior, but it seemed to be 
design in LilyPad).  I'll admit that I haven't tested it thoroughly, though; if 
you run it from within Frescobaldi, you at least see the diff.  Is it missing 
syntax differences?  If so, I'd appreciate a sample file that it's not behaving 
properly on.

Not a huge problem, since any instances of the old syntax (2.18.2) get 
highlighted during the compile anyway. 

If convert-ly is working properly, there shouldn't *be* any of the old syntax 
left.  If there are, that *is* a huge problem and means that the version I 
packaged is broken.  Is that the case?
Best,-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org  

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 7:45 PM Davide Liessi 
wrote:

> Il giorno mer 18 mar 2020 alle ore 00:23 Marnen Laibow-Koser
>  ha scritto:
> > Will that work on Mac OS without the problems that have plagued the
> other 3.x versions of Fresco?
>
> I solved some problems, but unfortunately not all.
> The main packaging problem concerning PyQtWebEngine, which caused
> crashes on startup or when using some panels, is not solved yet, but
> 3.1.2 will fail gracefully, simply disabling the features depending on
> WebEngine (Documentation browser, SVG viewer).


Understood.  I look forward to trying it; thanks!


>
> Best wishes.
> Davide
>
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile

Re: 64-bit Mac build of 2.20 is now available!

[Davide Liessi]

Il giorno mer 18 mar 2020 alle ore 00:23 Marnen Laibow-Koser
 ha scritto:
> Will that work on Mac OS without the problems that have plagued the other 3.x 
> versions of Fresco?

I solved some problems, but unfortunately not all.
The main packaging problem concerning PyQtWebEngine, which caused
crashes on startup or when using some panels, is not solved yet, but
3.1.2 will fail gracefully, simply disabling the features depending on
WebEngine (Documentation browser, SVG viewer).

Best wishes.
Davide

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 7:17 PM Davide Liessi 
wrote:

> Il giorno mar 17 mar 2020 alle ore 22:36 Arle Lommel
>  ha scritto:
> > #2: Update.ly doesn’t work for me when invoked from Frescobaldi. I get
> this message about a bad CPU type when I run it from Frescobaldi.
>
> Known problem, depending only on Frescobaldi, see
> https://github.com/frescobaldi/frescobaldi/issues/1232
> I have already fixed it in a pull request: Frescobaldi 3.1.2 will have it.


Will that work on Mac OS without the problems that have plagued the other
3.x versions of Fresco?


>
> Best wishes.
> Davide
>
-- 
Marnen Laibow-Koser mar...@marnen.org http://www.marnen.org Sent from Gmail
Mobile

Re: 64-bit Mac build of 2.20 is now available!

[Davide Liessi]

Il giorno mar 17 mar 2020 alle ore 22:36 Arle Lommel
 ha scritto:
> #2: Update.ly doesn’t work for me when invoked from Frescobaldi. I get this 
> message about a bad CPU type when I run it from Frescobaldi.

Known problem, depending only on Frescobaldi, see
https://github.com/frescobaldi/frescobaldi/issues/1232
I have already fixed it in a pull request: Frescobaldi 3.1.2 will have it.

Best wishes.
Davide

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 6:48 PM Marnen Laibow-Koser 
wrote:

> On Tue, Mar 17, 2020 at 6:43 PM Arle Lommel  wrote:
>
>> Glad my feedback seems to be useful.
>>
>> [cutting a bit here]
>>
>> Thanks, this makes sense.  I should be able to set the variables
>> correctly (and actually, the lilypond "binary" in the app bundle is already
>> a script that sets a few variables and calls the real executable, so
>> putting a few more in there should not be a problem).
>>
>> I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 for
>> this bug.  Feel free to subscribe there for updates, or to create new
>> issues there if they're problems with the 64-bit Mac packaging rather than
>> LilyPond itself.
>>
>>
>> Great. Glad it seems solvable.
>>
>
> Yeah, if it's just a question of setting a few variables, it shouldn't be
> too hard to fix.
>

...but that isn't the case.  Setting those variables (which were actually
already set in my shell anyway) appears to have no effect.  Moreover, it's
only GhostScript choking on these filenames, not LilyPond.  See the GitLab
issue for more.

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 6:43 PM Arle Lommel  wrote:

> Glad my feedback seems to be useful.
>
> [cutting a bit here]
>
> Thanks, this makes sense.  I should be able to set the variables correctly
> (and actually, the lilypond "binary" in the app bundle is already a script
> that sets a few variables and calls the real executable, so putting a few
> more in there should not be a problem).
>
> I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 for
> this bug.  Feel free to subscribe there for updates, or to create new
> issues there if they're problems with the 64-bit Mac packaging rather than
> LilyPond itself.
>
>
> Great. Glad it seems solvable.
>

Yeah, if it's just a question of setting a few variables, it shouldn't be
too hard to fix.


>
> #2: Update.ly  doesn’t work for me when invoked from
>> Frescobaldi.
>>
>
> You mean convert-ly?
>
>
> Yes. My mistake.
>
>  I get this message about a bad CPU type when I run it from Frescobaldi.
>
> Weird, I haven't seen that.  I'll try to reproduce.  What version of Mac
> OS are you running?
>
>
> I’m running 10.15.3 on a 2016 13” Touch Bar MacBook Pro. I’m using
> Frescobaldi 2.20.0. I seem to recall there are problems with the more
> recent versions on the Mac.
>

Hmm, I can't reproduce this on Mojave on my 2018 MacBook Pro (with the same
version of Fresco, FWIW).  Do you get this message with every file?  Do you
have a sample LilyPond file that you can share with me?


>
> Best,
>
> Arle
>

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 64-bit Mac build of 2.20 is now available!

[Arle Lommel]

Glad my feedback seems to be useful.

[cutting a bit here]

> Thanks, this makes sense.  I should be able to set the variables correctly 
> (and actually, the lilypond "binary" in the app bundle is already a script 
> that sets a few variables and calls the real executable, so putting a few 
> more in there should not be a problem).   
> 
> I've created https://gitlab.com/marnen/lilypond-mac-builder/-/issues/23 
>  for this bug.  
> Feel free to subscribe there for updates, or to create new issues there if 
> they're problems with the 64-bit Mac packaging rather than LilyPond itself.

Great. Glad it seems solvable.

> #2: Update.ly  doesn’t work for me when invoked from 
> Frescobaldi.
> 
> You mean convert-ly?

Yes. My mistake.

>  I get this message about a bad CPU type when I run it from Frescobaldi.
> 
> Weird, I haven't seen that.  I'll try to reproduce.  What version of Mac OS 
> are you running?

I’m running 10.15.3 on a 2016 13” Touch Bar MacBook Pro. I’m using Frescobaldi 
2.20.0. I seem to recall there are problems with the more recent versions on 
the Mac.

Best,

Arle

Re: 64-bit Mac build of 2.20 is now available!

[Marnen Laibow-Koser]

On Tue, Mar 17, 2020 at 12:10 PM Zone Dremik  wrote:

> A Big Thank You to Marnen Laibow-Koser —  Mac OS 64 bit Lilypond 2.20
> downloaded, installed and is running! This is a huge relief since my skill
> level is basically; download file and drag to application folder.
>
> The only thing not running quite as expected is convert.ly updating. It
> isn't flagging the syntax differences. It does execute without error
> messages and it changes the version number.
>

I thought that if it was run from the LilyPad app bundle, it would just
silently update the whole file (I don't like that behavior, but it seemed
to be design in LilyPad).  I'll admit that I haven't tested it thoroughly,
though; if you run it from within Frescobaldi, you at least see the diff.
Is it missing syntax differences?  If so, I'd appreciate a sample file that
it's not behaving properly on.

Not a huge problem, since any instances of the old syntax (2.18.2) get
> highlighted during the compile anyway.
>

If convert-ly is working properly, there shouldn't *be* any of the old
syntax left.  If there are, that *is* a huge problem and means that the
version I packaged is broken.  Is that the case?

Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org

Re: 64-bit Mac build of 2.20 is now available!

[Zone Dremik]

 A Big Thank You to Marnen Laibow-Koser —  Mac OS 64 bit Lilypond 2.20 
downloaded, installed and is running! This is a huge relief since my skill 
level is basically; download file and drag to application folder.

The only thing not running quite as expected is convert.ly updating. It isn't 
flagging the syntax differences. It does execute without error messages and it 
changes the version number.
Not a huge problem, since any instances of the old syntax (2.18.2) get 
highlighted during the compile anyway. 

I'm still running Mac System 10.14 (Mojave) but I will upgrade to OS 15 as time 
and the slow rolling Covid-19 disaster allows.

Be well everyone,
Zon D.


 On Wednesday, March 11, 2020, 01:53:27 PM EDT, Marnen Laibow-Koser 
 wrote:  
 
 Folks--
I've just published 64-bit Mac builds of 2.20 at 
https://bintray.com/marnen/lilypond-darwin-64/lilypond-2.20.0 .  Enjoy, and 
please let me know if you run into any issues: it appears to work, but I 
haven't tested it exhaustively.
Best,
-- 
Marnen Laibow-Koser
mar...@marnen.org
http://www.marnen.org  

Re: 64-bit Mac build of 2.20 is now available! (Marnen Laibow-Koser)

[Allan Kinnaird]

Yayy!! Although the Frescobaldi “LilyPond Documentation” menu command crashes. 
Minor problem.
Thanks Marnen!

> On 11 Mar 2020, at 20:34, lilypond-user-requ...@gnu.org wrote:
> 
> Send lilypond-user mailing list submissions to
>   lilypond-user@gnu.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>   https://lists.gnu.org/mailman/listinfo/lilypond-user
> or, via email, send a message with subject or body 'help' to
>   lilypond-user-requ...@gnu.org
> 
> You can reach the person managing the list at
>   lilypond-user-ow...@gnu.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: Markup in chordmode (Klaus Blum)
>   2. 64-bit Mac build of 2.20 is now available! (Marnen Laibow-Koser)
>   3. Re: Markup in chordmode (Carl Sorensen)
>   4. Re: Markup in chordmode (Noeck)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 11 Mar 2020 09:30:57 -0700 (MST)
> From: Klaus Blum 
> To: lilypond-user@gnu.org
> Subject: Re: Markup in chordmode
> Message-ID: <1583944257448-0.p...@n5.nabble.com>
> Content-Type: text/plain; charset=us-ascii
> 
> Hi Pablo, 
> 
> 
> pablocordal wrote
>> I'm trying to add a markup in the first chord of this music (but I get an
>> error)
>> 
>> How can I add ^\markup {"Var. 1"}  to the first chord?
> 
> You can put an invisible rest in parallel and attach your markup to it:
> 
> % -
> <<
>  \chordmode { c,,1:3.5.8 }
>  {s1^\markup "Var. 1"}
>>> 
> 
> \chordmode { 
>  c,,2:3.5.8 d,,2:3.5.8 e,,4:3.5.8 f,,2
>  % /+c:3.5.8  
>  r4   \bar "|."
> }
> % -
> 
> BTW: Ly 2.19.83 complained of the expression 
> f,,2/+c:3.5.8  
> That's why i commented it out. AFAIK after the slash you can only add a bass
> note but no other pitches after a colon. 
> 
> Cheers, 
> Klaus
> 
> 
> 
> 
> 
> --
> Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html
> 
> 
> 
> --
> 
> Message: 2
> Date: Wed, 11 Mar 2020 13:53:10 -0400
> From: Marnen Laibow-Koser 
> To: LilyPond , LilyPond Users
>   
> Cc: Zone Dremik 
> Subject: 64-bit Mac build of 2.20 is now available!
> Message-ID:
>   
> Content-Type: text/plain; charset="utf-8"
> 
> Folks--
> 
> I've just published 64-bit Mac builds of 2.20 at
> https://bintray.com/marnen/lilypond-darwin-64/lilypond-2.20.0 .  Enjoy, and
> please let me know if you run into any issues: it appears to work, but I
> haven't tested it exhaustively.
> 
> Best,
> -- 
> Marnen Laibow-Koser
> mar...@marnen.org
> http://www.marnen.org
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Message: 3
> Date: Wed, 11 Mar 2020 18:22:52 +
> From: Carl Sorensen 
> To: Pablo Cordal , "lilypond-user@gnu.org"
>   
> Subject: Re: Markup in chordmode
> Message-ID: <12bc974e-1e4e-4b93-ba96-3d20d78d6...@byu.edu>
> Content-Type: text/plain; charset="utf-8"
> 
> I have no idea what f,,2/+c:3.5.8 is supposed to mean, and that gives me an  
> error when I run your file.
> 
> Carl
> 
> 
> From: Pablo Cordal 
> Date: Wednesday, March 11, 2020 at 9:28 AM
> To: 
> Subject: Markup in chordmode
> 
> \version "2.18.2"
> #(ly:set-option 'midi-extension "midi")
> 
> \score {
>   <<
>\new StaffGroup
><<
>  \new Staff {
>\set Staff.instrumentName = #"Variciones"
>\set Staff.midiInstrument = #"acoustic grand"
>\clef "bass"
>\override Score.MetronomeMark.self-alignment-X = 1.5
>\override Score.MetronomeMark.Y-offset = 3.5
>\override Score.BarNumber.break-visibility = ##(#f #f #f)
>\time 4/4
>\numericTimeSignature
>\tempo 4 = 70
> 
>\chordmode {
> 
> c,,1:3.5.8  c,,2:3.5.8 d,,2:3.5.8 e,,4:3.5.8 f,,2/+c:3.5.8  r4   \bar "|."
> 
> }
>  }
>>> 
>>> 
> 
> \layout { indent = #15  }
> \midi { }
> 
> }
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Message: 4
> Date: Wed, 11 Mar 2020 21:34:50 +0100
> From: Noeck 
> To: lilypond-user@gnu.org
> Subject: Re: Markup in chordmode
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
> 
> Am 11.03.20 um 19:22 schrieb Carl Sorensen:
>> I have no idea what f,,2/+c:3.5.8 is supposed to mean, and that gives me
>> an  error when I run your file.
> 
> The order is important. The correct (working) syntax is:
> 
> \chordmode { f,,2:3.5.8/+c }
> 
> which is an f major chord with an additionall octave on top and a c,,
> below. Simply adding the 8 also adds the minor 7th and adding the 5
>