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 c
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-
[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
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 m
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 funct
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 shou
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
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/fl
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-var
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 Le
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
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
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
>
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
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 gu
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 tha
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
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 Frescobal
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 i
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
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-spaci
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
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 (Melo
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 m
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
cras
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 on
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/frescobal
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 "bi
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 variable
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
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 runni
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
flagg
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
> 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 slash
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
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 Ca
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 Bolo
ond-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)
>
>
>
> -- Forwar
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
__
> 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 cautio
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
> 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:
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.macport
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
> 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
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-d
> 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).
>>> 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
___
> 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
> 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.
___
> 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
> 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
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.g
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 b
On Thu, Jan 23, 2014 at 10:36 AM, Phil Holmes wrote:
> - Original Message - From: "Simon Bailey"
<...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 com
- Original Message -
From: "Simon Bailey"
To: "lilypond-user Mailinglist"
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 sum
Janek Warchoł writes:
> 2013/12/31 SoundsFromSound :
>>
>> 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 wher
Jay Anderson writes:
> On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
> 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
> t
2013/12/31 SoundsFromSound :
>
> 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
> 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
_
Jay Anderson wrote
> On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
> <
> soundsfromsound@
> > 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
On Mon, Dec 30, 2013 at 8:55 PM, SoundsFromSound
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 memor
Jay Anderson wrote
> On Mon, Dec 30, 2013 at 8:03 PM, SoundsFromSound
> <
> soundsfromsound@
> > 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
On Mon, Dec 30, 2013 at 8:03 PM, SoundsFromSound
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 LilyPo
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 bo
65 matches
Mail list logo
