Hi,

When I use console port to config my server, I have some troubles with Vim editor. For example, the screen wasn't clear when I opened file. It also keep the old characters of the command prompt (like: #bash 3,0 --: .........) and the main content of this file is not shown out :-(. I have to move the cursor to see each line (can you imagine how xxx it is). And another trouble that is I can't use the backspace to delete character before cursor while i'm being in edit mode, I must press ESC and use X to delete, hix

I don't have these troubles when I use RedHat on my PC. What should I do to avoid them?

Thanks.

"Welcome to Solaris"

We only use the console port long enough to get a network connection. Then we ssh in with vt100 emulation to get work done. Console port is not fun to use.

But vi works fine in the console, as long as you are using the right TERM environment variable, which seems to be the issue here.

That has not been my experience. TERM=vt100 + vt100 emulator results in the same as not doing any config

To Brian: thx for ur sharing. However, I can't use telnet or ssh now. I also have question how to active it. *NIX world is not easy...

To jlliagre: which TERM do I should to use?

Thx all.

The console is not vt100 compatible, so setting it to vt100 won't help.

"sun-color" if running on x86/x64 and "sun" for SPARC based H/W.
If by console you mean the CDE console window, then the correct setting is "dtterm".

I'm using VanDyke Software's CRT 4.1. It supports ANSI, Linux, SCO ANSI, VShell, VT100, VT102, VT220, WYSE50, WYSE60, and Xterm terminal emulation. There's no "sun" or "sun-color"

Okay, so you are complaining about issues when connecting to the Solaris box throuch the serial line ?

Of course in that case you have to set the TERM variable to what you emulator is faking.

If it doesn't works, you'd rather blame that emulator than Solaris, or find out what is going wrong in your process:
TERM not exported, escape sequences in the prompt messing the emulator, ...

Just get used to using vi blind
I usually cat the file out before editing and then use find in vi /or? to locate it and then replace it. Once I get done with the file I cat it out again to make sure it looks right.

As for the backspace in edit mode I think that's a vim feature and not supported with vi.

Like Brian said I use the serial connection long enough to get networking going then use a normal terminal.

Yeah, after I actived telnet and ssh, I don't use serial connection anymore. Vim works fine in telnet and ssh modes, but when I insert character (press "i"), it insert new character before the cussor. Can I make it insert after the cursor ?

You can erase the previous character with backspace when in edit mode under vi, provided these conditions are met:
- these characters were just added in the same insert session
- your emulator is really sending "backspace" when you hit the backspace key.

To check the latter, try erasing with [Ctrl-H] instead of [BackSpace], if only the first one works, blame you emulator, not vi.

"i" is inserting characters before the cursor as designed. If you want to 'insert after', also known as "append", use the "a" command instead of "i".

okay, it's clear. Thx so much.