Tim Chase wrote: <tofu snipping> >> 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." > 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." > VimScript is fairly easy to pick up if you've used any other > language. The obvious place to start is > :help script > :help write-plugin > :help write-filetype-plugin > All of those help targets are in the same file, so you may just > want to read it from top-to-bottom. However, Vim-script is > pretty close to many other scripting languages I've used (some of > the syntax seems Python and Javascript influenced), so it's > pretty easy to pick up. > > -tim Create my own, hm? Well, I may eventually. For the time being, I was just curious how to use readily made wheels to gain a little speed. And it seems you've tossed a match in my direction, oh wise vim guru. I'll be off now to further explore the signposts you offered. Thank you. </tofu snipping> --- Ben --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
