Revisions
-
nelstrom revised this gist
Jun 30, 2011 . 1 changed file with 1 addition and 1 deletion.There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -3,7 +3,7 @@ plugin these files are sourced for all file types doc naming convention: name_of_plugin.txt these files document the functionality of a plugin color -
nelstrom created this gist
Jun 30, 2011 .There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode charactersOriginal file line number Diff line number Diff line change @@ -0,0 +1,39 @@ plugin naming convention: name_of_plugin.vim these files are sourced for all file types doc naming convention: name_of_plugin.vim these files document the functionality of a plugin color naming convention: name_of_colorscheme.vim these files define a colorscheme for syntax highlighting syntax naming convention: filetype.vim these files define the operators, keywords and constructs of a language the syntax groups defined here are used by the colorscheme (much like HTML elements, ids and classes provide hooks for CSS styling) indent naming convention: filetype.vim these files define the `indentexpr` for a language the `indentexpr` is used by the `=`, `o` and `O` commands ftplugin naming convention: filetype.vim these files are sourced only for the specified filetype suitable for defining functionality for one particular language e.g. a command to build an HTML document from a markdown source autoload naming convention: ???.vim Vim provides a mechanism to ensure that startup time isn't compromised when large scripts are loaded. Functions, commands and mappings defined in the autoload directory are defined with an empty implementation on startup. It is only when these commands are invoked by the user that the script is sourced in full, and each command is attached to its implementation. :help autoload-functions :help 41.14