They would be mutually exclusive, and both off by default, resulting in
> On Sun, Nov 14, 2010 at 12:38 PM, David Kastrup <address@hidden
>> Means a tie, as indicated by the user.
> Oh. So, setting tieWaitForNote would disable the "automatic-slurs"
a warning instead.
>> Means bad input. Configurable to be treated as a slur to b.
> Then it would no longer be "bad input", would it?
As long as it is not the default.
> My main concern is that such a change would amount to make the input
> syntax more "fault-tolerant", which isn't the direction we've been
> taking so far.
I'd rather just warn, unless a specific option is set. I don't think it
> That being said, unterminated ties are currently allowed and do not
> produce any warning, so I don't think the current situation is optimal
> either. If anything, we could at least output a "warning: unfinished
> tie. A slur will be printed instead".
> How does it seems to you?
makes much sense to both warn and typeset a slur.
I agree with Marc Hohl - converting wrognly defined ties into slurs should be done by converters.
However, the behaviour described above by David would be acceptable to me.