OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: niv on June 26, 2005, 03:39:12 pm

Title: Bug: Vi Goes Wiled Via Ssh
Post by: niv on June 26, 2005, 03:39:12 pm

I must start by saying I don't like VI.
in order to add nano I had to edit it the ipkg.conf.

so I use vi :-(
moving to the buttom of the first screen, the text started going wield.

when I :wq lots of text i put was missing.

did any one used vi via ssh Like I did?
any chance to add nano as a standard editor?

Title: Bug: Vi Goes Wiled Via Ssh
Post by: Penguin Man on June 27, 2005, 10:48:02 am

I haven't had any problem using vi over ssh or on the machine itself.  I installed micro-emacs, but it took me forever to figure out what it was called (mec).

Title: Bug: Vi Goes Wiled Via Ssh
Post by: bluedevils on June 27, 2005, 11:03:56 am

you probably needed to set the terminal variable.

Code: [Select]

TERM=vt100
export TERM

Title: Bug: Vi Goes Wiled Via Ssh
Post by: niv on June 27, 2005, 11:59:29 am

10x blue.
aint there a .login I ca put this in, so it will run when ever I ssh to my zaurus?

Title: Bug: Vi Goes Wiled Via Ssh
Post by: bluedevils on June 27, 2005, 01:17:36 pm

Generally if you are using bash you can put it in .bashrc

Title: Bug: Vi Goes Wiled Via Ssh
Post by: Penguin Man on June 28, 2005, 12:45:55 pm

Quote

Generally if you are using bash you can put it in .bashrc
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86063\"][{POST_SNAPBACK}][/a][/div]

Or .profile for regular sh.

Title: Bug: Vi Goes Wiled Via Ssh
Post by: niv on June 30, 2005, 09:15:30 pm

I did that, still vi behaves bad if I move too fast , of beyond end of line.

I am ssh ing from a pc to the 5500, tring to fix the .bashrc , so ldconfig and the rest of the programs I am tring to install will work...

I mean setting u the path.

Title: Bug: Vi Goes Wiled Via Ssh
Post by: bluedevils on July 01, 2005, 09:36:03 am

and you typed

Code: [Select]

env|grep TERM to see if the TERM variable is correct?