On 2009-09-17, Jason wrote:
> Hey Everyone,
> 
> I just got a job working with unix on a daily basis. I have a script
> that I call that will launch a terminal for me. In this case it
> launches rxvt. I use the script to ssh into a box and by calling the
> script it opens up the ssh in a new window for me. The problem I am
> running into is on certain Solaris servers when I go to vi a file I
> get this.
> I don't know what kind of terminal you are on - all I have is 'rxvt'.
> >From vi and all I get to see is just one line of the file.
> I have googled this line and came across a site that says to specify
> the terminal type but it did not have anything for rxvt. Thank you in
> advance for your assistance with this.

Note that Solaris's vi is not vim, so that solutions that will work
with vim may not work with that vi.

The problem is that the terminfo and/or termcap databases on those
Solaris machines don't have an entry for 'rxvt', so vi doesn't know
how to control your terminal.  The best solution would be to update
those databases with info on rxvt.

If you can't do that, then I think the next-best solution would be
to lie to those servers and tell them you're using something else
that they do know about and that is close to an rxvt.  "man rxvt"
says it's a VT102 emulator, so you could execute

    export TERM=vt102

which the terminfo database on the Solaris system here does have.
The man page also says that the rxvt options are mostly a subset of
xterm's, so executing

    export TERM=xterm

might work as well.

You could execute either of those commands from the command line on
the Solaris servers or put it in your ~/.profile on those machines.

It might also work to instead put these in your ~/.exrc on those
machines,

    set term=vt102
    set ttytype=vt102

but I haven't tried that approach.

HTH,
Gary



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to