Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!wciu!wvus!pete From: pete@wvus.wciu.edu (Pete Gregory) Newsgroups: comp.terminals Subject: nulls Message-ID: Date: 29 Dec 90 01:19:00 GMT Organization: World Vision U.S. Lines: 31 Hi - I'm trying to write a terminfo (and termcap) for the rlogingl program that's a part of PC/TCP. I wrote a small C program that captures what characters arrive when I press arrow keys, etc., and put those entries in terminfo. (I am quite familiar with how to modify and 'compile' terminfo files - I don't think that's my problem) Trouble is, this emulator sends two bytes for cursor and function keys, and the *first* byte is a *null*. In my terminfo entry for up-arrow (for example), I've tried: kcuu1=\0\110, kcuu1=\200\110, kcuu1=\000\110, ...and none work (I use 'vi' to test this easy stuff :-). Question: is there something inherent about leading nulls on multi-byte character sequences that I need to do something special for? Thanks... (please send me E-mail - and feel free to post - 'cause I don't often read this subject) Pete Gregory, UNIX SA | pete@wvus.wciu.edu | World Vision USA/ISD | wciu!wvus!pete ___|___ 919 W. Huntingon Dr. | Voice: 818/357-7979 x3347 | Monrovia, CA 91016 | FAX: 818/303-6212 | | Romanian orphans need our help! Call 1-800-777-1229