This may or may not be anything to do with the
earlier scrolling post.
The behavior of scrolling with vi has changed in
the last year or so; I changed to ssh2 from
plain telnet and installed a more recent
version (5.49, which did help the hot hang,
thanks!). The remote machine (Solaris) shouldn't
have changed anything during this time.
I used to be able to move down in a vi file and
then use the scroll bars to view the part that
had scrolled up off the screen. This was great,
so I could cut and past large sections of code.
Now, using the scroll bars puts me somewhere
useless in the file, I don't know where or why.
I'm having to cut and paste smaller sections
which is much more effort and error prone.
Also, previously when I exited vi, the part of
the file I'd been looking at stayed on the
screen, now it clears and I'm seeing the
previous history with just the line invoking vi.
Is this just ssh, is it something I can configure
to work like it used to, or could whatever you
were doing for scrolling in the lastest version
help?
thanks!
Lisa
[size=1][ May 07, 2008, 11:42 AM: Message edited by: Brian T. Pence ][/size]
Lisa,
The terminal only does what the host tells it to do, so it is unlikely that anything in Absolute has changed to cause this. It is also important to note that in a full-screen app such as VI, there is never any guarantee of what happens in the scrollback. VI doesn't actually have to 'scroll' the data to get it to *appear* to scroll. It could, for example, delete the top row and shift the rest of the data up by one row, etc... This would cause the screen to appear to scroll to you the user, but would not result in data going to the scrollback.
From your description, I would suspect that you're using a different terminal type than before. If you're using 'xterm', try switching to vt100. Make sure the environment variable on the command line says 'vt100'. You may have to disconnect and reconnect after setting the terminal type in Options->Properties->VTOptions.
Let me know if this helps.
Brian
