On 2/18/2018 3:44 PM, Mason Hock wrote:
This link doesn't work for you?
http://download.linuxaudio.org/lilypond/source/v2.19/
Mason
And the current downloads are listed and available here:
http://lilypond.org/downloads/binaries/
from the lilypond.org website:
http://lilypond.org/developmen
On 2/18/2018 3:44 PM, Mason Hock wrote:
This link doesn't work for you?
It does, but I copied your original message without double checking it -
you made a mistake and posted an "s" at the end of downloadI see it
now, yes it's online.
http://download.linuxaudio.org/lilypond/source/v2.1
This link doesn't work for you?
http://download.linuxaudio.org/lilypond/source/v2.19/
Mason
On 02/18, Ben wrote:
>
> On 2/18/2018 2:42 PM, Mason Hock wrote:
> > downloads.linuxaudio.org is working again, and the mirrors they host
> > including Lilypond's are back up. However, the newest versio
On 2/18/2018 2:42 PM, Mason Hock wrote:
downloads.linuxaudio.org is working again, and the mirrors they host including
Lilypond's are back up. However, the newest version up there is still 2.19.80.
When will 2.19.81 be added?
Thanks,
Mason
Hi,
It's still down for me here
_
downloads.linuxaudio.org is working again, and the mirrors they host including
Lilypond's are back up. However, the newest version up there is still 2.19.80.
When will 2.19.81 be added?
Thanks,
Mason
___
lilypond-user mailing list
lilypond-user@gnu.
- Original Message -
From: "Thomas Morley"
To: "David Nalesnik"
seems the work is done.
LSR is on 2.14
Thanks a lot for all your help!!
Harm
I'm catching up on the LSR emails, but thanks to both of you for the work
you've done here. Looking forward to 2.16
--
Phil Holme
Hi David,
Am 5. März 2012 01:07 schrieb David Nalesnik :
> Hi Harm,
>
>> I've just read the new description. Very nice!
>> Of course you're aware: doing a good job means that more work of this
>> kind will be offered. :)
>
>
> Ha, no problem.
>
> Oh, by the way, forgot to mention that I added to t
Hi Harm,
I've just read the new description. Very nice!
> Of course you're aware: doing a good job means that more work of this
> kind will be offered. :)
Ha, no problem.
Oh, by the way, forgot to mention that I added to the actual snippet
itself. Couldn't resist :)
-David
___
Hi again,
2012/3/5 David Nalesnik :
> Hi Harm,
>
> On Sun, Mar 4, 2012 at 5:50 PM, Thomas Morley
> wrote:
>>
>> Hi David,
>>
>>
>> Sorry, I've just sent a tarball to Sebastiano. I hope that all is correct.
>
>
> Everything compiles, and you fixed a number of things that didn't need
> fixing--that
Hi David,
2012/3/5 David Nalesnik :
> Hi Harm,
>
>>
>> I just finished rewriting the description a moment ago. I'll fix it once
>> the update is through.
>
>
> Anyway, I suppose I should add the file to the conversation. Please look
> through it and see if it's accurate, and I'll take care of ad
Hi Harm,
On Sun, Mar 4, 2012 at 5:50 PM, Thomas Morley wrote:
> Hi David,
>
> Sorry, I've just sent a tarball to Sebastiano. I hope that all is correct.
>
Everything compiles, and you fixed a number of things that didn't need
fixing--that has to be good enough :)
>
> THANKS A LOT FOR ALL YOUR
Hi Harm,
> I just finished rewriting the description a moment ago. I'll fix it once
> the update is through.
>
Anyway, I suppose I should add the file to the conversation. Please look
through it and see if it's accurate, and I'll take care of adding it when
the LSR is running 2.14.2.
Oh, and
Hi David,
2012/3/5 David Nalesnik :
> Hi,
>
> On Sun, Mar 4, 2012 at 5:16 PM, Graham Percival
> wrote:
>>
>> On Mon, Mar 05, 2012 at 12:07:09AM +0100, Thomas Morley wrote:
>> > I just downloaded the LSR.tarball from today and ran a last successful
>> > test.
>> > I'd like to send it to Sebastiano
Hi,
On Sun, Mar 4, 2012 at 5:16 PM, Graham Percival wrote:
> On Mon, Mar 05, 2012 at 12:07:09AM +0100, Thomas Morley wrote:
> > I just downloaded the LSR.tarball from today and ran a last successful
> test.
> > I'd like to send it to Sebastiano.
>
> Please do.
>
> > Shall we postpone the change o
On Mon, Mar 05, 2012 at 12:07:09AM +0100, Thomas Morley wrote:
> I just downloaded the LSR.tarball from today and ran a last successful test.
> I'd like to send it to Sebastiano.
Please do.
> Shall we postpone the change of the description for
> increasing-spacing-between-staves.ly?
No; if there
>> ; "lilypond-user"
>> Sent: Sunday, March 04, 2012 8:52 PM
>>
>> Subject: Re: LSR updates: was: polychords: a working solution
>>
>>
>>> Hi James,
>>>
>>> 2012/3/4 James :
>>>>
>>>> Phil,
>>>
il.com>; "lilypond-user"
> Sent: Sunday, March 04, 2012 8:52 PM
>
> Subject: Re: LSR updates: was: polychords: a working solution
>
>
> Hi James,
>>
>> 2012/3/4 James :
>>
>>> Phil,
>>>
>>> On 4 March 2012 18:30, Phil Holmes wrote
- Original Message -
From: "Thomas Morley"
To: "James"
Cc: "Phil Holmes" ; "David Nalesnik"
; "lilypond-user"
Sent: Sunday, March 04, 2012 8:52 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi James,
2012/3/4
Hi James,
2012/3/4 James :
> Phil,
>
> On 4 March 2012 18:30, Phil Holmes wrote:
>> - Original Message - From: "Thomas Morley"
>>
>> To: "David Nalesnik"
>> Cc: "lilypond-user"
>> Sent: Saturday, March 03, 2012 11:1
Phil,
On 4 March 2012 18:30, Phil Holmes wrote:
> - Original Message - From: "Thomas Morley"
>
> To: "David Nalesnik"
> Cc: "lilypond-user"
> Sent: Saturday, March 03, 2012 11:14 PM
> Subject: Re: LSR updates: was: polychords: a workin
- Original Message -
From: "Thomas Morley"
To: "David Nalesnik"
Cc: "lilypond-user"
Sent: Saturday, March 03, 2012 11:14 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi David,
2012/3/3 David Nalesnik :
Hi Harm,
I attached a tarb
Hi David,
2012/3/3 David Nalesnik :
> Hi Harm,
>
>>
>> I attached a tarball with all fixed files (hope it's not to big).
>> Perhaps you could test compiling them. IIRC you use windows, it should
>> make no difference, but who knows ...
>
>
> Everything compiles :) All I get are warnings with a fe
Hi Harm,
> I attached a tarball with all fixed files (hope it's not to big).
> Perhaps you could test compiling them. IIRC you use windows, it should
> make no difference, but who knows ...
>
Everything compiles :) All I get are warnings with a few of the files.
I've attached the trimmed-down
Hi Harm,
"staves swapped around" are not shown in the NR. So if we can make it
> work, the snippet is worth to keep.
>
I haven't been able to make this work either. Whenever I use negative
values as in the original snippet I get programming errors such as "insane
spring distance requested, igno
Hi David,
2012/3/1 David Nalesnik :
> Hi Harm,
>
> On Wed, Feb 29, 2012 at 6:57 PM, Thomas Morley
> wrote:
>>
>>
>> > Converting some files gave:
>> > "Not smart enough to convert minimum-Y-extent.
>> > Vertical spacing no longer depends on the Y-extent of a
>> > VerticalAxisGroup.
>> > Pl
Hi Harm,
On Wed, Feb 29, 2012 at 6:57 PM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
>
> > Converting some files gave:
> > "Not smart enough to convert minimum-Y-extent.
> > Vertical spacing no longer depends on the Y-extent of a
> VerticalAxisGroup.
> > Please refer to the manu
Hi,
2012/2/29 Thomas Morley :
> TODO
>
> Convert:
> Converting some files gave:
> "Not smart enough to convert minimum-Y-extent.
> Vertical spacing no longer depends on the Y-extent of a VerticalAxisGroup.
> Please refer to the manual for details, and update manually."
> (or sth similiar
- Original Message -
From: "Thomas Morley"
If you agree, what to do now?
I'll see how Sebastiano (maintainer of the LSR) is progressing on looking at
updating the binary on the LSR.
--
Phil Holmes
___
lilypond-user mailing list
lilyp
Hi Phil,
2012/2/28 Thomas Morley :
> Hi Phil,
>
> in the LSR-tarball I found the directory "correction-wanted", shall I
> fix these files too? (I'd think, some of them should be deleted)
>
> I didn't look in the other directories. It seems they contain only
> sorted duplicates. Or am I wrong?
>
>
Hi Phil,
in the LSR-tarball I found the directory "correction-wanted", shall I
fix these files too? (I'd think, some of them should be deleted)
I didn't look in the other directories. It seems they contain only
sorted duplicates. Or am I wrong?
Cheers,
Harm
__
Hi Phil,
2012/2/27 Phil Holmes :
> - Original Message - From: "Thomas Morley"
>
> To: "Phil Holmes"
> Cc: "lilypond-user"
> Sent: Sunday, February 26, 2012 10:30 PM
> Subject: Re: LSR updates: was: polychords: a working solution
>
&g
- Original Message -
From: "Thomas Morley"
To: "Phil Holmes"
Cc: "lilypond-user"
Sent: Sunday, February 26, 2012 10:30 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi Phil,
this step from CG 7.7 Updating LSR to a new version
&
Hi David,
2012/2/27 David Nalesnik :
> I realize that it's not necessary for an update that warnings be fixed, so
> feel free to ignore this :)
reducing the quantity of warnings is fine. I changed the file
according to your suggestion.
Thanks,
Harm
___
Forgot to reply to all:
Hi Harm,
>
>
> cross-staff-chords---beaming-problems-workaround.txt:cross-staff-chords---beaming-problems-workaround.ly:39
> :11:
> warning: ignoring too many clashing note columns
> --As expected! Same warnings as in 12.2.3
>
I realize that it's not necessary for an upda
Hi Phil,
this step from CG 7.7 Updating LSR to a new version
"2. Copy relevant snippets (i.e., snippets whose version is equal to
or less than the new version of LilyPond) from
‘Documentation/snippets/new/’ into the tarball."
is outstanding.
I don't know how to extract them other than manually and
Hi Harm,
On Sun, Feb 26, 2012 at 12:28 PM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
>
> many thanks for this and for your and David Kastrup's work on this
> intractable filtering-parts-from-the-command-line.ly file.
>
My pleasure! So, are there any other snippets that need looking
Hi David,
2012/2/26 David Nalesnik :
> This seems to do the trick:
[...]
many thanks for this and for your and David Kastrup's work on this
intractable filtering-parts-from-the-command-line.ly file.
Best,
Harm
___
lilypond-user mailing list
lilypon
Hi Harm,
On Sun, Feb 26, 2012 at 10:59 AM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
> Hi,
>
> in repeat-with-upbeat-and-different-durations-in-the-alternatives.ly (
> = http://lsr.dsi.unimi.it/LSR/Item?id=490 ) I want to avoid the
> warning, but I can't find a proper fix. All I can t
Hi,
in the preventing-final-mark-from-removing-final-tuplet.ly (=
http://lsr.dsi.unimi.it/LSR/Item?id=705 ) I noticed a bug with \set
tupletFullLength and \mark while using 2.14.2 and 2.15.30.
log:
warning: Found infinity or nan in output. Substituting 0.0
Made a bug-report about it.
For now I
Hi,
in repeat-with-upbeat-and-different-durations-in-the-alternatives.ly (
= http://lsr.dsi.unimi.it/LSR/Item?id=490 ) I want to avoid the
warning, but I can't find a proper fix. All I can think of is crude
and ugly:
{
\repeat volta 2 {
\partial 4
e'4
c'2
}
\alternative {
{
f'
Le 25/02/2012 15:54, David Nalesnik a écrit :
Thanks for trying this out, but I believe you're running the version with
the dummy Scheme lines I added. (I just tried it with 2.15.22 in its
original form, and it doesn't work.)
-David
Oh! You're right. I got all muddled up! Apologies for wast
David,
Thank you for your detailed explanations earlier in this thread.
On Fri, Feb 24, 2012 at 9:26 AM, David Kastrup wrote:
>
> #(newline) creates output. If you really want a filler of that sort,
> #(begin) is likely simplest.
I've made this substitution and fixed the unnecessary macro def
Thomas Morley writes:
> Hi,
>
> 2012/2/19 Thomas Morley :
>
>> use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.ly
>> I simply added added lowercase? To the definition of
>> my-chord-name->pop-markup
>> Of course lowercase? Is of no use here. A better fix would be more invasive.
>
> I mad
Phil,
On Fri, Feb 24, 2012 at 7:45 AM, Phil Hézaine wrote:
If it could help, compile fine here on 2.15.22 with the number version
> added.
>
>
Thanks for trying this out, but I believe you're running the version with
the dummy Scheme lines I added. (I just tried it with 2.15.22 in its
original f
2012/2/25 Thomas Morley :
> 2012/2/25 Thomas Morley :
>
>> I detected several other problematic files. :(
>
> Next:
> adding-a-figured-bass-above-or-below-the-notes.ly
>
> The command \once \override Staff.BassFigureAlignmentPositioning
> #'direction = #CENTER gives a log-warning (but worked in 2.1
2012/2/25 Thomas Morley :
> I detected several other problematic files. :(
Next:
adding-a-figured-bass-above-or-below-the-notes.ly
The command \once \override Staff.BassFigureAlignmentPositioning
#'direction = #CENTER gives a log-warning (but worked in 2.12.3):
programming error: direction unkn
Hi,
2012/2/24 Thomas Morley :
> Well, I have to do some clean up, but apart from this last file the
> main work seems to be done, so far normal users can do.
> Or missed I something?
>
> Thanks,
> Harm
I detected several other problematic files. :(
One of them is beams-across-line-breaks.ly.
It
Hi,
2012/2/19 Thomas Morley :
> use-custom-fonts-flat-b-and-sharp-#-symbols-for-chords.ly
> I simply added added lowercase? To the definition of
> my-chord-name->pop-markup
> Of course lowercase? Is of no use here. A better fix would be more invasive.
I made some additions. Now \set chordName
Phil Hézaine writes:
> Le 24/02/2012 05:54, David Nalesnik a écrit :
>> Hi,
>>
>> On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup wrote:
>>>
>>>
>>> I think it was something like \lyricsto "xxx" \music \musicfunction
>>> ... and it would likely already do to write \lyricsto "xxx" { \music }
>>> \
Le 24/02/2012 05:54, David Nalesnik a écrit :
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup wrote:
I think it was something like \lyricsto "xxx" \music \musicfunction
... and it would likely already do to write \lyricsto "xxx" { \music }
\musicfunction ...
I wasn't able to apply this
David Nalesnik writes:
> David,
>
> On Fri, Feb 24, 2012 at 12:44 AM, David Kastrup wrote:
>
> David Nalesnik writes:
>
> > I wasn't able to apply this to the snippet,
>
>
> Sigh.
>
> \lyricsto "chorus" \new Lyrics \txtChorus
> \lyricsto "verse" \ne
David,
On Fri, Feb 24, 2012 at 12:44 AM, David Kastrup wrote:
> David Nalesnik writes:
>
> > I wasn't able to apply this to the snippet,
>
> Sigh.
>
>\lyricsto "chorus" \new Lyrics \txtChorus
>\lyricsto "verse" \new Lyrics \txtVerseI
>\ifTargetIn ...
>
>
Sorry for being unclear: I d
David Nalesnik writes:
> Hi,
>
> On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup wrote:
>
>
> I think it was something like \lyricsto "xxx" \music
> \musicfunction
> ... and it would likely already do to write \lyricsto "xxx" {
> \music }
> \musicfunction ...
>
>
>
>
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup wrote:
>
>
> I think it was something like \lyricsto "xxx" \music \musicfunction
> ... and it would likely already do to write \lyricsto "xxx" { \music }
> \musicfunction ...
>
>
I wasn't able to apply this to the snippet, but I managed to make t
Thomas Morley writes:
> Hi David,
>
> 2012/2/21 David Kastrup :
>> Thomas Morley writes:
>>
>>> I didn't manage to fix:
>>> filtering-parts-from-the-command-line.ly
>>
>> You just did not try hard enough. It was a really obscure bug in the
>> lexer. I'll commit a fix to staging once make check
David Nalesnik writes:
> Hi,
>
> > It means that you had no chance due to that bug. David has
> fixed
> > the bug, so stay tuned for 2.15.31 whenever it comes out.
>
>
> Possibly stupid question: does this mean that the LSR update will need
> to bypass 2.14.2 and wait for stab
Hi,
> It means that you had no chance due to that bug. David has fixed
> > the bug, so stay tuned for 2.15.31 whenever it comes out.
>
Possibly stupid question: does this mean that the LSR update will need to
bypass 2.14.2 and wait for stable 2.16?
-David
___
Hi Graham,
2012/2/24 Graham Percival :
> On Thu, Feb 23, 2012 at 11:37:12PM +0100, Thomas Morley wrote:
>> Hi David,
>>
>> 2012/2/21 David Kastrup :
>> > You just did not try hard enough. It was a really obscure bug in the
>> > lexer. I'll commit a fix to staging once make check goes through.
>>
On Thu, Feb 23, 2012 at 11:37:12PM +0100, Thomas Morley wrote:
> Hi David,
>
> 2012/2/21 David Kastrup :
> > You just did not try hard enough. It was a really obscure bug in the
> > lexer. I'll commit a fix to staging once make check goes through.
>
> not sure I understand.
David's trying to b
Hi David,
2012/2/21 David Kastrup :
> Thomas Morley writes:
>
>> I didn't manage to fix:
>> filtering-parts-from-the-command-line.ly
>
> You just did not try hard enough. It was a really obscure bug in the
> lexer. I'll commit a fix to staging once make check goes through.
not sure I understan
Hi David N, David K,
2012/2/21 David Nalesnik :
> David,
>
>
> On Tue, Feb 21, 2012 at 11:10 AM, David Kastrup wrote:
>>
>>
>> Sorry for the unnecessary work caused by not thinking about this
>> sufficiently from your point of view. And sorry for the "it does not
>> take a genius" tone of my pre
Thomas Morley writes:
> I didn't manage to fix:
> filtering-parts-from-the-command-line.ly
You just did not try hard enough. It was a really obscure bug in the
lexer. I'll commit a fix to staging once make check goes through.
I think I need a beer.
--
David Kastrup
___
David,
On Tue, Feb 21, 2012 at 11:10 AM, David Kastrup wrote:
>
> Sorry for the unnecessary work caused by not thinking about this
> sufficiently from your point of view. And sorry for the "it does not
> take a genius" tone of my previous message that was uncalled for, stupid
> and offensive.
David Nalesnik writes:
> On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup wrote:
>
> So please check with the _current_ convert-ly. It has an option
>
> -t, --to=VERSION convert to VERSION [default: 2.15.31]
>
> for telling it at which version to stop. You don't
David,
On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup wrote:
> David Kastrup writes:
>
> > David Nalesnik writes:
> >
> >> David,
> >>
> >> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
> >>
> >> Uh, convertrules.py converts interval-translate to coord-translate
> >> so
> >>
Thomas Morley writes:
> Hi David,
>
> 2012/2/20 David Kastrup :
>> Thomas Morley writes:
>>
>>> Hi David, Phil,
>>>
>>> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
>>> km away from my home)
>>> May I ask you to continue the updating work?
>>
>> I'm just going to take a
David Kastrup writes:
> David Nalesnik writes:
>
>> David,
>>
>> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>>
>> Uh, convertrules.py converts interval-translate to coord-translate
>> so
>> where is the actual problem?
>>
>>
>>
>> Certainly coord-translate is th
David Nalesnik writes:
> David,
>
> On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>
> Uh, convertrules.py converts interval-translate to coord-translate
> so
> where is the actual problem?
>
>
>
> Certainly coord-translate is the natural fix (thank you!), but when I
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup wrote:
>
> Uh, convertrules.py converts interval-translate to coord-translate so
> where is the actual problem?
>
>
Certainly coord-translate is the natural fix (thank you!), but when I run
convert-ly and the snippet is updated to 2.14.0, this
David Nalesnik writes:
> David,
>
> On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup wrote:
>
> Thomas Morley writes:
>
> > 2012/2/19 David Kastrup :
>
>
> > Furthermore, I realized, that there seems to be no conversion
> rule for
> > the following 2.12.3-defini
David,
On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup wrote:
> Thomas Morley writes:
>
> > 2012/2/19 David Kastrup :
>
> > Furthermore, I realized, that there seems to be no conversion rule for
> > the following 2.12.3-definitions:
> >
> > From 2.12.3: \scm\lily-library.scm
> >
> >(define
Hi David,
2012/2/20 David Nalesnik :
> Hi Harm,
>
> On Mon, Feb 20, 2012 at 2:25 PM, Thomas Morley
> wrote:
>>
>>
>> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
>> km away from my home)
>> May I ask you to continue the updating work?
>
>
> Sure, I'll be happy to do what
Hi David,
2012/2/20 David Kastrup :
> Thomas Morley writes:
>
>> Hi David, Phil,
>>
>> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
>> km away from my home)
>> May I ask you to continue the updating work?
>
> I'm just going to take a look at the snippet you analyzed.
>
>
Hi Harm,
On Mon, Feb 20, 2012 at 2:25 PM, Thomas Morley <
thomasmorle...@googlemail.com> wrote:
>
>
> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
> km away from my home)
> May I ask you to continue the updating work?
>
Sure, I'll be happy to do what I can. I can certai
Thomas Morley writes:
> Hi David, Phil,
>
> I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
> km away from my home)
> May I ask you to continue the updating work?
I'm just going to take a look at the snippet you analyzed.
--
David Kastrup
__
Hi David, Phil,
I'll be offline for two days, perhaps three. (Visiting a funeral, ~800
km away from my home)
May I ask you to continue the updating work?
Best,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/li
- Original Message -
From: "Thomas Morley"
Phil: What to do with this file and the other deleting candidates
mentioned by Carl?
Keep a record of it and we'll get rid of it as part of the upgrade.
--
Phil Holmes
___
lilypond-user mailin
Hi David,
2012/2/20 David Kastrup :
>> Furthermore, I realized, that there seems to be no conversion rule for
>> the following 2.12.3-definitions:
>>
>> From 2.12.3: \scm\lily-library.scm
>>
>> (define (interval-translate iv amount)
>> (cons (+ amount (car iv))
>> (+ amount (cdr iv
Thomas Morley writes:
> 2012/2/19 David Kastrup :
>
>> So if it is not too much work to collect triplets of "version #, before,
>> after convert-ly, after correct change", it might be a nice base for
>> looking how to improve the convertrules file.
>
> as an example I use: overriding-automatic-be
Hi David, Phil,
2012/2/20 David Nalesnik :
> Hi again,
>
> On Sun, Feb 19, 2012 at 9:03 PM, David Nalesnik
> wrote:
>>
>>
>> Hi Harm,
>>
>> On Sun, Feb 19, 2012 at 11:51 AM, Thomas Morley
>> wrote:
>>>
>>>
>>> I didn't manage to fix:
>>>
>>> mixed-meter---automatic-compound-time-signatures.ly
>
Hi again,
On Sun, Feb 19, 2012 at 9:03 PM, David Nalesnik wrote:
>
> Hi Harm,
>
> On Sun, Feb 19, 2012 at 11:51 AM, Thomas Morley <
> thomasmorle...@googlemail.com> wrote:
>
>>
>> I didn't manage to fix:
>
> mixed-meter---automatic-compound-time-signatures.ly
>>
>
A little more exploring led me t
to work just fine, but given the substantial changes, I'm a bit
unsure of what I've done. Could you (and interested parties reading this)
try this out?
One question I have concerns the lines which are commented out (which are
updates of lines in the original snippet). Uncommenting them do
Hi David,
2012/2/19 David Kastrup :
> So if it is not too much work to collect triplets of "version #, before,
> after convert-ly, after correct change", it might be a nice base for
> looking how to improve the convertrules file.
as an example I use: overriding-automatic-beam-settings.ly
I atach
On 2/19/12 10:51 AM, "Thomas Morley" wrote:
>Hi David,
>
>2012/2/19 David Nalesnik :
>> Hi Harm,
>>
>> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes
>>wrote:
>>>
>>>
>>> 2) "correct" the syntax of the files you know have errors ready for
>>>that
>>> move. Which you do is up to you - bear in mi
Graham Percival writes:
> On Sun, Feb 19, 2012 at 07:27:31PM +0100, David Kastrup wrote:
>> So if it is not too much work to collect triplets of "version #, before,
>> after convert-ly, after correct change", it might be a nice base for
>> looking how to improve the convertrules file.
>
> David,
On Sun, Feb 19, 2012 at 07:27:31PM +0100, David Kastrup wrote:
> So if it is not too much work to collect triplets of "version #, before,
> after convert-ly, after correct change", it might be a nice base for
> looking how to improve the convertrules file.
David, are you volunteering to produce pa
Thomas Morley writes:
> 2012/2/19 David Kastrup :
>
>> Did you try using convert-ly?
>
> yes. But without complete success in the mentioned files.
It may also be an idea to use this as input for improving the convert-ly
rules. After all, they will presumably get exercised a lot more when
the ne
Hi David,
2012/2/19 David Kastrup :
> Thomas Morley writes:
>
>> Hi David,
>>
>> 2012/2/19 David Nalesnik :
>>> Hi Harm,
>>>
>>> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
2) "correct" the syntax of the files you know have errors ready for that
move. Which you do i
Hi Phil,
2012/2/19 Phil Holmes :
> It looks like what you've done is exactly right for preparing for updating
> the LSR. I think you have 2 options: 1) wait until we know that the LSR
> will be moved to 2.14 before doing anything else; or 2) "correct" the syntax
> of the files you know have erro
Thomas Morley writes:
> Hi David,
>
> 2012/2/19 David Nalesnik :
>> Hi Harm,
>>
>> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
>>>
>>>
>>> 2) "correct" the syntax of the files you know have errors ready for that
>>> move. Which you do is up to you - bear in mind that if you go for 2),
Hi David,
2012/2/19 David Nalesnik :
> Hi Harm,
>
> On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
>>
>>
>> 2) "correct" the syntax of the files you know have errors ready for that
>> move. Which you do is up to you - bear in mind that if you go for 2), then
>> it's possible that the work
I first suggested to put the column code because I think it would be probably
useful.
The polychord snippets would need a little more work, as I advance in the
theory class, i'll know which cases are pertinent to add, but still it could be
a good example.
I didn't realized there were two places
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes wrote:
>
> 2) "correct" the syntax of the files you know have errors ready for that
> move. Which you do is up to you - bear in mind that if you go for 2),
> then it's possible that the work will be wasted if we struggle to get the
> LSR u
Apologies for top-posting - I'm having problems with the way my Windows
machine is quoting text.
Also apologies, Thomas, for the late reply, and pointing you to a page
yesterday that you'd already read! It was getting past my bedtime and I
wasn't reading too accurately.
It looks like what y
Sven,
On Wed, Oct 26, 2011 at 10:22 AM, Sven Axelsson wrote:
> On 26 October 2011 02:59, Colin Campbell wrote:
>> On 11-10-25 07:38 AM, Sven Axelsson wrote:
>>>
>>> On 21 October 2011 00:52, Jon Chalk wrote:
I think I may have found a small problem with bagpipe.ly... Each
embell
On 26 October 2011 02:59, Colin Campbell wrote:
> On 11-10-25 07:38 AM, Sven Axelsson wrote:
>>
>> On 21 October 2011 00:52, Jon Chalk wrote:
>>>
>>> I think I may have found a small problem with bagpipe.ly... Each
>>> embellishment that uses \small should have a \normalsize after it.
>>
>> Man,
On 11-10-25 07:38 AM, Sven Axelsson wrote:
On 21 October 2011 00:52, Jon Chalk wrote:
I think I may have found a small problem with bagpipe.ly... Each
embellishment that uses \small should have a \normalsize after it.
Man, I can't believe I haven't noticed that before! Or anyone else
using ba
On 21 October 2011 00:52, Jon Chalk wrote:
> I think I may have found a small problem with bagpipe.ly... Each
> embellishment that uses \small should have a \normalsize after it.
Man, I can't believe I haven't noticed that before! Or anyone else
using bagpipe.ly for that matter.
Anyhow, for now
Adobe InDesign CS - 100
Ahead Nero v6.3 Powerpack - 40
Microsoft SQL Server 2000 Enterprise Edition - 200
Windows 2000 Server - 50
Microsoft Windows 2000 Professional - 50
Quark Express 6.0 - 60
Adobe Acrobat 6.0 Professional - 100
Borland Delphi 7 Professional - 70
Adobe Illustrator 10 - 80
Mac
New Q E M software
Nero V 6.0 Ultra Edition CD/DVD Burning Suite - 30
SuSe Linux 9.1 Professional Edition - 50
Diskeeper 8 Professional - 25
Nero V 6.0 Ultra Edition CD/DVD Burning Suite - 30
QuickBooks Premier 2004 - 110
QuarkXPress 6 Passport - 120
3D Home Architect V 6 Deluxe - 15
Pinnacle Stud
1 - 100 of 104 matches
Mail list logo
