lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond 2.23.8 released


From: Freeman Gilmore
Subject: Re: LilyPond 2.23.8 released
Date: Wed, 27 Apr 2022 09:56:21 -0400



On Wed, Apr 27, 2022 at 6:55 AM David Kastrup <dak@gnu.org> wrote:
Freeman Gilmore <freeman.gilmore@gmail.com> writes:

> On Tue, Apr 26, 2022 at 7:58 PM David Kastrup <dak@gnu.org> wrote:
>
>> Freeman Gilmore <freeman.gilmore@gmail.com> writes:
>>
>> > Is there going to be a non binary version for windows coming soon?
>>
>> The source code is the same independent of operating system, so you
>> apparently don't mean "source code" when you say "non binary".  What
>> would your expectations of a "non binary version for windows" be?
>>
> Ok i see it now, but this was my problem.  I know that the source code
> (binary) is usually the same for all but I have never worked with
> source code for LilyPond so when I read this, "Documentation writers
> and testers will generally want to download the latest binary:" with 5
> binaries listed below, *Note, the colon should be a period;* and make
> it look like it is not the header for a listing.  I may not b the only
> dummy out there!.

I don't understand what you are saying here and you write things like
"source code (binary)"
I worded this wrong. I should have just used the word binaries.    I was mixing the two, disregarding Source code.
I do know the difference.    I was looking for a program for windows. Not being a programmer the header sentence says to use one of the following binaries{ at least that is how I read it.   So i was asking when the programs would be listed, not understanding that this was thmn and not binaries.     I have what I need now so no need to go any further with this..    
Thank you for your help with this, ƒg
that make pretty clear that we are still talking
i
about entirely different things.  So I repeat my question: what would
your expectations of a "non binary version for windows" be?

--
David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]