Hi Noeck,
I think that problem does point you really to the paths configured.
Check (on Linux or OSX, sorry I don't use Wxx for this) these command-
line commands:
$ which lilypond
$ which convert-ly
$ lilypond --version
$ convert-ly --version
(Wxx doesn't know the "which" commands, but should produce output with
the --version switches)
Check for consistency in paths, versions, etc. Match it with what
Frescobaldi tells you (menu settings -- configure Frescobaldi).
If the convert-ly (menu Lilypond -- source -- etc.) stays greyed out,
check if you did not already convert it (once is enoough!), next run
should produce a window stating this file is already up-to-date,
Frescobaldi might also puts some comments in your file to remember
this. Try setting the version-number in the file to something else.
Regards,
Wim.
(mail me the output if you have troubled interpreting)
On 16 Nov 2012, at 20:51 , Noeck wrote:
Am 16.11.2012 08:43, schrieb Thomas Scharkowski:
Thomas Scharkowski wrote
Hello all,
I noticed a strange behaviour of convert-ly in LilyPond 2.17
today:
Converting a 2.15.25 file with 2.17.6 gives:
Now I tried convert-ly 2.17.6 from the terminal and it works like
expected.
Hi Joram,
thank you for you suggestion, but this is not the reason - the
complete
path to convert-ly was already set.
Thomas
Now, I've tested it and I can't even run convert-ly from version
2.16 to
2.17.6 in frescobaldi, the Ok-button is greyed out.
So there seems to be something wrong, even if I can't reproduce your
findings here.
Joram
_______________________________________________
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
