Vim displays OOPS instead of placement/color commands?

As can be seen here: code.google.com/p/vim/source/browse/src/... code.google.com/p/vim/source/browse/src/... The tgoto function (purpose: decode cm cursor motion string) can fail and return OOPS. The most likely reason is unsupported TERM environment variable. To get a list of builtin terminal types recognized, try TERM=bogus vim +q It will show a list, and you can pick the one most closely resembling your OS/terminal (emulator) PS.

Consider filing a bug on the vim-dev list if you think this behaviour affects standard Solaris installations.

I'm Windows using Putty. The TERM is set to xterm. However, I did as you asked and saw the list of available TERM's.

I used one of them, but the behavior didn't change. I matched the TERM environment variable to the users that did work and there is no difference. – fidesachates Jun 24 at 22:12 I'd inquire on the list and/or file the bug; chances are that your solaris is using nondefault terminal codes unknown to vim.

There is a chance that the devs know precisely what to add. I don't remember having this with my OpenSolaris box (nv147) – sehe Jun 24 at 23:52 Just noticed you fixed it. I bet it was libtermcap or something, but I won't complain if you don't want to find out :) – sehe Jun 24 at 23:58.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.