>>> It is probably buried in the reference documents somewhere. >> In all likelyhood, yes -- Vim's documentation is amazingly >> detailed & thorough. However *finding* what you want in that >> documentation can be a challenge even for folks with years of >> experience. > > That was exactly my point. At times, a flooding of good documentation > can leave a newbie seeking an advanced degree in astrophysics. When all > they really need is a simple, "hey buddy, you use a match to light fire."
It helps to know how to navigate the help, along with its conventions. Using <tab> or control+D after typing some relevant key-word shows what vim knows as tagged help. E.g. :help script<C-D> where <C-D> is pressing control+D after typing "script". Vim will respond with all of the indexed targets (tags) that it knows about in the help that match what you've typed. Additionally, you can use the ":helpgrep" command to search the help: :helpgrep script and then use :cn :cp to navigate to the next/previous hit as detailed at :help location-list :help :helpgrep >> You speak of "the scripts" as if we should know what you mean :) > > :) <chuckling> You know, the "precious" ones, scripts got from vim.org, > not been to Dr. Chip yet. "Keep hearing of this Dr. Chip. Might need to > see who they are." Most of Dr. Chip's scripts are on vim.org -- I believe he keeps the stable versions there and the bleeding-edge versions on his personal web-site http://mysite.verizon.net/astronaut/vim/ Ben Fritz gave a better summary than I could regarding how to install various scripts. Hope this continues to help you on your way... -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
