>
> 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
This has been pretty much my way of learning as well... a lot of
testing of bits from other peoples' .vimrc files, a lot of vim wiki
tips and stack overflow, etc. sites and then reading of very specific
parts of the manual.
And while I've done some light programming in the past, my use of Vim
is all about general text editing and editing of prose plain and with
Markdown, LaTeX, ConTeXt, etc.
The only "danger" in the approach, for me, has been that there are so
many ways to do things--even setting aside deprecated/eclipsed
methods--that it can be hard to know what is "best" (if, indeed, it
matters).
c
--
Chris Lott <chris@chrislott.org>
--
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