Thanks for the suggestion. I should have thought of trying this myself,
but a long time ago I put a 'cygwin' terminfo entry on the Linux host and
after a while trying to get it to work without success I just settled on using
TERM=linux. The current 'cygwin' entry is substantially different from t
On Mon, Feb 10, 2003 at 04:55:01AM -0600, Doug Wyatt wrote:
> Finally, the vim problem only occurs when the linux env var TERM=linux,
> but not when it is set to 'vt100'. Of course, there is lost functionality with
> vt100 - this is a useable workaround but really not an acceptable fix.
Try copyi
Hi,
Thank you for the quick feedback, Corinna! What follows is what I've done
so far to try to figure out what is causing my problem. I doubt, seriously,
that anyone is going to read this and solve the problem for me, but perhaps
one or more readers can suggest things to look at or tools that mi
On Sun, Feb 09, 2003 at 05:19:37AM -0600, Doug Wyatt wrote:
> Is it possible that 3.5p1-3 was built somehow differently than 3.5p1-2?
No. I'm using 3.5p1-3 with Linux w/o problems btw.
> What were the exact options used to configure and build each? I don't
> see any documentation of this in the
Hi,
I use ssh to connect to a Linux box and on the 6th I suddenly found that
vim (enhanced) on the linux host was no longer useable over the usual
ssh connection. Vim would load a text file, but almost any input produced
a series of beeps and streams of trash chars at the bottom of the screen.
Fo
5 matches
Mail list logo
