Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Support for Perl 5 and Perl 6 in Vim

branch: master

This branch is 0 commits ahead and 0 commits behind master

Fetching latest commit…


Cannot retrieve the latest commit at this time

Octocat-spinner-32 contrib
Octocat-spinner-32 ftplugin
Octocat-spinner-32 indent
Octocat-spinner-32 syntax
Octocat-spinner-32 t
Octocat-spinner-32 t_source
Octocat-spinner-32 tools
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 Changes
Octocat-spinner-32 Makefile


This is the aggregation of all the various Perl-related syntax and helper files for Perl 5 and Perl 6.


You can install vim-perl using

  • Pathogen and git submodules
  • Vundle
  • VAM

They were all tested and work: please read the related documentation on the related sites.

The legacy method is to install just do a "make install" and you'll get the .vim files all installed in your ~/.vim directory.

Getting Help

Any bug reports/feature requests/patches should be directed to the vim-perl group.

When reporting bugs in the highlighting of items, please include an example file as well as a screenshot demonstrating the problem.


Curly braces inside of regexes/strings are considered when I use %

(See also GH #86)

Vim itself only considers double quotes in this scenario; the matchit plugin, however, can deal with this scenario and vim-perl's files are set up to work with it should you choose to use it.

Can you add highlighting for Moose, Try::Tiny, Test::More, etc, keywords?

We have syntax "extensions" under the contrib directory; you can find custom highlighting for these sorts of things there.


If you would like to contribute to vim-perl (which would be greatly appreciated!), you may find the and scripts of use. What I do is drop the sources for Moose, Data::Printer, and Regexp::Debugger in the corpus directory and use the scripts to make sure my changes don't cause regressions in highlighting and folding.

Andy (

Something went wrong with that request. Please try again.