Re: Problem using vim in csh on linux

On 2015-10-21 05:20, Lowell Specht wrote:
> What version of vim?
> VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Mar 31 2015 11:14:07)
> Included patches: 1-207, 209-629
> Huge version without GUI. Features included (+) or not (-):

Okay, not running some archaic version, nor a stripped-down "tiny"
version.

> csh: TERM=xterm
> ksh: TERM=xterm

Okay, the same. Good.

> How do I establish my terminal session?
> terminal is Windows client app hummingbird exceed common desktop
> environment to logon to a HP unix server. From there, I ssh -Y to
> the linux server.

I'm not sure if there's something funky going on here. Can you SSH
directly to the linux server rather than through the HP server?

> Does CTRL Shift L work? No.

The "shift" is unobserved by vim in this case (so ctrl+shift+L ==
ctrl+L), but control+ell should force a clear+repaint of vim. If that
doesn't resolve matters, I'm now curious whether the artifacts are
full characters, in which case Vim may think that they belong there,
so it repaints them, or they're rendering corruption on your Exceed
terminal end (these could be full-characters or they could be partial
lines/swaths of color that simply don't get properly
cleared/overwritten/moved/updated). My money would be on Exceed
munging things as I remember less-than-quality experiences with it
the last time I used it (which, granted, was back in the late 90s).

> Minimal sequence of steps to demonstrate the problem:
> 1. windows client, launch hummingbird exceed CDE, login to unix
> server with default csh, launch an xterm, ssh -Y <linux server> in
> an xterm 2. vim an ascii file large enough that you can page back
> and forth. 3. ctrl-f and ctrl-b a few times and watch the text
> become garbled as the window does not fully refresh. Note that
> using j and k to scroll one line at time works fine (I just
> discovered this).

[wrote this before reading your closing paragraph. Whoops]
Do you have access to a terminal SSH program on your Windows PC?
Maybe via Cygwin or PuTTY? Or boot a live Linux/BSD CD, connect to
your HP box, then SSH to the Linux box? It would help to know what
happens if you can cut Exceed out of the picture (or possibly cut the
HP box out too).

> Do I notice it more with different file types?
> No. Problem appears while editing a makefile, a fortran source file
> and my .cshrc. I haven't spent a lot of time exploring this with
> other files.

Okay, the only really interesting answers would be "it happens with
this particular file-type, or family-of-file-types". Since it seems
to happen across the board, likely a blind alley.

> Same path in both shells?
> yes. which vim returns /usr/bin/vim in both shells. which vi
> indicates it is aliased to vim.

Drat. That was my front-runner idea before you so thoroughly shot it
down :-)

> Try, vim -N -u NONE.
> I did. Same problem.

Okay, this strongly suggests that it's not Vim, but that something
between vim and you is getting garbled.

> What is the output from :set termcap?
> I am not familiar with this command. I tried it in both shells and
> got :set not found. So I tried it without the colon and got no
> error and no output. Just a return to the prompt.

The ":" prefix was a hint that it should be run within vim. It can
be a little messy, so you might want to

:redir > termcap_output_from_vim.txt
:set termcap
:redir END

which should have vim capture the output and send it to
"termcap_output_from_vim.txt" that you can attach or manipulate a bit
more easily.

> After typing this up, I tried Windows Client, putty terminal, ssh
> -Y to linux server and now vim works in csh. So it is looking like
> a problem with the hummingbird exceed CDE.

Heh, would help if I read all the way to the end of your message
before beginning a reply. At least this corroborates my suspicions. I
don't know if your test included SSHing to the HP box and then SSHing
from there to the Linux box, just to exculpate the HP box.

But now you have some evidence you can take to Exceed folks to get
use out of your support-dollars. :-)

-tim






--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.