Re: Small buglet in tset/termcap
Jonathan Hogg <[email protected]>
| Newsgroups | gmane.comp.sysutils.ark.devel |
|---|---|
| Message-ID | <[email protected]> |
On 17/4/01 18:26, Matt Holgate wrote: >Any ideas what the correct fix is? Should we modify the termcap, or >post-process tset's output to quote the TERM variable... The 'setenv TERM CDE terminal emulator' line looks pretty broken to me. I don't think post-processing it is a good idea. The TERM variable should be 'dtterm'. I'd guess at it being a bug in the termcap file or tset itself. In general though I'm confused as to why you're using tset to set the TERM (or TERMCAP) variable(s). This seems a pretty archaic ritual. Unless you're logging in via some kind of hardwired BSD console, the TERM variable should be getting set by the terminal itself and tset will use this to initialise the terminal. I'm not sure why you'd want to reset the TERM variable, nor why you'd want to explicitly set TERMCAP - since any termcap-aware program should use the TERM variable to look up whatever it needs in the termcap database. In short, why aren't you just doing 'tset -Q'? However, I am completely ignorant of the sidai user initialisation procedures so I apologise if I'm missing the point. :-j -- jonathan hogg, one good idea ltd, 131 queen margaret dr., glasgow g20 8pd http://www.onegoodidea.com/ tel:+44-(0)7976-614338 fax:+44-(0)7970-537451