Re: 64-bit MacBook Air M2 problems

[Ian West]

Thanks gentlemen. You have been most helpful.
I am motoring with the 2.22.0 manual; so far everything is working. When it 
does not, I shall search out the 2.20 as you suggest.
I started to load Frescobaldi, and indeed downloaded 
MacPorts-2.7.2-12-Monterey.pkg. But could not face it. I have seen command line 
used, once, but would have to look up how to use it. Too much I fear.
Anyway, there is something very satisfying about the ‘longhand’ approach to 
writing music. I had one of the first copies of Sibelius sold (running on an 
Archimedes computer), but threw it and the Archimedes out and refused to buy 
another as the company would not credit me the £500 I had already spent. Made 
do with ABC,  Noteworthy and suchlike till I found Lilypond. They say it is not 
the arrival but the travelling, and I think it may apply here; but you know you 
are travelling when you get a score at the end. Compare a wordprocessor and 
setting type into a tray.
Viva Lilypond!
Best wishes, Ian West

---
Ian West
9 Thenford Road, Middleton Cheney,
BANBURY, OX17 2NB,
Tel: 01295 713 889; (Mobile: 07474 572 588)
==

> On 16 Aug 2022, at 21:41, Jean Abou Samra  wrote:
> 
> 
> 
>> Le 16 août 2022 à 22:16, Ian West  a écrit :
>> 
>> 
>> I reset my laptop to abolish 'smart quotes' . Successful. But there must be 
>> other subtleties that are frustrating me.
> 
> 
> If you have issues, please tell what they are, or we cannot do anything to 
> help you :-)
> 
> Have you tried setting up Frescobaldi as I recommended?
> 
> 
>> Perhaps if I type the text with textedit, then copy and paste to feed it to 
>> Ly. Or just change the suffix from .txt to .ly?
>> 
>> It has proved impossible to find a manual for version 2.20.0. What is it 
>> that I am doing wrong?
> 
> 
> Take the 2.22 manual
> 
> https://lilypond.org/doc/v2.22/Documentation/notation/index.fr.html 
> 
> 
> and replace "2.22" in the URL with "2.20", giving
> 
> https://lilypond.org/doc/v2.20/Documentation/notation/index.fr.html 
> 
> 
> 
>> I am inclined to think that, if Google cannot find it, then it does not 
>> exist. I do not know which would be better: use 2.18.x or 2.22.x?
> 
> 
> In theory, 2.22.x, which is the latest stable version, but to my knowledge 
> you won’t find a macOS 64-bit download for it like the unofficial bundle of 
> LilyPond 2.20. You have to use either MacPorts or HomeBrew, which are package 
> managers for macOS. If you don’t know how to use the command line or what it 
> even is, this is not recommended. Instead, use 2.23, which while being a 
> development release series is quite stable currently, and has official macOS 
> 64-bit binaries.
> 
> Best,
> Jean
> 
> 
> 
>> Ian West
>> 
>> 
>>> On 16 Aug 2022, at 11:08, Ian West >> > wrote:
>>> 
>>> Thanks Hans, and Jean.
>>> I shall try and learn up those tricks. 
>>> Ian
>>> 
>>> ==
 On 15 Aug 2022, at 17:01, Hans Åberg >>> > wrote:
 
 
> On 15 Aug 2022, at 17:57, Jean Abou Samra  > wrote:
> 
> Also, when you enter the apostrophe from the keyboard, is it really
> a straight apostrophe  ->   '   <-  or could it be that macOS does
> you the “favor” to replace it with a curly apostrophe ->’ <- ?
> LilyPond expects straight apostrophes. If this is the problem, you need
> to fix your macOS settings somewhere to prevent those “smart quotes”.
 
 One can turn those off at System Preferences → Keyboard → Text → Use smart 
 quotes and dashes. Those are reachable at least from the keyboard map I am 
 using, so I decided to type them by hand at need.
 
 Also, one can add custom text replacements, which I use for example for 
 the arrows above.
 
 
>>> 
>> 

Re: 64-bit MacBook Air M2 problems

[Jean Abou Samra]

Le 18/08/2022 à 14:18, Ian West a écrit :

Thanks gentlemen. You have been most helpful.

  * I am motoring with the 2.22.0 manual; so far everything is
working. When it does not, I shall search out the 2.20 as you suggest.
  * I started to load Frescobaldi, and indeed downloaded
MacPorts-2.7.2-12-Monterey.pkg. But could not face it. I have seen
command line used, once, but would have to look up how to use it.
Too much I fear.




You don't know to know how to use the command line in order to use
the .pkg installer. Quoting the tutorial: “In the Finder, double-click
on the file to run the installer.” It's as simple as that :-)

Best,
Jean

Re: 64-bit MacBook Air M2 problems

[Hans Åberg]

[List changed to LilyPond-User, from LilyPond-Devel.]

> On 16 Aug 2022, at 22:16, Ian West  wrote:
> 
> I reset my laptop to abolish 'smart quotes' . Successful. But there must be 
> other subtleties that are frustrating me. Perhaps if I type the text with 
> textedit, then copy and paste to feed it to Ly. Or just change the suffix 
> from .txt to .ly?

You might try Frescobaldi, which is in effect an integrated development system 
for LilyPond. Both type and compile from within the app.

The program 'lilypond' does not care about the filename other than that if the 
filename extension is '.ly' it can be omitted when passed as argument, and 
there may be some more.

The extension might also be set so that if it ends on ".ly" some favorite app 
is opened, say Frescobaldi.

If one has a lot of these filename extensions to set, one can use the System 
Preferences pane RCDefaultApp by Rubicode, which is for free. It may require 
changing something in Security & Privacy to work.

Otherwise, in general, it is set from the Finder in the pop-up menu for the 
file "Open With…", or Info on the file.

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
> 

Re: 64 bit

[Hans Åberg]

> On 11 Nov 2019, at 19:04, Jonathan Armitage  
> wrote:
> 
> On 11/11/2019 15:32, Eric wrote:
>> On the assumption that it would have been pointed out if this link was 
>> dangerous phished spam (apologies, Mr Sorensen!!) I have decided to install 
>> this development version to replace my slashed-out 32-bit Lilyponds. Has 
>> anyone else - or are others who use Mac Catalina waiting for Lilypond 2.20 
>> to possibly include a 64-bit version (if even then) linked from the Lilypond 
>> site?
> 
> I took the plunge and upgraded my Mac Mini to Catalina (not without other 
> difficulties which are still coming out of the woodwork) and installed Hans's 
> package, which seems to work perfectly well, apart from convert-ly as 
> mentioned elsewhere.
> 
> I am a Homebrew user, I do not have MacPorts installed.
> 
> I did have to recompile Qsynth myself. I cannot (so far) build Lilypond, 
> possibly because I cannot compile Guile 1.8.8. This is not a big deal for me, 
> I am only a casual Lilypond user.
> 
> Thank you, Hans.

You are welcome. It is a self-contained installer that install into 
/opt/lilypond/, made from MacPorts lilypond-devel without requiring it, 
maintained by Walter, who helped cutting down on the installer size.

Re: 64 bit

[Carl Sorensen]

From: Eric 
Date: Monday, November 11, 2019 at 8:32 AM
To: 
Subject: Re: 64 bit

On the assumption that it would have been pointed out if this link was 
dangerous phished spam (apologies, Mr Sorensen!!) I have decided to install 
this development version to replace my slashed-out 32-bit Lilyponds. Has anyone 
else - or are others who use Mac Catalina waiting for Lilypond 2.20 to possibly 
include a 64-bit version (if even then) linked from the Lilypond site? I can't 
seem to find much followup on this topic, and nothing? in our mailing list 
(maybe I need to search better) that mentions the below (rather unusually 
large, maybe because 64-bit?) unofficial development update.


Eric,

I’m not sure what you are waiting for.

Right now, we are at the point where there is no way for us to make a lilypond 
64-bit version because we need the Apple Xcode software, and the license allows 
it to be only used on Apple hardware.  We do not have Apple build hardware, and 
as a GNU project, it’s unlikely that using Apple build hardware for all of our 
distributions would be acceptable to the team.

I think  it’s possible that we could get an approved binary eventually hosted 
on the LilyPond website.  A couple of developers are trying to make that happen.

In the meantime, Hans has provided an installable distributable package created 
in MacPorts, which is at the link referred to below.  I’ve mirrored that link 
on a site that might be considered to be less dangerous for spam or phishing:

  https://www.et.byu.edu/~sorensen/lilypond-devel-2.19.83_2.mpkg

I’m only aware of one person who has installed that package, and they found 
that it works and it is a 64-bit package.

You can read more about this on the lilypond-devel archives:

https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00059.html
https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00272.html

https://lists.gnu.org/archive/html/lilypond-devel/2019-10/msg00063.html

I think our best hope going forward is for Marnen to succeed in making a 64-bit 
lilypond.app.  I really hope he’s successful.

Thanks,

Carl



On Thu, Oct 17, 2019 at 10:47 PM 
mailto:lilypond-user-requ...@gnu.org>> wrote:
Send lilypond-user mailing list submissions to
lilypond-user@gnu.org<mailto: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<mailto:lilypond-user-requ...@gnu.org>

You can reach the person managing the list at
lilypond-user-ow...@gnu.org<mailto: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:Lilypond on OS X Catalina (Chris Crossen)
   2. Re:Lilypond on OS X Catalina (Chris Crossen)
   3. Re:Lilypond on OS X Catalina (Carl Sorensen)
   4. Re:64 bit (Carl Sorensen)



-- Forwarded message --
From: Chris Crossen mailto:ch...@crossen.net>>
To: Allan Kinnaird mailto:akinna...@icloud.com>>
Cc: Carl Sorensen mailto:c_soren...@byu.edu>>, 
"lilypond-user@gnu.org<mailto:lilypond-user@gnu.org>" 
mailto:lilypond-user@gnu.org>>
Bcc:
Date: Thu, 17 Oct 2019 17:29:39 -0700
Subject: Re: Lilypond on OS X Catalina


> On Oct 17, 2019, at 4:48 PM, Allan Kinnaird via lilypond-user 
> mailto:lilypond-user@gnu.org>> wrote:
>
> Thanks, Carl - I haven’t upgraded to Catalina myself for exactly that reason 
> (and Lilypond is my only significant 32-bit app!). I’ll see if I can work out 
> how to use Hans’s version.
> Allan

I have Catalina installed on a Mac laptop. I downloaded the installer and am 
running it now. I’ll report back when I have some results to share.








-- Forwarded message --
From: Chris Crossen mailto:ch...@crossen.net>>
To: Allan Kinnaird mailto:akinna...@icloud.com>>, Carl 
Sorensen mailto:c_soren...@byu.edu>>, 
"lilypond-user@gnu.org<mailto:lilypond-user@gnu.org>" 
mailto:lilypond-user@gnu.org>>
Cc:
Bcc:
Date: Thu, 17 Oct 2019 18:46:46 -0700
Subject: Re: Lilypond on OS X Catalina


> On Oct 17, 2019, at 5:29 PM, Chris Crossen 
> mailto:ch...@crossen.net>> wrote:
>
>> Thanks, Carl - I haven’t upgraded to Catalina myself for exactly that reason 
>> (and Lilypond is my only significant 32-bit app!). I’ll see if I can work 
>> out how to use Hans’s version.
>> Allan
>
> I have Catalina installed on a Mac laptop. I downloaded the installer and am 
> running it now. I’ll report back when I have some results to share.

The install was successful. I didn’t know where it installed, but found it in 
/opt/lilypond .

It successfully generated a correct-looking pdf and midi (I’ll verify them 
tomorrow) from a single s

Re: 64 bit

[Jonathan Armitage]

On 11/11/2019 15:32, Eric wrote:
On the assumption that it would have been pointed out if this link was 
dangerous phished spam (apologies, Mr Sorensen!!) I have decided to 
install this development version to replace my slashed-out 32-bit 
Lilyponds. Has anyone else - or are others who use Mac Catalina waiting 
for Lilypond 2.20 to possibly include a 64-bit version (if even then) 
linked from the Lilypond site?


I took the plunge and upgraded my Mac Mini to Catalina (not without 
other difficulties which are still coming out of the woodwork) and 
installed Hans's package, which seems to work perfectly well, apart from 
convert-ly as mentioned elsewhere.


I am a Homebrew user, I do not have MacPorts installed.

I did have to recompile Qsynth myself. I cannot (so far) build Lilypond, 
possibly because I cannot compile Guile 1.8.8. This is not a big deal 
for me, I am only a casual Lilypond user.


Thank you, Hans.

Jon

Re:64 bit

[Mario Bolognani]

I am a LilyPond user on MacOsX and am anxiously waiting for a 64bit version of 
LilyPond, before installing Catalina. I am managing a baroque music site 
(baroque music.it) with many followers and at present I can’t evolve my 
transcription platform for this 64bit problem. 

Best wishes

Mario Bolognani
email:  mario.bologn...@gmail.com
www.baroquemusic.it

Re: 64 bit

[Eric]

On the assumption that it would have been pointed out if this link was
dangerous phished spam (apologies, Mr Sorensen!!) I have decided to install
this development version to replace my slashed-out 32-bit Lilyponds. Has
anyone else - or are others who use Mac Catalina waiting for Lilypond 2.20
to possibly include a 64-bit version (if even then) linked from the
Lilypond site? I can't seem to find much followup on this topic, and
nothing? in our mailing list (maybe I need to search better) that mentions
the below (rather unusually large, maybe because 64-bit?) unofficial
development update.

On Thu, Oct 17, 2019 at 10:47 PM  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:Lilypond on OS X Catalina (Chris Crossen)
>2. Re:Lilypond on OS X Catalina (Chris Crossen)
>    3. Re:Lilypond on OS X Catalina (Carl Sorensen)
>4. Re:64 bit (Carl Sorensen)
>
>
>
> -- Forwarded message --
> From: Chris Crossen 
> To: Allan Kinnaird 
> Cc: Carl Sorensen , "lilypond-user@gnu.org" <
> lilypond-user@gnu.org>
> Bcc:
> Date: Thu, 17 Oct 2019 17:29:39 -0700
> Subject: Re: Lilypond on OS X Catalina
>
>
> > On Oct 17, 2019, at 4:48 PM, Allan Kinnaird via lilypond-user <
> lilypond-user@gnu.org> wrote:
> >
> > Thanks, Carl - I haven’t upgraded to Catalina myself for exactly that
> reason (and Lilypond is my only significant 32-bit app!). I’ll see if I can
> work out how to use Hans’s version.
> > Allan
>
> I have Catalina installed on a Mac laptop. I downloaded the installer and
> am running it now. I’ll report back when I have some results to share.
>
>
>
>
>
>
>
>
> -- Forwarded message --
> From: Chris Crossen 
> To: Allan Kinnaird , Carl Sorensen <
> c_soren...@byu.edu>, "lilypond-user@gnu.org" 
> Cc:
> Bcc:
> Date: Thu, 17 Oct 2019 18:46:46 -0700
> Subject: Re: Lilypond on OS X Catalina
>
>
> > On Oct 17, 2019, at 5:29 PM, Chris Crossen  wrote:
> >
> >> Thanks, Carl - I haven’t upgraded to Catalina myself for exactly that
> reason (and Lilypond is my only significant 32-bit app!). I’ll see if I can
> work out how to use Hans’s version.
> >> Allan
> >
> > I have Catalina installed on a Mac laptop. I downloaded the installer
> and am running it now. I’ll report back when I have some results to share.
>
> The install was successful. I didn’t know where it installed, but found it
> in /opt/lilypond .
>
> It successfully generated a correct-looking pdf and midi (I’ll verify them
> tomorrow) from a single source file (no includes but english.ly). The
> file was already version 2.19. I’ll try using convert-ly and more complex
> files tomorrow.
>
> Since this may not be of general interest, please give me some guidance on
> whether to continue posting to the group or confine it to those interested.
>
>
>
>
>
>
>
>
>
>
>
>
> -- Forwarded message --
> From: Carl Sorensen 
> To: Chris Crossen , Allan Kinnaird <
> akinna...@icloud.com>, "lilypond-user@gnu.org" 
> Cc:
> Bcc:
> Date: Fri, 18 Oct 2019 02:42:37 +
> Subject: Re: Lilypond on OS X Catalina
>
>
> On 10/17/19, 7:46 PM, "Chris Crossen"  wrote:
>
>
>
> > On Oct 17, 2019, at 5:29 PM, Chris Crossen 
> wrote:
> >
> >> Thanks, Carl - I haven’t upgraded to Catalina myself for exactly
> that reason (and Lilypond is my only significant 32-bit app!). I’ll see if
> I can work out how to use Hans’s version.
> >> Allan
> >
> > I have Catalina installed on a Mac laptop. I downloaded the
> installer and am running it now. I’ll report back when I have some results
> to share.
>
> The install was successful. I didn’t know where it installed, but
> found it in /opt/lilypond .
>
> That's where it was supposed to be.
>
> It successfully generated a correct-looking pdf and midi (I’ll verify
> them tomorrow) from a single source file (no includes but english.ly).
> The file was already version 2.19. I’ll try using convert-ly and more
> complex files tomorrow.
>
> Yes, it was made from the latest deve

Re: 64 bit

[Carl Sorensen]

From: "marco.massobrio" 
Date: Tuesday, October 15, 2019 at 11:12 PM
To: 
Subject: 64 bit


I Havel installed catalina 10.15 on my Mac andiamo lilypond 2.19.83 don't run
HELP!


Install the package from here:  https://web2.storegate.com/share/oCQjV4r

HTH,

Carl

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6 and Catalina 10.15

[Hans Åberg]

> On 16 Oct 2019, at 23:08, Thomas Scharkowski  
> wrote:
> 
>  Original-Nachricht 
>>> On 16 Oct 2019, at 21:54, Thomas Scharkowski  
>>> wrote:
>>> 
>>>  Original-Nachricht 
> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
> wrote:
> 
> I am cautious and did not upgrade to 10.15 Catalina yet.
> 
> On my current (10.14.6) system lilypond-devel does not build:
> 
>> error: expected initializer before '__OSX_AVAILABLE_STARTING'
>> https://trac.macports.org/ticket/59130
> 
> Would this be different on Catalina?
 The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it 
 yet, though.
> I'd rather try to build lilypond-devel on my working system before 
> upgrading.
 It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 
 10 (which you might try).
 Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying 
 because stuff is updated rather fast right now.
>>> 
>>> Ok, I'll try to downgrade to Xcode 10.
>> I believe one can have them side-by-side and use xcode-select to choose, 
>> though I haven’t tried it.
> lilypond-devel built with Xcode 10.3 on MacOS 10.14.6!
> :-)

Good, meanwhile, the port lilypond-devel seems to work on MacOS 10.15, or at 
least a small snippet compiled.

> Thank you,

You are welcome.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Thomas Scharkowski]

 Original-Nachricht 



On 16 Oct 2019, at 21:54, Thomas Scharkowski  wrote:

 Original-Nachricht 

On 16 Oct 2019, at 18:35, Thomas Scharkowski  wrote:

I am cautious and did not upgrade to 10.15 Catalina yet.

On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Would this be different on Catalina?

The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.

I'd rather try to build lilypond-devel on my working system before upgrading.

It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).
Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.


Ok, I'll try to downgrade to Xcode 10.


I believe one can have them side-by-side and use xcode-select to choose, though 
I haven’t tried it.




lilypond-devel built with Xcode 10.3 on MacOS 10.14.6!
:-)
Thank you,
Thomas

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Hans Åberg]

> On 16 Oct 2019, at 21:54, Thomas Scharkowski  
> wrote:
> 
>  Original-Nachricht 
>>> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
>>> wrote:
>>> 
>>> I am cautious and did not upgrade to 10.15 Catalina yet.
>>> 
>>> On my current (10.14.6) system lilypond-devel does not build:
>>> 
 error: expected initializer before '__OSX_AVAILABLE_STARTING'
 https://trac.macports.org/ticket/59130
>>> 
>>> Would this be different on Catalina?
>> The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it 
>> yet, though.
>>> I'd rather try to build lilypond-devel on my working system before 
>>> upgrading.
>> It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 
>> 10 (which you might try).
>> Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying 
>> because stuff is updated rather fast right now.
> 
> Ok, I'll try to downgrade to Xcode 10.

I believe one can have them side-by-side and use xcode-select to choose, though 
I haven’t tried it.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Thomas Scharkowski]

 Original-Nachricht 



On 16 Oct 2019, at 18:35, Thomas Scharkowski  wrote:

I am cautious and did not upgrade to 10.15 Catalina yet.

On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Would this be different on Catalina?


The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.


I'd rather try to build lilypond-devel on my working system before upgrading.


It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).

Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.



Ok, I'll try to downgrade to Xcode 10.

Thomas

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Werner LEMBERG]

 error: expected initializer before '__OSX_AVAILABLE_STARTING'
 https://trac.macports.org/ticket/59130
>>
>> Try to install gcc9, then retry installation of lilypond-devel
>> (with `port clean lilypond-devel' before doing that).
>
> I have already done this - no success.

OK.  Unfortunately, I can't help more.


Werner



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Hans Åberg]

> On 16 Oct 2019, at 18:35, Thomas Scharkowski  
> wrote:
> 
> I am cautious and did not upgrade to 10.15 Catalina yet.
> 
> On my current (10.14.6) system lilypond-devel does not build:
> 
> > error: expected initializer before '__OSX_AVAILABLE_STARTING'
> > https://trac.macports.org/ticket/59130
> 
> Would this be different on Catalina?

The port lilypond-devel just installed on MacOS 10.15. I haven’t tried it yet, 
though.

> I'd rather try to build lilypond-devel on my working system before upgrading.

It seems to be a problem with Xcode 11. It built on MacOS 10.14 with Xcode 10 
(which you might try).

Also run ‘port selfupdate’ and 'port upgrade outdated’ before retrying because 
stuff is updated rather fast right now.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Thomas Scharkowski]

 Original-Nachricht 



On my current (10.14.6) system lilypond-devel does not build:


error: expected initializer before '__OSX_AVAILABLE_STARTING'
https://trac.macports.org/ticket/59130


Try to install gcc9, then retry installation of lilypond-devel (with
`port clean lilypond-devel' before doing that).


 Werner


Thank you,

I have already done this - no success.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit - MacPorts lilypond-devel on Mojave 10.14.6

[Werner LEMBERG]

> On my current (10.14.6) system lilypond-devel does not build:
> 
>> error: expected initializer before '__OSX_AVAILABLE_STARTING'
>> https://trac.macports.org/ticket/59130

Try to install gcc9, then retry installation of lilypond-devel (with
`port clean lilypond-devel' before doing that).


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Werner LEMBERG]

>>> Maybe if a compiler is not listed as a dependency, it will just
>>> take what is currently installed.
>> 
>> Yes.
> 
> So perhaps it suffices to remove it from the lilypond-devel
> dependency list to get it to install.

What dependency?


Werner

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Hans Åberg]

> On 16 Oct 2019, at 15:53, Mario Bolognani  wrote:
> 
> is there any simple way to run Frescobaldi+LilyPond on Catalina? Maybe in a 
> not so delayed future?

It is also in MacPorts:
% port info frescobaldi
frescobaldi @2.20.0_1 (editors, python)

% port info frescobaldi-devel
frescobaldi-devel @20180806 (editors, python)

> Your suggestions are for experienced users not for musicians with an amateur 
> approach to the platform?

It is not difficult to install and run MacPorts. The problem discussed is that 
not everything has been updated yet.

To install MacPorts, download the installer here and run it:
  https://www.macports.org/install.php



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Hans Åberg]

> On 16 Oct 2019, at 15:37, Werner LEMBERG  wrote:
> 
>> Maybe if a compiler is not listed as a dependency, it will just take
>> what is currently installed.
> 
> Yes.

So perhaps it suffices to remove it from the lilypond-devel dependency list to 
get it to install.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Werner LEMBERG]

> It may be the case that only lilypond-devel is actively maintained,

Probably true.  I only take care of `lilypond-devel' and know nothing
of `lilypond'.

> but it was reported on the devel list that the dependency gcc8
> didn’t build.

The patch to fall back to gcc9 has been applied to the git repository
already.

> Curiously, it is not listed as a dependency for port lilypond.

MacPorts tries to avoid explicit dependencies on compilers.  Instead,
possibly working compilers are added to the fallback list, and not
working compilers are added to the blacklist.

> Maybe if a compiler is not listed as a dependency, it will just take
> what is currently installed.

Yes.


Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Hans Åberg]

> On 16 Oct 2019, at 09:09, Alan Shaw  wrote:
> 
> PS By doing this I got 2.18.2.

This is 'sudo port install lilypond’. It may be the case that only 
lilypond-devel is actively maintained, but it was reported on the devel list 
that the dependency gcc8 didn’t build. Curiously, it is not listed as a 
dependency for port lilypond. Maybe if a compiler is not listed as a 
dependency, it will just take what is currently installed.



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Alan Shaw]

PS By doing this I got 2.18.2.

On Wed, Oct 16, 2019 at 12:06 AM Alan Shaw  wrote:

> Here's what I did:
> 1.
> https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/
> (step 17, sudo make install, failed, but I ran it again and it succeeded.)
> 2. https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00040.html
>
> Both of these took a very long time because many dependencies had to be
> installed. Take a long lunch.
>
> On Tue, Oct 15, 2019 at 10:12 PM marco.massobrio <
> marco.massob...@gmail.com> wrote:
>
>>
>> I Havel installed catalina 10.15 on my Mac andiamo lilypond 2.19.83 don't
>> run
>> HELP!
>>
>> Inviato da smartphone Samsung Galaxy.
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit

[Alan Shaw]

Here's what I did:
1.
https://www.ghostwheel.com/2019/09/05/installing-macports-on-macos-10-15-catalina-beta-7/
(step 17, sudo make install, failed, but I ran it again and it succeeded.)
2. https://lists.gnu.org/archive/html/lilypond-user/2019-03/msg00040.html

Both of these took a very long time because many dependencies had to be
installed. Take a long lunch.

On Tue, Oct 15, 2019 at 10:12 PM marco.massobrio 
wrote:

>
> I Havel installed catalina 10.15 on my Mac andiamo lilypond 2.19.83 don't
> run
> HELP!
>
> Inviato da smartphone Samsung Galaxy.
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit font problems in GUB

[Phil Holmes]

- Original Message - 
From: Simon Bailey si...@bailey.at

To: lilypond-user Mailinglist lilypond-user@gnu.org
Sent: Thursday, January 23, 2014 9:20 AM
Subject: 64-bit font problems in GUB



Hello,

I kicked this thread off last week sometime:
http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00762.html
TL/DR summary: ligatures were not being shown for lilypond-generated 
output.


further investigation led me to:
http://lists.gnu.org/archive/html/lilypond-user/2014-01/msg00804.html

TL/DR summary: GUB lilypond packages for 32-bit show ligatures, 64-bit
packages do not.
I verified this on a stock fedora 20 installation using the 2.18.0
packages downloaded from lilypond.org. the Mac OSX packages
distributed through lilypond.org also show the same behaviour, i.e. no
ligatures. for testing purposes, i have also verified this behaviour
with the latest 2.19.1 releases.

I followed these instructions:
http://nicolas.sceaux.free.fr/index.php/2008/01/20/26-building-lilypond-from-git-sources-on-mac-os-105-intel
(adapting them somewhat for more modern builds and interpolating with
INSTALL.txt -- removed the kpathsea options, had to install some extra
ports).
after building lilypond (showing version 2.19.2) on my mac, using the
font libraries installed by MacPorts, ligatures are shown.

I will build lilypond from source on my linux box later today; I
expect the bevaviour to be the same as on OS X -- i.e. the ligatures
will work.

This leads me to conclude that there seems to be a problem with the
64-bit version of the font libraries in the build system for the
release packages. Can anyone comment on this? Should I forward this
information to the bug list?



Yes.

--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit font problems in GUB

[Simon Bailey]

On Thu, Jan 23, 2014 at 10:36 AM, Phil Holmes m...@philholmes.net wrote:
 - Original Message - From: Simon Bailey si...@bailey.at
...SNIP SNAP...
 This leads me to conclude that there seems to be a problem with the
 64-bit version of the font libraries in the build system for the
 release packages. Can anyone comment on this? Should I forward this
 information to the bug list?

 Yes.

done.

-- 
Do not meddle in the affairs of trombonists, for they are subtle and
quick to anger.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[Ed Gordijn]

 Now I see what you're getting at. So, assuming a user never
 compiles/renders/outputs their score, just merely does the inputting,
their
 process is not going to increase RAM usage practically at all, right?

Well, than you don't use Lilypond, do you?

Greeting, Ed
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[Janek Warchoł]

2013/12/31 SoundsFromSound soundsfromso...@gmail.com:

 Now I see what you're getting at. So, assuming a user never
 compiles/renders/outputs their score, just merely does the inputting, their
 process is not going to increase RAM usage practically at all, right? It's
 the compiling where LilyPond eats up resources in large projects?


As Ed wrote, the only time when LIlyPond program actually runs is when
it compiles a file.  LilyPond doesn't do anything else - editing the
files is done using text editors.
See for yourself - you won't find a lilypond process running in the
system except during compilation.

Janek

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[David Kastrup]

Janek Warchoł janek.lilyp...@gmail.com writes:

 2013/12/31 SoundsFromSound soundsfromso...@gmail.com:

 Now I see what you're getting at. So, assuming a user never
 compiles/renders/outputs their score, just merely does the inputting, their
 process is not going to increase RAM usage practically at all, right? It's
 the compiling where LilyPond eats up resources in large projects?


 As Ed wrote, the only time when LIlyPond program actually runs is when
 it compiles a file.  LilyPond doesn't do anything else - editing the
 files is done using text editors.
 See for yourself - you won't find a lilypond process running in the
 system except during compilation.

Well... if I get around to working on the Emacs mode at some point of
time, it is likely that there will be a LilyPond process running
continuously (or rather, sitting at a GUILE command line prompt) that
Emacs will use for translating note languages, figure out syntax,
convert absolute to relative, transpose and so on.

But it's not more than hot air right now.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[David Kastrup]

Jay Anderson horndud...@gmail.com writes:

 On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
 soundsfromso...@gmail.com wrote:
 Wow, really? I never thought editing text files (.ly) would ever get close
 to 4GB of RAM. Maybe I'll try a quick benchmark here...

 6.9GB for one book to be exact. Text editing has nothing to do with it
 though. This is the amount of memory used to compile the project. This
 specific book is a much larger than most for sure (633 pages (9x12) of
 piano + horn music). I doubt most people would notice a difference
 between 32-bit and 64-bit installs.

Also a cell is larger on 64bit systems, so a 32bit system uses less
memory.  With 4GB of memory and no swap (swapping on SSD is a bad idea),
a 32bit system might get along better than a 64bit system with the
available memory.  8GB of main memory is the no-brainer threshold for
using a 64bit system.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[Jay Anderson]

On Mon, Dec 30, 2013 at 8:03 PM, SoundsFromSound
soundsfromso...@gmail.com wrote:
 I usually don't think twice about this sort of thing, I always reach for x64
 installers since all my systems here are 64bit. The only exception maybe is
 something like Python or something odd that is finicky...

 But, as far as LilyPond goes, is there any real-world benefit to using the
 64bit install (on a 64bit OS) vs. the 32bit install (on 64bit OS)? Does RAM
 ever really being to be an issue with LilyPond? I've never seen resource
 spikes at all so maybe I'm just the minority here, but could someone tell me
 what the differences are between these installers?

For some of my larger projects memory usage climbs above 4GB (max
32-bit address space). So using 64-bit is very nice. I've never
benchmarked speed of 32-bit versus 64-bit though.

-Jay

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[SoundsFromSound]

Jay Anderson wrote
 On Mon, Dec 30, 2013 at 8:03 PM, SoundsFromSound
 lt;

 soundsfromsound@

 gt; wrote:
 I usually don't think twice about this sort of thing, I always reach for
 x64
 installers since all my systems here are 64bit. The only exception maybe
 is
 something like Python or something odd that is finicky...

 But, as far as LilyPond goes, is there any real-world benefit to using
 the
 64bit install (on a 64bit OS) vs. the 32bit install (on 64bit OS)? Does
 RAM
 ever really being to be an issue with LilyPond? I've never seen resource
 spikes at all so maybe I'm just the minority here, but could someone tell
 me
 what the differences are between these installers?
 
 For some of my larger projects memory usage climbs above 4GB (max
 32-bit address space). So using 64-bit is very nice. I've never
 benchmarked speed of 32-bit versus 64-bit though.
 
 -Jay
 
 ___
 lilypond-user mailing list

 lilypond-user@

 https://lists.gnu.org/mailman/listinfo/lilypond-user

Wow, really? I never thought editing text files (.ly) would ever get close
to 4GB of RAM. Maybe I'll try a quick benchmark here...

Thanks!



-
composer | sound designer 
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/64-bit-vs-32-bit-LilyPond-GNU-Linux-tp156754p156758.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[Jay Anderson]

On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
soundsfromso...@gmail.com wrote:
 Wow, really? I never thought editing text files (.ly) would ever get close
 to 4GB of RAM. Maybe I'll try a quick benchmark here...

6.9GB for one book to be exact. Text editing has nothing to do with it
though. This is the amount of memory used to compile the project. This
specific book is a much larger than most for sure (633 pages (9x12) of
piano + horn music). I doubt most people would notice a difference
between 32-bit and 64-bit installs.

-Jay

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64-bit vs 32-bit LilyPond (GNU/Linux)

[SoundsFromSound]

Jay Anderson wrote
 On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
 lt;

 soundsfromsound@

 gt; wrote:
 Wow, really? I never thought editing text files (.ly) would ever get
 close
 to 4GB of RAM. Maybe I'll try a quick benchmark here...
 
 6.9GB for one book to be exact. Text editing has nothing to do with it
 though. This is the amount of memory used to compile the project. This
 specific book is a much larger than most for sure (633 pages (9x12) of
 piano + horn music). I doubt most people would notice a difference
 between 32-bit and 64-bit installs.
 
 -Jay
 
 ___
 lilypond-user mailing list

 lilypond-user@

 https://lists.gnu.org/mailman/listinfo/lilypond-user

Now I see what you're getting at. So, assuming a user never
compiles/renders/outputs their score, just merely does the inputting, their
process is not going to increase RAM usage practically at all, right? It's
the compiling where LilyPond eats up resources in large projects?



-
composer | sound designer 
LilyPond Tutorials (for beginners) -- http://bit.ly/bcl-lilypond
--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/64-bit-vs-32-bit-LilyPond-GNU-Linux-tp156754p156771.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 64 bit addressing and Lilypond

[Patrick McCarty]

On Sun, Mar 22, 2009 at 02:58:33AM -0400, Craig Bakalian wrote:
 Hi,
   I am just curious, is anyone running a 64 bit chip with Lilypond on  
 Windows Vista or some form of Linux?  If so, how is it working.

I run LilyPond on a 32-bit and 64-bit machine (Arch Linux), and it
works great on both.

I primarily compile LilyPond from scratch, but the GUB builds
available from LilyPond's download page also work fine for me.


-Patrick


___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user