On 20/04/2012 20:13, Donn Cave wrote: > Another way to approach this might be to make sure Terminal handles > the mode switch sequence(s) (and it looks like it now does not, so > that would take some work.) > > To the extent that termcap is relevant at all, then you may specify > whichever flavor of cursor you prefer, and include the respective > mode switch in the termcap screen mode initialization. An application > that knows how to override that will get what it expects, and the > rest will get what termcap leads them to expect. > > Unfortunately, that won't help so much with remote applications, > since they're working from a different termcap. (E.g., the BBS > example that may have brought this up.) Well, as long as we declare a known TERM like xterm or xterm-color, we should follow whichever public temrinfo declaration it has instead of overriding it. Or put back beterm if you want to patch the thing. François.