Graham Percival wrote:
2010/2/19 Dénes Harmath <harmathde...@gmail.com>:
There should be an option in lilypond to invoke convert-ly on the files before
compiling. This way, the user doesn't have to care with updating the syntax of
her files manually; when updating LilyPond, files will be up to date
automatically when compiled.
convert-ly is not sufficiently automatic / foolproof to be worth doing
this. Feel free to write a script that runs convert-ly -e before
calling lilypond, but this will not be added to the LilyPond project
itself.
Also, since the main LilyPond programmers work primarily with UNIX, they
follow the UNIX paradigm of letting separate programs be responsible for
separate tasks. As Graham said, combining the two into a single command
is easily done using a script or could be included as an option into a
"development environment" (such as LilypondTool, or the LilyPond mode of
editors like Emacs or VIM).
Finally, I see several risks of confusions when using such an option. If
it did "convert-ly -e", then the file would have to be reloaded in the
text editor, manually or automatically depending on what editor you use.
If it instead kept the original file and let LilyPond process a
temporary copy with updated syntax, then the warning/error messages
would not point to relevant lines in the original file.
/Mats
/Mats
Cheers,
- Graham
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond