From: Ethan M. <merritt@u.washington.edu> - 2004-08-21 17:30:06
|
On Saturday 21 August 2004 01:23 am, you wrote: > > term->option() does not actually *do* > > anything; it just loads some fields in the terminal data structures. > > Which term->option() in particular are you speaking of? There are > dozens of them, each a bit different. I looked at all of them, and saw a potential problem only in svg.trm. But I freely admit that it's possible I missed something; that's why I asked if you had a particular terminal type or bit of code in mind as a problem area. All the critical (order-dependent) code seems to be in term->init(), rather than term->options(). If this wasn't intentional, then it's a lucky coincidence. Either way, calling term->options looks safe to me. Furthermore, I have modified the code in set_termoptions() to call only those terminal drivers that actually support the option in question ('set term font ..' or 'set term {no}enhanced'). So the term->options() of most drivers will not be called even if you do issue a 'set termoption' command. Nevertheless, if there is indeed a fundamental problem with this approach I can back off to some other mechanism that is specific to enabling enhanced text mode. -- Ethan A Merritt |