On Sunday, August 25, 2002, at 03:54 PM, Ben Reser wrote: > >> I don't know... I think having it default to xterm might be a good >> idea... despite the fact that there is now an Eterm entry in termcap >> and the Eterm terminfo files are installed, we may still have some >> compatibility issues, like this one. > > Yup
I'm sure that there are more than just this one... > >> This is, of course, just for defaults. I, personally, copy the >> standard mutt themes into my homedir and modify to suite my personal >> tastes, and I suspect most power users who feel they may benefit from >> TERM=Eterm (actually, what *are* the benefits, if any?) would do the >> same. > > I do the same thing. And I have no idea what the advantages are. I've > tried it both ways and can't see any discernable difference... Except > the bizare escape issue and dealing with machines without the > termcap/terminfo. Nope, same here. I can't see anything that would make me think that having TERM=Eterm offers any distinct advantages... I could be wrong, of course. But I suspect those cases would either be for Eterm-supplied tools or perhaps Enlightenment needing/setting certain things. Either way, I think it safe enough to force a TERM=xterm for "backwards compatibility". On an unrelated note... Is my message being properly wrapped or is the above one long line? I can't tell. -- MandrakeSoft Security; http://www.mandrakesecure.net/ "lynx -source http://www.freezer-burn.org/bios/vdanen.gpg | gpg --import" {FE6F2AFD/88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
