This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!


Posted by: Anonymous Coward on May 16, 2007 11:00 PM
I'm always amused by people who try to convert ViM into another KWrite/Gedit/Notepad.

Why to butcher ViM? Why not to use originals? - and leave ViM for people who really are using it for its unique features - not Notepad copycats?

I'm bothered by all the stuff, because not on single distro I heard horror stories of VIM being totally unusable. With little research, it usually turning out that packagers have screwed configs for VIM to behave more like Notepad. Or like Emacs. And that's just silly.

If normally one starts by customizing his/her favorite editor. Now people start by de-customizing editors (disabling all the stuff) just to find where the editor itself - and where the all stupid bells'n'whistles are. Because otherwise customization would screw things to worse - since it would conflict with all the funny stuff editor was forced to swallow by packagers.

<nobr> <wbr></nobr>... Ctrl-C to copy text or Alt-F to open the File menu<nobr> <wbr></nobr>...

Guys, if you are using Ctrl-C or menu, than you are most likely not a target audience of VIM.

VIM has stream-lined textual interface which allows one to never ever let his hands off keyboard - nor to change their position. (The abomination to text processing called "Mouse" is totally optional.) VIM is still one of the few (actually single I know) editors suitable for touch typists.

Not everybody is touch typist. But the general accessibility model of serial command like interface (fully accessible from keyboard) is precisely why VIM is so popular with its users.

VIM isn't Notepad - where people are for editor. VIM is "editor for people" which does precisely what I say it to do - not more but not less.

<nobr> <wbr></nobr>... File Tree<nobr> <wbr></nobr>...

Ever tried<nobr> <wbr></nobr>:E? Not the same, but works without "plug-ins"/"add-ons".

On the other hand, if you use gVim infrequently or want to take advantage of the power of Vim without learning the editor's commands, then Cream is definitely worth a look.

IOW trying to learn to swim without leaving coast? Don't be silly.

I have recommended and helped with VIM to many people. And learning is only problem. But unless one would start learning VIM commands - using ViM is pretty much pointless. Since otherwise ViM really is a weird equivalent of Notepad.

You wanna learn VIM - then learn it. Internet is filled with tutorials (which compared to emacs tutorial are actually readable and useful) e.g. <a href="" title="">VIM Cookbook by Steve Oualline</a> or <a href="" title="">even dumb web search</a>.


Return to Adding a little Cream to (g)Vim