Saluton viktiglemma :) On Tue 5 May 2009 11:58 +0200, viktiglemma <[email protected]> dixit: > Why doesn't Vim leave vi behind? As a new user I do not benefit from > all the vi-information.
Myself, I don't even see the point of Vim being able to behave "compatibly" with old vi, but I know that Bram has his reasons and as the author, he has the right of doing things that way. While for me ":set nocp" is basic, for many other users it may be wrong not being able to ":set cp". > The only two reasons I see why vi should continually be > referenced are > 1) there are still a large number of people using vi and who will be very > confused if they are ever forced to work in Vim > 2) sentimentality and appreciation for vi as the mother editor 3) vi is a POSIX standard command, and if I remember correctly, you can even read how it should behave and be used in Single Unix Specification v3. Being as compatible as possible with POSIX vi may be of help if you have to use Vim on some machines, other vi flavors in other machines, who knows. 4) It would probably take more time getting rid of POSIX-vi information from help files than maintain it. 5) There is a large number of people using POSIX vi or any other POSIX-vi compatible vi implementation that may want to switch to Vim, and being able to behave in a compatible way with POSIX vi makes such transitions less painful. 6) Many people may have switched to Vim after years of having use POSIX vi and may wonder why Vim doesn't do certain things like POSIX vi. The help files give them the information. 7) Any other set of reasons Bram may have. ;) -- Raúl "DervishD" Núñez de Arenas Coronado Linux Registered User 88736 | http://www.dervishd.net It's my PC and I'll cry if I want to... RAmen! --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
