It was pointed out to me that a /usr/bin/vi is always available, so posix compliance may not be at issue in that respect.
However, my point was that /bin/vi is not available in a default install and this _is_ a problem if you have a separate /usr partition that has problems being mounted for some reason, there's only nano as a visual editor in /bin/. In emergencies this would be mostly annoying to someone used to using vi, not impossible to overcome (nano can edit files).
I've noticed the problem since about 8.04 LTS, especially when using a command like visudo, which normally uses vi, but somehow decides to use /bin/nano. The problem is not that by default the EDITOR variable is set for all users to /bin/nano.
I hope this clarifies my earlier report somewhat...
It was pointed out to me that a /usr/bin/vi is always available, so posix compliance may not be at issue in that respect.
However, my point was that /bin/vi is not available in a default install and this _is_ a problem if you have a separate /usr partition that has problems being mounted for some reason, there's only nano as a visual editor in /bin/. In emergencies this would be mostly annoying to someone used to using vi, not impossible to overcome (nano can edit files).
I've noticed the problem since about 8.04 LTS, especially when using a command like visudo, which normally uses vi, but somehow decides to use /bin/nano. The problem is not that by default the EDITOR variable is set for all users to /bin/nano.
I hope this clarifies my earlier report somewhat...
/Simon