The real issue comes with the fact that successful connections are reported via unsolicited "_OWANCALL" messages like this:
(ttyHS2): <-- '_OWANCALL: 2, 1<CR><LF>'
These messages don't come prefixed with <CR><LF>, and therefore the new echo removal mechanism in MM 0.5.1.97 gets rid of those.
I will fix it to avoid using the echo removal in the Option & HSO plugins.
The real issue comes with the fact that successful connections are reported via unsolicited "_OWANCALL" messages like this:
(ttyHS2): <-- '_OWANCALL: 2, 1<CR><LF>'
These messages don't come prefixed with <CR><LF>, and therefore the new echo removal mechanism in MM 0.5.1.97 gets rid of those.
I will fix it to avoid using the echo removal in the Option & HSO plugins.