Thanks, I will have to fix that, probably by trapping any non-printing, non-whitespace code, not just [\n\r]. I can't think of any situation I would not want to

Thanks, I will have to fix that, probably by trapping any non-printing, non-whitespace code, not just [\n\r]. I can't think of any situation I would not want to confirm past of text containing control codes, so it should be an easy fix. Incidentally, while I wasn't vulnerable to C-o because I have a lot of remapped bindings. However, I am vulnerable to the two other codes that I bound to operate-and-get-next. > Enumerating badness usually doesn't end well. *applause* I wish more people that create and/or operate networked devices understood that.