All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
vi and TERM
|
Logged in as: Guest |
Users viewing this topic: none |
|
Login |
|
|
vi and TERM - Jan. 16, '04, 3:55:53 PM
|
|
|
Pericles
Posts: 7
Joined: Jan. 15, '04,
Status: offline
|
Currently, when i try to edit anything in vi under SFU the screen buffer goes nuts. I' ve tried setting TERM to any number of combinations, no luck. Is there a version from interopsystems forthcoming that will address this?
|
|
|
RE: vi and TERM - Jan. 16, '04, 4:41:55 PM
|
|
|
Rodney
Posts: 2916
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
Your TERM environment variable should be set to " interix" .
Vi has been working with this setting for about 5 or 6 years now.
When you start a fresh shell (i.e. from the Start menu) what is TERM set to?
|
|
|
RE: vi and TERM - Jan. 16, '04, 4:54:50 PM
|
|
|
markfunk
Posts: 622
Joined: Mar. 31, '03,
Status: offline
|
What is the context in which you start ' vi' ?
Are you in an Interix ksh window ? Are you in a cmd.exe window ? Are you in a telnet session ?
|
|
|
RE: vi and TERM - Jan. 16, '04, 5:26:47 PM
|
|
|
Pericles
Posts: 7
Joined: Jan. 15, '04,
Status: offline
|
it was set to " dumb" by default, i tried cygwin (i know, i know), ansi, and vt100. this is in a shell started with this command:
C:\WINNT\system32\POSIX.EXE /u /c /bin/bash -l
Anyway, setting TERM=interix seems to have cured what ailed me. Thanks a lot.
|
|
|
RE: vi and TERM - Jan. 20, '04, 9:10:49 AM
|
|
|
Carsti
Posts: 2
Joined: Jan. 20, '04,
Status: offline
|
Partially that worked for me too. But when I start the bash via posix.exe my .bashrc isn' t executed. Only if I run the bash from commandline, it gets executed and then TERM is set correctly.
Where did you put in that line? Is there something like /etc/csh.cshrc for bash, too? Darn, my Linux knowledge is rusting for 5 years or so now...
TIA, Carsti
|
|
|
RE: vi and TERM - Jan. 20, '04, 11:53:15 AM
|
|
|
Pericles
Posts: 7
Joined: Jan. 15, '04,
Status: offline
|
I just put it in the command line for the shortcut.
|
|
|
RE: vi and TERM - Jan. 20, '04, 11:53:51 AM
|
|
|
Pericles
Posts: 7
Joined: Jan. 15, '04,
Status: offline
|
Oh, you mean the TERM definition? in my .bash_profile script
|
|
|
RE: vi and TERM - Jan. 25, '04, 7:36:17 PM
|
|
|
markfunk
Posts: 622
Joined: Mar. 31, '03,
Status: offline
|
When you start up " bash -l" , either directly or from a short cut icon, it will read /etc/profile.
/etc/profile will set TERM to " interix" if TERM is not yet defined. If it is defined, that means you (or some other software) has set TERM in your global system environment.
This is most likely the source of your problem.
If so, the simple fix is to add
export TERM=interix
explicitly in your /etc/profile.lcl file.
This way, whenever you enter the interix environment via a login shell (like " bash -l" or " csh -l" or ...) you will get TERM setup properly.
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
|
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|