lilyp...@googlecode.com writes: > Comment #2 on issue 1396 by v.villenave: Enhancement: an option to > turn unterminated ties into slurs > http://code.google.com/p/lilypond/issues/detail?id=1396 > > Well, one could make the opposite argument: what's the point in *not* > treating a~b as a slur? (At least, from a "lax" user's point of view, > as Johan mentioned in his first email.) > > (FTR: As I explained on the list, *I* am not convinced that this is > needed at all. But some people, including David, seemingly agreed that > it would be a nice "feature" to have.)
Uh, David is so bad at expressing his opinions that you should be wary of rephrasing him. Basically, I objected to a) the availability of tiewaitfornote being an obstacle to making a~b behave as a slur b) having a~b produce a slur be standard behavior c) a mode where a~b both produces a slur as well as a warning That is, I analyzed in what manner a~b producing slurs could be made an option in Lilypond without producing a total mess. That does not mean that I consider it a good idea. But I can tolerate bad ideas if they are switched off by default. As long as they don't clutter the code all too badly. In this case, I have the feeling that they might. But without any prospective code, I can't judge that aspect. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond