I don't suggest any significant changes in our input syntax. But I
>>want to point out that editing efficiency on that level_is_ an issue
>>we should keep taking into account when it comes to professional
>>work.
>Current LilyPond input tools, editors, and workflows suck. That is not
>LilyPond's "responsibility" as a command line tool, but of course it is
>something affecting its uptake nevertheless.
Frescobaldi doesn't suck! It is a very handy tool to enter lilypond code
with its code assistance. But for anyone used to another application, it
is a foreign tool-chain. I know so many people, who fear the switch from
MS Office to OpenOffice, because they are so different.