Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!texbell!sugar!ficc!peter From: peter@ficc.uu.net (Peter da Silva) Newsgroups: comp.unix.questions Subject: Re: Termcap/Terminfo questions. (He'p me please!) Keywords: time delays, cursor addressing, 132 columns etc. Message-ID: <7344@ficc.uu.net> Date: 18 Dec 89 20:23:15 GMT References: <630@cogent.UUCP> Reply-To: peter@ficc.uu.net (Peter da Silva) Organization: Xenix Support, FICC Lines: 36 In article <630@cogent.UUCP> doug@cogent.UUCP (Doug Perlich) writes: > I do not want to use > curses or termcap functions. Why not? Termlib can support... > do an initialization routine > at user start up that will load all the needed information into the > users shared memory segment since the information will be needed > by several processes, (everything running under a menu system). Now terminfo is a different matter. Get a PD copy of termcap and hack on it. It's easy enough. > #1 What about time delays? If the first character of a string is a digit, it's preceded by a per-unit time delay. I.e., dc=4\E[P, means delay for 4 ms for each character deleted. > #2 I don't want to call termcap's tgoto() routine for cursor addressing Why not? > #3 I also want to know about switching from 80 to 132 column and back. > I don't see that information anywhere. It's not standard. For termcap, you could just add a new capability. For terminfo you're out of luck. Personally, I think terminfo sucks. -- `-_-' Peter da Silva. +1 713 274 5180. . 'U` Also or . "It was just dumb luck that Unix managed to break through the Stupidity Barrier and become popular in spite of its inherent elegance." -- gavin@krypton.sgi.com