>> On Jan 16, 2012, at 1:37 PM, Phil Dobbin wrote:
>> Be warned. I've lost days of life reading vim's documentation. Habit
>> forming... ;-)
>
> As a novice, and nonprogrammer, I find it hard to get help from the help. I
> try. The elementary stuff I can take in. But must of it, as I and others have
> said previously, seems written for those who already know how to do whatever
> it is the documentation might "help" them with. When I can't get help from the
> help I turn to the FAQs--or ask here. It's always a lot more helpful--really!
I first started reading the documentation in a web browser & found it very
hard going. Page after page of uniform black text on a white background that
was very thorough indeed.
So I started to search the Internet for people's hints, tips, vimrc's, etc &
then read most of the online vim wiki before finally settling upon calling
specific parts of the documentation when needed & slowly started to
understand the way it was written. This mailing list is an invaluable
resource of very helpful people who are very patient & friendly to newcomers
(some other lists are the exact opposite I'm afraid to say. Not vim related
ones however) so in time it's all starting to drop into place.
Happy vimming :-)
Cheers,
Phil...
--
Some [people] feel that the best way to improve Perl would be to go
back in time and shoot the author before he wrote it.
-Larry Wall
--
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
No comments:
Post a Comment