Lines Matching refs:plugin
17 |05.6| Adding a plugin
146 This loads the "matchit" plugin if the required features are available.
285 filetype plugin indent on
297 2. Using filetype plugin files
302 |write-filetype-plugin|.
391 For example, the matchit plugin. This plugin makes the "%" command jump to
395 To start using the matchit plugin, add one line to your vimrc file: >
398 That's all! After restarting Vim you can find help about this plugin: >
401 This works, because when `:packadd` loaded the plugin it also added the
416 ~/.vim/pack/fancy/start/fancytext/plugin/fancy.vim ~
423 *05.6* Adding a plugin *add-plugin* *plugin*
425 Vim's functionality can be extended by adding plugins. A plugin is nothing
427 can add a plugin very easily by dropping it in your plugin directory.
432 global plugin: Used for all kinds of files
433 filetype plugin: Only used for a specific type of file
436 |add-filetype-plugin|.
439 GLOBAL PLUGINS *standard-plugin*
445 |standard-plugin-list|. Also see |load-plugins|.
447 *add-global-plugin*
448 You can add a global plugin to add functionality that will always be present
449 when you use Vim. There are only two steps for adding a global plugin:
450 1. Get a copy of the plugin.
457 - Some are always loaded, you can see them in the directory $VIMRUNTIME/plugin.
462 - You could write one yourself, see |write-plugin|.
470 First read the text in the plugin itself to check for any special conditions.
471 Then copy the file to your plugin directory:
473 system plugin directory ~
474 Unix ~/.vim/plugin/
475 PC $HOME/vimfiles/plugin or $VIM/vimfiles/plugin
476 Amiga s:vimfiles/plugin
477 Macintosh $VIM:vimfiles:plugin
478 Mac OS X ~/.vim/plugin/
480 Example for Unix (assuming you didn't have a plugin directory yet): >
483 mkdir ~/.vim/plugin
484 cp /tmp/yourplugin.vim ~/.vim/plugin
486 That's all! Now you can use the commands defined in this plugin.
488 Instead of putting plugins directly into the plugin/ directory, you may
489 better organize them by putting them into subdirectories under plugin/.
490 As an example, consider using "~/.vim/plugin/perl/*.vim" for all your Perl
494 FILETYPE PLUGINS *add-filetype-plugin* *ftplugins*
499 :filetype plugin on
503 If you are missing a plugin for a filetype you are using, or you found a
504 better one, you can add it. There are two steps for adding a filetype plugin:
505 1. Get a copy of the plugin.
512 type of file is mentioned, then you know if the plugin is a global or a
519 You can add a filetype plugin by dropping it in the right directory. The
521 plugins, but the last part is "ftplugin". Suppose you have found a plugin for
527 If that file already exists you already have a plugin for "stuff". You might
528 want to check if the existing plugin doesn't conflict with the one you are
538 trouble if you add a second plugin and the filetype has more than six
557 The <filetype> part is the name of the filetype the plugin is to be used for.
558 Only files of this filetype will use the settings from the plugin. The <name>
559 part of the plugin file doesn't matter, you can use it to have several plugins
567 |ftplugin-overrule| Overruling the settings from a global plugin.
568 |write-plugin| How to write a plugin script.
569 |plugin-details| For more information about using plugins or when your
570 plugin doesn't work.
576 If you are lucky, the plugin you installed also comes with a help file. We
578 for your new plugin.
579 Let us use the "doit.vim" plugin as an example. This plugin comes with
580 documentation: "doit.txt". Let's first copy the plugin to the right
585 :!mkdir ~/.vim/plugin
586 :!cp /tmp/doit.vim ~/.vim/plugin