Date: Sat, 21 May 2005 18:07:23 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: alexander <arundel@h3c.de> Cc: freebsd-hackers@freebsd.org Subject: Re: Looking for ANSI/VT100 code replacement. Message-ID: <20050521080723.GN2129@cirb503493.alcatel.com.au> In-Reply-To: <20050521015105.GA9063@skatecity> References: <20050520224726.GA7951@skatecity> <20050520230845.GC51092@dan.emsphone.com> <20050521015105.GA9063@skatecity>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 2005-May-21 03:51:05 +0200, alexander wrote:
>Ohh...sorry for not telling you this. Yes. The app works alright when
>executed from the console. But my problem is with xterm or Eterm. They don't
>handle VT100 very well.
By default, xterm is a VT102 superset, and the VT102 is a VT100 superset.
Unless you are issuing unusual escape sequences, you shouldn't be able
to tell the difference.
> In fact Eterm or xterm might not update the value
>for as long as 5-8 seconds.
Out of interest, is the xterm or Eterm client running on the Xserver or
a different host? It is possible that updates are being queued between
xterm and the Xserver, though I think 5-8 seconds is excessive.
>The app is used to upload data to another device. Under the console the upload
>time is ~ 11.5 seconds. Under Eterm it is ~ 25 seconds. That's why I really
>want to get rid of the VT100 stuff.
xterm/Eterm have much more overhead than the console. If you're running
on really slow hardware, this might make a difference.
>The nanosleep delay I'm using is 0,00050000.
Note that the minimum delay is 1 tick (1/HZ). Shorter delays are rounded
up (and there might still be a one-tick additional delay).
> Plus the cursor jumps forth and back.
I would expect that. The cursor is moving back and forth as you write
to the xterm. Since the screen refresh rate is much slower than your
update rate, you are seeing the cursor in random locations. The easy
solution for xterm is to make the cursor invisible ("\e[?25l" and
"\e[?25h" to make it visible again).
I think you need to give us more details and preferably some sample code
to simulate the problem. What is the hardware you are running on? What
version of FreeBSD, X11 and xterm/Eterm.
--
Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050521080723.GN2129>