- Original Message -
From: Thomas Morley thomasmorle...@googlemail.com
To: David Nalesnik david.nales...@gmail.com
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
Hi David,
Am 5. März 2012 01:07 schrieb David Nalesnik david.nales...@gmail.com:
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
- Original Message -
From: Thomas Morley thomasmorle...@googlemail.com
To: David Nalesnik david.nales...@gmail.com
Cc: lilypond-user lilypond-user@gnu.org
Sent: Saturday, March 03, 2012 11:14 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi David,
2012/3/3 David
updates: was: polychords: a working solution
...
warning: MIDI channel wrapped around
warning: remapping modulo 16
I never saw them before during my testings. And I can't appraise them.
LIAR!
http://lists.gnu.org/archive/html/lilypond-devel/2011-06/msg00833.html
;)
I think if look
, March 03, 2012 11:14 PM
Subject: Re: LSR updates: was: polychords: a working solution
...
warning: MIDI channel wrapped around
warning: remapping modulo 16
I never saw them before during my testings. And I can't appraise them.
LIAR!
http://lists.gnu.org/archive/html/lilypond-devel/2011
@gnu.org
Sent: Saturday, March 03, 2012 11:14 PM
Subject: Re: LSR updates: was: polychords: a working solution
...
warning: MIDI channel wrapped around
warning: remapping modulo 16
I never saw them before during my testings. And I can't appraise them.
LIAR!
http://lists.gnu.org/archive/html
@gnu.org
Sent: Sunday, March 04, 2012 8:52 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi James,
2012/3/4 James pkx1...@gmail.com:
Phil,
On 4 March 2012 18:30, Phil Holmes m...@philholmes.net wrote:
- Original Message - From: Thomas Morley
thomasmorle
Nalesnik
david.nales...@gmail.com; lilypond-user lilypond-user@gnu.org
Sent: Sunday, March 04, 2012 8:52 PM
Subject: Re: LSR updates: was: polychords: a working solution
Hi James,
2012/3/4 James pkx1...@gmail.com:
Phil,
On 4 March 2012 18:30, Phil Holmes m...@philholmes.net 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 of the description for
increasing-spacing-between-staves.ly?
No; if there's
Hi,
On Sun, Mar 4, 2012 at 5:16 PM, Graham Percival gra...@percival-music.cawrote:
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
Hi David,
2012/3/5 David Nalesnik david.nales...@gmail.com:
Hi,
On Sun, Mar 4, 2012 at 5:16 PM, Graham Percival gra...@percival-music.ca
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.
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 Harm,
On Sun, Mar 4, 2012 at 5:50 PM, Thomas Morley thomasmorle...@googlemail.com
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 :)
Hi David,
2012/3/5 David Nalesnik david.nales...@gmail.com:
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
Hi again,
2012/3/5 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Mar 4, 2012 at 5:50 PM, Thomas Morley
thomasmorle...@googlemail.com 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
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 David,
2012/3/3 David Nalesnik david.nales...@gmail.com:
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
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 manual for
Hi David,
2012/3/1 David Nalesnik david.nales...@gmail.com:
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
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, ignoring
Hi,
2012/2/29 Thomas Morley thomasmorle...@googlemail.com:
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.
- Original Message -
From: Thomas Morley thomasmorle...@googlemail.com
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
___
Hi Phil,
2012/2/28 Thomas Morley thomasmorle...@googlemail.com:
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
Hi David,
2012/2/27 David Nalesnik david.nales...@gmail.com:
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
- Original Message -
From: Thomas Morley thomasmorle...@googlemail.com
To: Phil Holmes m...@philholmes.net
Cc: lilypond-user lilypond-user@gnu.org
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
Hi Phil,
2012/2/27 Phil Holmes m...@philholmes.net:
- Original Message - From: Thomas Morley
thomasmorle...@googlemail.com
To: Phil Holmes m...@philholmes.net
Cc: lilypond-user lilypond-user@gnu.org
Sent: Sunday, February 26, 2012 10:30 PM
Subject: Re: LSR updates: was: polychords
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,
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 {
{
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 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 think
Hi David,
2012/2/26 David Nalesnik david.nales...@gmail.com:
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
___
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 at?
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,
2012/2/24 Thomas Morley thomasmorle...@googlemail.com:
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
2012/2/25 Thomas Morley thomasmorle...@googlemail.com:
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):
2012/2/25 Thomas Morley thomasmorle...@googlemail.com:
2012/2/25 Thomas Morley thomasmorle...@googlemail.com:
I detected several other problematic files. :(
Next:
adding-a-figured-bass-above-or-below-the-notes.ly
The command \once \override Staff.BassFigureAlignmentPositioning
#'direction
Phil,
On Fri, Feb 24, 2012 at 7:45 AM, Phil Hézaine philippe.heza...@free.frwrote:
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
Thomas Morley thomasmorle...@googlemail.com writes:
Hi,
2012/2/19 Thomas Morley thomasmorle...@googlemail.com:
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.
David,
Thank you for your detailed explanations earlier in this thread.
On Fri, Feb 24, 2012 at 9:26 AM, David Kastrup d...@gnu.org 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
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
David Nalesnik david.nales...@gmail.com writes:
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup d...@gnu.org wrote:
I think it was something like \lyricsto xxx \music
\musicfunction
... and it would likely already do to write \lyricsto xxx {
\music }
David,
On Fri, Feb 24, 2012 at 12:44 AM, David Kastrup d...@gnu.org wrote:
David Nalesnik david.nales...@gmail.com writes:
I wasn't able to apply this to the snippet,
Sigh.
\lyricsto chorus \new Lyrics \txtChorus
\lyricsto verse \new Lyrics \txtVerseI
\ifTargetIn ...
Sorry
David Nalesnik david.nales...@gmail.com writes:
David,
On Fri, Feb 24, 2012 at 12:44 AM, David Kastrup d...@gnu.org wrote:
David Nalesnik david.nales...@gmail.com writes:
I wasn't able to apply this to the snippet,
Sigh.
\lyricsto chorus \new
Le 24/02/2012 05:54, David Nalesnik a écrit :
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrupd...@gnu.org 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
Phil Hézaine philippe.heza...@free.fr writes:
Le 24/02/2012 05:54, David Nalesnik a écrit :
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrupd...@gnu.org wrote:
I think it was something like \lyricsto xxx \music \musicfunction
... and it would likely already do to write \lyricsto xxx {
Hi,
2012/2/19 Thomas Morley thomasmorle...@googlemail.com:
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
Hi David N, David K,
2012/2/21 David Nalesnik david.nales...@gmail.com:
David,
On Tue, Feb 21, 2012 at 11:10 AM, David Kastrup d...@gnu.org 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
Hi David,
2012/2/21 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@googlemail.com 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
On Thu, Feb 23, 2012 at 11:37:12PM +0100, Thomas Morley wrote:
Hi David,
2012/2/21 David Kastrup d...@gnu.org:
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
Hi Graham,
2012/2/24 Graham Percival gra...@percival-music.ca:
On Thu, Feb 23, 2012 at 11:37:12PM +0100, Thomas Morley wrote:
Hi David,
2012/2/21 David Kastrup d...@gnu.org:
You just did not try hard enough. It was a really obscure bug in the
lexer. I'll commit a fix to staging once
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
David Nalesnik david.nales...@gmail.com 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
Thomas Morley thomasmorle...@googlemail.com writes:
Hi David,
2012/2/21 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@googlemail.com 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
Hi,
On Thu, Feb 23, 2012 at 9:27 PM, David Kastrup d...@gnu.org 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
David,
On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup d...@gnu.org wrote:
Thomas Morley thomasmorle...@googlemail.com writes:
2012/2/19 David Kastrup d...@gnu.org:
Furthermore, I realized, that there seems to be no conversion rule for
the following 2.12.3-definitions:
From 2.12.3:
David Nalesnik david.nales...@gmail.com writes:
David,
On Mon, Feb 20, 2012 at 5:01 AM, David Kastrup d...@gnu.org wrote:
Thomas Morley thomasmorle...@googlemail.com writes:
2012/2/19 David Kastrup d...@gnu.org:
Furthermore, I realized, that there seems to
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup d...@gnu.org 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
David Nalesnik david.nales...@gmail.com writes:
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup d...@gnu.org wrote:
Uh, convertrules.py converts interval-translate to coord-translate
so
where is the actual problem?
Certainly coord-translate is the natural
David Kastrup d...@gnu.org writes:
David Nalesnik david.nales...@gmail.com writes:
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup d...@gnu.org wrote:
Uh, convertrules.py converts interval-translate to coord-translate
so
where is the actual problem?
Thomas Morley thomasmorle...@googlemail.com writes:
Hi David,
2012/2/20 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@googlemail.com 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
David,
On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup d...@gnu.org wrote:
David Kastrup d...@gnu.org writes:
David Nalesnik david.nales...@gmail.com writes:
David,
On Tue, Feb 21, 2012 at 9:24 AM, David Kastrup d...@gnu.org wrote:
Uh, convertrules.py converts
David Nalesnik david.nales...@gmail.com writes:
On Tue, Feb 21, 2012 at 10:37 AM, David Kastrup d...@gnu.org 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
David,
On Tue, Feb 21, 2012 at 11:10 AM, David Kastrup d...@gnu.org 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
Thomas Morley thomasmorle...@googlemail.com 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
Hi David, Phil,
2012/2/20 David Nalesnik david.nales...@gmail.com:
Hi again,
On Sun, Feb 19, 2012 at 9:03 PM, David Nalesnik david.nales...@gmail.com
wrote:
Hi Harm,
On Sun, Feb 19, 2012 at 11:51 AM, Thomas Morley
thomasmorle...@googlemail.com wrote:
I didn't manage to fix:
Thomas Morley thomasmorle...@googlemail.com writes:
2012/2/19 David Kastrup d...@gnu.org:
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
Hi David,
2012/2/20 David Kastrup d...@gnu.org:
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
- Original Message -
From: Thomas Morley thomasmorle...@googlemail.com
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
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
Thomas Morley thomasmorle...@googlemail.com 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 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 certainly
Hi David,
2012/2/20 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@googlemail.com 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
Hi David,
2012/2/20 David Nalesnik david.nales...@gmail.com:
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
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
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net 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
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
Hi David,
2012/2/19 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net 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
Thomas Morley thomasmorle...@googlemail.com writes:
Hi David,
2012/2/19 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net wrote:
2) correct the syntax of the files you know have errors ready for that
move. Which you do
Hi Phil,
2012/2/19 Phil Holmes m...@philholmes.net:
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
Hi David,
2012/2/19 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@googlemail.com writes:
Hi David,
2012/2/19 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net wrote:
2) correct the syntax of the files you know
Thomas Morley thomasmorle...@googlemail.com writes:
2012/2/19 David Kastrup d...@gnu.org:
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
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
Graham Percival gra...@percival-music.ca 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
On 2/19/12 10:51 AM, Thomas Morley thomasmorle...@googlemail.com wrote:
Hi David,
2012/2/19 David Nalesnik david.nales...@gmail.com:
Hi Harm,
On Sun, Feb 19, 2012 at 8:32 AM, Phil Holmes m...@philholmes.net
wrote:
2) correct the syntax of the files you know have errors ready for
that
Hi David,
2012/2/19 David Kastrup d...@gnu.org:
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
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
I took a look at this file, and I came up with the attached. What I've
done seems to work just fine, but given the
Hi again,
On Sun, Feb 19, 2012 at 9:03 PM, David Nalesnik david.nales...@gmail.comwrote:
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
87 matches
Mail list logo
