Robert Hickman <robehick...@gmail.com> writes: >> Trying to understand LilyPond syntax based on how it actually >> processes input is not likely to make learning easy since a lot of >> complicated mechanisms work behind the scenes in order to make things >> look easy. > > In my general experience, systems which try to be cleaver and are not > explicit about what they are doing tend to break in weird, unexpected > ways. Complex abstractions always leak. It is also a constant burden > on the user if they have to remember that some things are added > implicitly.
It turns out I have some bits of specific experience with LilyPond and its design and its users in addition to non-trivial amounts of general experience to rely on. It may save you some headaches to just trust me on that. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
