The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(Score: 0) by Anonymous Coward on Tuesday September 13 2016, @12:48AM
by Anonymous Coward
on Tuesday September 13 2016, @12:48AM (#401034)
I don't use vi because it's not my cup of tea. So I use a different editor and you can too. If you don't like vi then don't hate on it just use what you prefer.
Otherwise, I would agree with you. When I want to alter a crontab I'm forced to use vi. That's not choice, but being dictated to by the vi crowd that at some level you must know vi to use Linux. I do refuse to learn anything beyond x:x as it's not required to learn something that fucking difficult to use in the first place. Yes, the mountain exists; Do I have time to climb it in addition to the others? Fuck no. I got to get shit done. Perl is enough of a mountain for me thank you, and I'm devoting my energies to climbing it, not energies involved in how to use the editor to start to climb the other mountains. Fuck, vi is supposed to be a tool, but it's just a hassle.
If there were choice involved, I could install low level replacements for all vi everywhere. Meaning that crontab now works with nano under the hood instead of vi.
Seriously. vi just slows you the fuck down. I'm not a 14 year old South Korean girl that can type 4000 symbols per second on a tiny clamshell phone, assuming I could remember them all in the first place. I don't like being forced to use it, and as long as I'm forced to use it, I'm going to complain loudly about how stupid vi is :D
-- Technically, lunchtime is at any moment.
It's just a wave function.
(Score: 1, Informative) by Anonymous Coward on Tuesday September 13 2016, @02:15AM
by Anonymous Coward
on Tuesday September 13 2016, @02:15AM (#401071)
apt-get install joe apt-get --purge vim export EDITOR=/usr/bin/joe export VISUAL=/usr/bin/joe
Then do "joe ~/.bashrc" to add those last 2 lines to your start-up file. You can put it in /etc/bash.bashrc as well, and anywhere else suitable. These take effect when shells start up, so restart things or just set the variables in each shell.
Don't those utilities respect the EDITOR environment variable? I've been using it to force vim all over the place for years. Does it not work to set EDITOR=nano?
-- ⓋⒶ☮✝🕊 Secession is the right of all sentient beings
Like the AC and jdavidb said: if you don't like vi, set your damn $EDITOR and $VISUAL environment variable already. It's why they exist. Once they're set, things like git commit, crontab -e, etc. will read them and run the desired editor instead of vi. I usually have mine set to a small script that runs emacs -nw so I can get an emacs frame in the terminal I'm working on, or sometimes something like mg, jed, or joe.
There you go, no need to complain about vi any more.
I forgot to also note that this isn't exactly obscure, arcane *nix knowledge or anything. From crontab's manpage:
The -e option is used to edit the current crontab using the editor specified by the VIS‐ UAL or EDITOR environment variables. After you exit from the editor, the modified crontab will be installed automatically. If neither of the environment variables is defined, then the default editor /usr/bin/editor is used.
So, you've been annoyed by this problem long enough to rant about it online and talk about how big an issue it is, but apparently never even tried to look for a solution.
(Score: 0) by Anonymous Coward on Tuesday September 13 2016, @12:48AM
I don't use vi because it's not my cup of tea. So I use a different editor and you can too. If you don't like vi then don't hate on it just use what you prefer.
Choice - if you have one make one.
(Score: 2, Disagree) by edIII on Tuesday September 13 2016, @01:43AM
I DON'T HAVE A FUCKING CHOICE! :P
Otherwise, I would agree with you. When I want to alter a crontab I'm forced to use vi. That's not choice, but being dictated to by the vi crowd that at some level you must know vi to use Linux. I do refuse to learn anything beyond x:x as it's not required to learn something that fucking difficult to use in the first place. Yes, the mountain exists; Do I have time to climb it in addition to the others? Fuck no. I got to get shit done. Perl is enough of a mountain for me thank you, and I'm devoting my energies to climbing it, not energies involved in how to use the editor to start to climb the other mountains. Fuck, vi is supposed to be a tool, but it's just a hassle.
If there were choice involved, I could install low level replacements for all vi everywhere. Meaning that crontab now works with nano under the hood instead of vi.
Seriously. vi just slows you the fuck down. I'm not a 14 year old South Korean girl that can type 4000 symbols per second on a tiny clamshell phone, assuming I could remember them all in the first place. I don't like being forced to use it, and as long as I'm forced to use it, I'm going to complain loudly about how stupid vi is :D
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 1, Informative) by Anonymous Coward on Tuesday September 13 2016, @02:15AM
apt-get install joe
apt-get --purge vim
export EDITOR=/usr/bin/joe
export VISUAL=/usr/bin/joe
Then do "joe ~/.bashrc" to add those last 2 lines to your start-up file. You can put it in /etc/bash.bashrc as well, and anywhere else suitable. These take effect when shells start up, so restart things or just set the variables in each shell.
(Score: 2) by jdavidb on Tuesday September 13 2016, @02:26AM
ⓋⒶ☮✝🕊 Secession is the right of all sentient beings
(Score: 3, Informative) by Marand on Tuesday September 13 2016, @03:04AM
Like the AC and jdavidb said: if you don't like vi, set your damn $EDITOR and $VISUAL environment variable already. It's why they exist. Once they're set, things like git commit, crontab -e, etc. will read them and run the desired editor instead of vi. I usually have mine set to a small script that runs emacs -nw so I can get an emacs frame in the terminal I'm working on, or sometimes something like mg, jed, or joe.
There you go, no need to complain about vi any more.
(Score: 4, Insightful) by Marand on Tuesday September 13 2016, @03:10AM
I forgot to also note that this isn't exactly obscure, arcane *nix knowledge or anything. From crontab's manpage:
The -e option is used to edit the current crontab using the editor specified by the VIS‐
UAL or EDITOR environment variables. After you exit from the editor, the modified
crontab will be installed automatically. If neither of the environment variables is
defined, then the default editor /usr/bin/editor is used.
So, you've been annoyed by this problem long enough to rant about it online and talk about how big an issue it is, but apparently never even tried to look for a solution.
(Score: 0) by Anonymous Coward on Tuesday September 13 2016, @03:59AM
ლ) Turn in your geek card.