Thursday, June 30, 2011

Re: vim & Solaris

Gary Johnson <garyjohn@spocom.com> [11-06-30 17:27]:
> On 2011-06-30, meino.cramer@gmx.de wrote:
> > Hi,
> >
> > at work there is Solaris machine with an oler vim installed. I am
> > neither sysadmin nor can I acchieve root privileges.
>
> I used a Solaris system for years without root privileges and was
> still able to install everything I needed in my ~/bin, ~/man, etc.
> directories.
>
> > When starting vim (terminal) and trying to type anything else than
> > printable characters, these characters are inserted as
> > control-sequence but they are not "executed" (read: Cursor arrow down
> > does not move the cursor down but inserts its control sequence).
> >
> > >echo $TERM
> > at the console says "xterm". CDE is used (motif).
>
> It appears that the terminfo entry for xterm does not match the
> behavior of the terminal you're using. What are you really using?
>
> It may also be that the terminfo database on your Solaris system is
> poorly maintained and doesn't have the correct or complete
> description of an xterm.
>
> There are several possible solutions to this.
>
> First, make sure that the value of $TERM matches the terminal you're
> using.
>
> Next, check that the terminfo database exists and is correct for
> that terminal. You can execute the "infocmp" command to see the
> terminfo description of your terminal. You can also execute Vim's
> ":set termcap" command to see Vim's idea of your terminal's
> capabilities. These usually come from the terminfo database but Vim
> sometimes fills in some values from it's built-in terminal
> information.
>
> If the terminfo database information is wrong for your terminal, you
> can look in the database for a terminal description that more
> closely matches your terminal. Then you can just set TERM to that
> name. Alternatively, you can build your own terminfo database from
> publicly-available sources or your own description, but that may be
> more than you want to tackle for now.
>
> > Is there any chance to tweak, so that such things work without
> > remapping each charcter, which does not work, to a command sequence?
> > Thank you very much for any help in advance!
>
> I don't understand what does not work.
>
> One way to create your own mappings for the arrow keys, for example,
> is to put in your ~/.vimrc at set of lines like these,
>
> map OD <Left>
> map OC <Right>
> map OA <Up>
> map OB <Down>
>
> where for each of those I typed "map ", then Ctrl-V, then hit the
> actual arrow key to be mapped, then a space and Vim's name for that
> key.
>
> Instead of mapping each key, you could set Vim's termcap name for
> each key like this:
>
> set t_kl= OD
> set t_kr= OC
> set t_ku= OA
> set t_kd= OB
>
> where again I inserted the key's character sequence by typing Ctrl-V
> then hitting the arrow key.
>
> Those are just some ideas since I don't know exactly what the
> problem is nor what constraints your under.
>
> HTH,
> Gary
>
> --
> 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
>


Hi Gary,

thank you for your help! :)

I am simply not allowed to install anything regardless
of the prevelidges I have or better: not have...
Thats the reason, why the vim is that old.

I will try what you have written. If I will get further
or different problems, I will contact this friendly
list :) again...

w!

Best regards and have a nice weekend!
mcc

--
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

No comments: