I was working on some sysadmin tasks on a freshly installed server, and I found out the crontab editor was not what I expected it to be. I really like vi (or vim) for command line editing, so I wanted ‘crontab -e’ to use vim instead of something else. To make that happen, I put this into my roots .bashrc file (location: ~/.bashrc):
or from the command line
If using CentOS7 – System Default Editor
During login, a number of scripts are run to setup the environment. In CentOS, a file for each subject is used. These are stored in a system profile directory, /etc/profile.d/. There are two environment variables that control which editor to use.
Per User Default
If a user wishes to set the default editor for themselves, it can be, instead, be done in the user’s bash profile.
Some of the changes made won’t take effect on the current session. Log out and back in to activate the changes.
Scheduling jobs is one multi-layer process that uses a text editor. Editing the current user’s scheduled jobs is one way to test which editor is the default.
If it is still nano, use ctrl+x to exit. If you are using vim, congratulations! Use “:q” to exit.
I keep forgetting this, so I decided to blog it. Don’t forget to reload the bashrc by doing this:
If you are in the same situation and want to change the editor to nano, here is the simple command that will change your default OS editor.
export VISUAL=’pico -w’
Now when you run:
Nano will open up. Don’t forget to logout and log back in to see the changes.