janek.lilypond wrote > However, I think when discussing case-sensitiveness, we agreed to a > following convention: LilyPond should differentiate between upper- and > lowercase, but no commands/properties/etc. should differ only by case.
so the validity of a command/property/etc. can be checked by setting both the user input and the internal LilyPond expectation to lowercase and that's it! with this we can write /down DoWn dOwN down DOWN/ or whatever contains these 4 letters in this order same with keyCancellation (or is it KeyCancellation?) one well known problem of course is \score and \Score quoting Joram: /… it is more important to make things easy for users / Eluze -- View this message in context: http://lilypond.1069038.n5.nabble.com/shall-we-rename-X-offset-and-similar-to-lowercase-tp143209p143372.html Sent from the Dev mailing list archive at Nabble.com. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
