bug-lilypond
[Top][All Lists]
Advanced

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

Issue 1387 in lilypond: Enhancement: non-trivial convert-ly trace as a c


From: lilypond
Subject: Issue 1387 in lilypond: Enhancement: non-trivial convert-ly trace as a comment in .ly files
Date: Mon, 08 Nov 2010 11:13:50 +0000

Status: Accepted
Owner: ----
Labels: Type-Enhancement Priority-High convert-ly Maintainability

New issue 1387 by v.villenave: Enhancement: non-trivial convert-ly trace as a comment in .ly files
http://code.google.com/p/lilypond/issues/detail?id=1387

This feature has been suggested by Graham:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00160.html
"""
[It may be argued that] in-file comments are much more noticeable than console warning messages, and thus _any_ change which we current display a NOT_SMART rule on the console should instead be placed inside the file as a comment.
"
Carl:
"""
I couldn't like having such comments scattered throughout the file, [but] we could collect all the NOT_SMART output and put it as comments at the
top of the file.
"
Reinhold:
"""
Some things like property names will not necessarily print an error or a warning. In these cases, if you don't save the convert-ly output somewhere you will not notice that anything is wrong possibly until a score went to a publisher and it is too late...
"
Trevor:
"""
[In some NOT_SMART cases, we could even] add something which made compilation fail - in a way that clearly indicated the problem, of course. When running convert-ly on many files (like the LSR) inspecting every file for a comment would be laborious, although a simple script to look for the comment would be an alternative.
"

Of course, these comments should be made easy to grep. In a patch for Issue 1365, yours truly suggested the following syntax:
% [Convert-ly] Automatic comment text.

[I'm marking this as High-prio, since it may be a good idea not to release the next stable version without having seriously considered this enhancement suggestion. Feel free to lower the priority if needed.]




reply via email to

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