> 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.
> How do you actually use the scripts? Is it dependent upon each > script? Is there a simple generic process for using them in > Windows Vista, Linux? You speak of "the scripts" as if we should know what you mean :) Do you want to enable stock scripts that are distributed with Vim? Are you downloading enhancement scripts from vim.org or from Dr. Chip's huge library of nifty scripts (or other places on the internets)? Do you want to create your own? > I read about folks using these scripts, having headaches and > such. It makes a person say, "hey I want some headaches, too." VimScript is fairly easy to pick up if you've used any other language. The obvious place to start is :help script Most of the headaches I've seen stem from (1) getting started, (2) wrong assumptions about settings such as 'magic' (3) platform dependence or (4) backwards compatibility. Usually the "getting started" difficulty comes from trying to write a plugin. This is written up in a fairly detailed fashion at :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 --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
