1855757 Members
5451 Online
104103 Solutions
New Discussion

Re: set -o vi

 
JFS_1
Advisor

set -o vi

Hi all,

where do i have to "set -o vi"
so that all the users and all types of terminals (xterm, dtterm...) are concerned ?

reason : i want all to be able to use "esc+k" to call previous commands.

thanx
6 REPLIES 6
Marco Santerre
Honored Contributor

Re: set -o vi

Why don't you put it in /etc/profile if you want it for everyone? Otherwise I'd put it in my own personal .profile
Cooperation is doing with a smile what you have to do anyhow.
T G Manikandan
Honored Contributor

Re: set -o vi

/etc/profile

JFS_1
Advisor

Re: set -o vi

i tried it, of course

but it doesn't work 100 %...

it works for the hpterminal, but not for the xterm and not for the dtterm i have positioned in my home session.
Jean-Louis Phelix
Honored Contributor

Re: set -o vi

Hi,

Depending on how you log in (CDE, ...), your .profile is sometimes not executed for child windows. You don't care for Env variables which are exported but you can loose some setting or aliases. That's why I set a ENV variable to $HOME/.kshrc in my .profile (or /etc/profile) and I put the "set -o vi" with my aliases in $HOME/.kshrc which will be executed by all child processes ...

Regards.
It works for me (© Bill McNAMARA ...)
John Bolene
Honored Contributor

Re: set -o vi

Your dtterm may not be calling the .profile, you need to set the last line in .dtprofile to DTSOURCEPROFILE=true

This line may be commented out.




I have no problems putting this in my personal .profile
It is always a good day when you are launching rockets! http://tripolioklahoma.org, Mostly Missiles http://mostlymissiles.com
T G Manikandan
Honored Contributor

Re: set -o vi

Also make sure that the variable

EDITOR is set to vi


EDITOR=vi

Revert