It might be handy to make a difference between $EDITOR and $VISUAL as they have different purposes (which are often ignored - but still there): $EDITOR is for when you can't have a $VISUAL (and even less so, a GUI one).
I made a little experiment this morning, exchanging $EDITOR for $VISUAL and it works as expected.
I guess the recommendation should be to use $VISUAL for you GUI enabled editor and then define $EDITOR point to a non-gui like vi, nano, vim or similar for hosts where you access via ssh.
Which makes your shell configuration portable, which holds a lot of benefits.
Thanks for the pointer. I do however wonder where this is documented, would love to know a know authoritative resource. I will update my TIL accordingly.
Parts of the definition come from POSIX. Even in 2018 when most operating systems skip large parts of POSIX, it could be useful to stick to its recommendations.
It might be handy to make a difference between
$EDITORand$VISUALas they have different purposes (which are often ignored - but still there):$EDITORis for when you can't have a$VISUAL(and even less so, a GUI one).I made a little experiment this morning, exchanging
$EDITORfor$VISUALand it works as expected.I guess the recommendation should be to use
$VISUALfor you GUI enabled editor and then define$EDITORpoint to a non-gui likevi,nano,vimor similar for hosts where you access viassh.Which makes your shell configuration portable, which holds a lot of benefits.
So I ended up with the following:
Thanks for the pointer. I do however wonder where this is documented, would love to know a know authoritative resource. I will update my TIL accordingly.
Parts of the definition come from POSIX. Even in 2018 when most operating systems skip large parts of POSIX, it could be useful to stick to its recommendations.
Glad to help.
I find your recommendation much more correct, the more I think about it - thanks again.
My
.bash_profilehas followed me for many years, glad to learn that I can still improve it.