move vim-tiny to / filesystem?
Bug #372364 reported by
Simon Oosthoek
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vim (Debian) |
Fix Released
|
Unknown
|
|||
vim (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I've noticed a few times now that nano is the default editor in Ubuntu, which I can to a certain extent understand because of the learning curve of the vi editor. However, I do believe the vi editor is specified in the posix standard as part of the Unix command set.
As a Linux/Unix educator, I tell my students that vi is the one editor that they can depend on to be available on all Unix systems. Unfortunately, ubuntu is no longer a Unix system by _this_ definition :-(
Please include a statically compiled vi-clone in the base-install in /bin/vi to fix this problem!
thank you!
/Simon
Changed in vim (Debian): | |
status: | Unknown → New |
Changed in vim (Debian): | |
status: | New → Confirmed |
Changed in vim (Debian): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
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