2010/11/12 Tony Mechelynck <[email protected]>

On 12/11/10 21:14, egarrulo wrote:
>
>> Hello,
>>
>> is there *complete* reference of Vim commands already available?  I
>> mean, something along this one about Vi:
>> http://hea-www.harvard.edu/~fine/Tech/vi.html<http://hea-www.harvard.edu/%7Efine/Tech/vi.html>
>>
>> Here:
>>
>> http://vimdoc.sourceforge.net/htmldoc/help.html#reference_toc
>>
>> it says "|index.txt <http://vimdoc.sourceforge.net/htmldoc/index.html>|
>>
>> alphabetical index of all commands", but if I click on "index.txt", I
>> get redirected to main help page.
>>
>> Disclosure: I'm not a Vim user, but I'd like to learn how much Vim
>> emulators I use differ from the reference implementation.
>>
>> Thanks.
>>
>>
>> --
>>
>> You received this message from the "vim_use" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>
> Well, apparently that index.html link erroneouslylinks to the HTML version
> of help.txt, rather than to that of index.txt.
>
> So, here's how to get the index of all Vim commands:
> 1. Install Vim
> 2. Start it.
> 3. Once it is running, type ":help index.txt" (without the quotes, but with
> the colon, and finish it by hitting the Enter key).
>
> Vim will then show you the file index.txt, one of its many buit-in help
> files.
>
> However, like Marc said, Vim is more that a collection of commands, it is
> also how to use them. I would not recommend to "learn" the Vim help by rote,
> nor even to read all the help files top-to-bottom in sequence, any more than
> you should read all the articles in an encyclopaedia in sequence from A to B
> to C etc. to Z.
>
> What I recommend is to read the help, after you have started using Vim,
> like you would read an encyclopaedia: start by what you want information
> about, then follow the hotlinks in the text, all that without leaving Vim.
> Recently, a new help file has been added, about using the Vim help: by
> putting together in one place information which used to be in various
> obscure places, this change makes learning Vim much more painless. You would
> get it by doing ":help helphelp.txt" or, if you don't care about the
> heading, ":help helphelp".
>
>
> Best regards,
> Tony.
> --
> Ogden's Law:
>        The sooner you fall behind, the more time you have to catch
> up.
>

Thank you for providing the solution.  I realize that Vim's power can be
fully understood only by using it, but I've settled upon another editor
already.  Such editor provides a Vim emulation mode which is scantly
documented, with the assumption that you can go to Vim manual for further
reference.  I've been using such Vim-clone for a while, and I'm looking for
ways to shortcut my tasks even more.  Now, I'm going to read Vim's manual
from cover to cover, and with a command reference at hand, I can "force"
myself to include more and more commands into my editing routine.

Happy Vimming!

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to