Am 16.11.2016 um 10:48 schrieb David Kastrup: > "we have seen only one case where LilyPond actually shows a limitation" > is disingenuous: this is a clear and well-known architectural limit of > the current code base's operation and it is by far not trivial to > overcome.
What I was referring to is mainly that among the huge haystack of code, examples and claimed bugs I can see only one that might actually qualify as a bug. > But the long and the short of it is that LilyPond does have limitations > in that area. That they are irrelevant to the vast majority of use > cases people have for typesetting music does not mean that there is a > point in discussing them away: mclaren is not wrong about them being > there, and on that point he will "win" any "discussion". I do not question this in any way. Of course if an actual bug or limitation is determined it should be put on the bug list to be tackled in appropriate order. The point is that a) as you, David, have expressed more than once there's no use insulting those who would be able to help (somehow this reminds me of an old woman constantly shouting at her nurses) and b) that it's completely inappropriate to make fun of LilyPond's proclaimed total incompetence at performing even "ridiculously simple" tasks while in fact these tasks are extremely complex and most other programs wouldn't even let you *think* of even starting with them. Urs _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user