Re: [tlug] vi weird when I ssh to one machine

[Darren Cook <darren@example.com>]

Thanks for the replies.

>  > I would verify the contents of the TERM variable on working and non-
>  > working terminals:
>  >   echo $TERM

Hhmm, seems we are into the more exotic causes then, as I'm comparing
ssh sessions on two machines, and both are:

TERM=xterm-256color
SHELL=/bin/bash

The client machine also has exactly the same.

Scott wrote:
> I first set it as TERM=vt100, otherwise I get various error messages,...

Ooh, this works. In my existing ssh session, I did `export TERM=vt100`
then I can now `vi test` with no control codes appearing when I press "i".

BTW, `vi` is the only thing I've seen having a problem. E.g. `ls` shows
coloured file listings (with either TERM setting).

I had a bit of a poke around, to see if I could find something that is
different between working and problem server.

/etc/vim/vimrc is identical on both machines.

/etc/ssh/sshd_config looks identical

Comparing printenv, LANG is LANG=en_GB.UTF-8 vs LANG=en_US.UTF-8. The
XDG_ variables are a bit different. LS_COLORS is very slightly different

On the working server
  SHLVL=1

On the problem server:
  SHLVL=0

...ah, perhaps as I'd exited conda. In a new session (conda is on by
default) SHLVL is 1. The VT100 trick still works with/without conda.
(And I'd already confirmed vi behaviour was the same with/without conda.)

Darren