Contents
Compilation of various setup scripts for VIM
To use these files with VIM you will need to do the following :
- Copy these files to $HOME/.vim or to the proper system-wide location
- Enable them with the command
filetype plugin indent on
in your $HOME/.vimrc file.
Includes the following files */puppet.vim
Includes the following files:
folding-ideas/*
syntax/python.vim
- This section (Puppet syntax highlighting scripts for Vim) of this
README.rst
file
Enhanced version of the original Python syntax highlighting script. Based on
python.vim
from Vim 6.1 distribution by Neil Schemenauer (nas at python dot
ca). Check also python.vim page on vim.org.
Please use the following channels for reporting bugs, offering suggestions or feedback:
- python.vim issue tracker: https://github.com/hdima/python-syntax/issues
- Email: Dmitry Vasiliev (dima at hlabs.org)
- Send a message or follow me for updates on Twitter: @hdima
Changes from the original python.vim
are:
- Added support for Python 3 syntax highlighting
- Added
:Python2Syntax
and:Python3Syntax
commands which allow to switch between Python 2 and Python 3 syntaxes respectively without reloads/restarts - Updated strings highlighting
- Enhanced special symbols highlighting inside strings
- Enhanced highlighting of numeric constants
- Added optional highlighting for %-formatting inside strings
- Added highlighting for magic comments: source code encoding and #! (executable) strings
- Added highlighting for new exceptions and builtins
- Added highlighting for doctests
- Added highlighting for new
@decorator
syntax introduced in Python 2.4a2 - Added highlighting for the following errors:
- invalid symbols in source file
- mixing spaces and tabs
- invalid numeric constants
- invalid %-formatting inside strings
- invalid variable names
- trailing spaces (triggered by the
python_highlight_space_errors
option)
Some of these features was later backported into the original python.vim
.
There are two commands to enable or disable an option:
:let OPTION_NAME = 1
- Enable option
:let OPTION_NAME = 0
- Disable option
For example to enable all syntax highlighting features you can place the
following command in your ~/.vimrc
script:
let python_highlight_all = 1
python_version_2
- Enable highlighting for Python 2 (Python 3 highlighting is enabled by
default). Can also be set as a local to buffer
b:python_version_2
variable.
The following local to buffer commands can be used to switch between two highlighting modes:
:Python2Syntax
- Switch to Python 2 highlighting mode
:Python3Syntax
- Switch to Python 3 highlighting mode
python_highlight_builtins
- Highlight builtin functions and objects
python_highlight_builtin_objs
- Highlight builtin objects only
python_highlight_builtin_funcs
- Highlight builtin functions only
python_highlight_exceptions
- Highlight standard exceptions
python_highlight_string_formatting
- Highlight
%
string formatting python_highlight_string_format
- Highlight syntax of
str.format
syntax python_highlight_string_templates
- Highlight syntax of
string.Template
python_highlight_indent_errors
- Highlight indentation errors
python_highlight_space_errors
- Highlight trailing spaces
python_highlight_doctests
- Highlight doc-tests
python_print_as_function
- Highlight
print
statement as function for Python 2 python_highlight_file_headers_as_comments
- Highlight shebang and coding headers as comments
python_highlight_all
- Enable all the options above. NOTE: This option don't override any previously set options
python_slow_sync
- Can be set to 0 for slow machines
List of the contributors in alphabetical order:
- Andrea Riciputi
- Anton Butanaev
- Caleb Adamantine
- David Briscoe
- Elizabeth Myers
- Jeroen Ruigrok van der Werven
- John Eikenberry
- Marc Weber
- Pedro Algarvio
- Victor Salgado
- Will Gray
- Yuri Habrusiev
Includes the following files : indent/python.vim
This small script modifies vim's indentation behavior to comply with PEP8 and my aesthetic preferences. Most importantly:
foobar(foo, bar)
and:
foobar( foo, bar )
Please note that Kirill Klenov's python-mode ships its own version of this bundle. Therefore, if you want to use this version specifically, you’ll have to disable python-mode’s using:
let g:pymode_indent = 0
This script is based on one from vim’s official script repo that was not originally written by me. Unfortunately the indentation was off by one character in one case and the script hasn’t been updated since 2005.
Even more unfortunately, I wasn't able to reach any of the original authors/maintainers: David Bustos and Eric Mc Sween.
So I fixed the annoyance it with the help of Steve Losh and am putting it out here so you don’t have to patch the original yourself. The original patch is still available here.
Over the time a lot more improvements have been contributed by generous people.
I’d like to thank the original authors here for their work and release it hereby to the Public Domain (using the CC0 licence) since I hope that would be in their spirit. If anyone with a say in this objects, please let me know immediately. Also, if someone is in contact with one of them, I would appreciate being introduced.
While my Vimscript skills are still feeble, I intend to maintain it for now. This mainly means that I'll triage through bugs and pull requests but won't be fixing much myself.
vim-python-pep8-indent
has been originally written by David Bustos and Eric Mc Sween who both are unreachable unfortunately.
It is currently maintained by Hynek Schlawack with the generous help of the following contributors:
- 0player
- Bryan Bennett
- Clay Gerrard
- Hassan Kibirige
- Jelte Fennema
- Johann Klä
- Joseph Irwin
- Steve Losh
- Sylvain Soliman
Includes the following files :
autoload/rubycomplete.vim
compiler/*ruby*.vim
compiler/rake.vim
compiler/rspec.vim
doc/*ruby*
etc/examples/indent/closing_brackets.rb
ftdetect/ruby.vim
ftplugin/*ruby.vim
indent/*ruby.vim
syntax/*ruby.vim
This project contains Vim configuration files for editing and compiling Ruby within Vim. See the project homepage for more details.
Homepage: https://github.com/vim-ruby Explanation: https://github.com/vim-ruby/vim-ruby/wiki
- The autoload, compiler, ftdetect, ftplugin, indent and syntax directories contain the ruby*.vim files that are to be copied to a location somewhere in the Vim 'runtimepath'.
- By downloading the project via a snapshot or Git, you can keep up with the latest, make changes, and install the files to a Vim directory.
- By downloading one of the tarballs, you can easily install the latest stable or development version wherever you like on your machine. No README etc. just Vim files. You would typically install these into either $VIM/vimfiles, for system-wide use, or $HOME/.vim ($HOME/vimfiles on Windows) for personal use.
- Remember that when you install Vim in the first place, all of these files are present. The purpose of downloading and installing them from GitHub is to get the latest version of them.
- Project was migrated from CVS in August, 2008.
- Files are tagged according to which version of Vim they are released in.
- The project was initiated in July 2003, when the current version of Vim was 6.2. Thus every file began its life tagged as vim6.2.
- Modifications to the files are made in the expectation that they need to be tested by interested users. They therefore (probably) don't have a tag, and are available via "git pull --rebase", or a development snapshot.
- When a modification is considered stable, it is given a tag. Everything that is stable gets released in vim-ruby-YYY.MM.DD.tar.gz files.
- When a new version of Vim is about to be released, the stable tarball is contributed to it. After it has been released, the files are tagged accordingly.
- MORAL OF THE STORY: modifications are committed to the head of the tree; when they are ready for release into userland, they are tagged "stable".
- If there's something about the project or its concepts that you don't understand, send an email to the release coordinator, Doug Kearns (dougkearns at gmail.com).
- To ask about the contents of the configuration files, open a GitHub issue or ask on the mailing list, as different people maintain the different files.
- While the individual effort to maintain these files has a long history, this actual project began in late July 2003.
- Mark Guzman <segfault@hasno.info>
- Doug Kearns <dougkearns@gmail.com>
- Tim Pope <vim@NOSPAMtpope.org>
- Andrew Radev <andrey.radev@gmail.com>
- Nikolai Weibull <now@bitwi.se>
- Michael Brailsford <brailsmt@yahoo.com>
- Sean Flanagan <sdflanagan@ozemail.com.au>
- Tim Hammerquist <timh@rubyforge.org>
- Ken Miller <ken.miller@gmail.com>
- Hugh Sasse <hgs@dmu.ac.uk>
- Tilman Sauerbeck <tilman@code-monkey.de>
- Bertram Scharpf <info@bertram-scharpf.de>
- Gavin Sinclair <gsinclair@gmail.com>
- Aaron Son <aaronson@uiuc.edu>
- Ned Konz <ned@bike-nomad.com>
Includes the following files :
autoload/vst/*
doc2/test/png
doc2/vst*
plugin/vstplugin.vim
This is a combined version of http://www.vim.org/scripts/script.php?script_id=1334 and http://www.vim.org/scripts/script.php?script_id=1743
Requires Vim7.
VST is script which makes possible to export text files with simple markup to HTML or LaTeX format or S5 HTML presentation. Script doesn't require any external dependency and will work on any platform Vim7 is available. VST is implementation of reStructuredText.
- emphasised text (italic)
- strongly emphasised text (bold)
- hyperlinks (in various syntax forms)
- custom decorations (among them: sub, sup, big, small)
- paragraphs
- block quotes
- ordered lists
- unordered lists
- option lists
- footnotes
- citations
- images
- preformatted text
- colorized preformatted text (HTML export only)
- tables
- admonitions
- table of contents
Also bunch of auxiliary commands which should ease writing of document and navigating (folding, text table of contents, lists or declared links, replacements)
Latest version of script: http://skawina.eu.org/mikolaj/vst.zip
Help file in text form: http://skawina.eu.org/mikolaj/vst.txt
Following versions of help file was produced without any modifications to HTML or LaTeX source:
HTML: http://skawina.eu.org/mikolaj/vst.html
LaTeX file exported from vst.txt: http://skawina.eu.org/mikolaj/vst.tex
PDF file produced from vst.tex: http://skawina.eu.org/mikolaj/vst.pdf
Includes the following files :
colors/molokai.vim
Molokai is a Vim port of the monokai theme for TextMate originally created by Wimer Hazenberg.
By default, it has a dark gray background based on the version created by Hamish Stuart Macpherson for the E eBy default, it has a dark gray background based on the version created by Hamish Stuart Macpherson for the E editor.
256-Color terminals are also supported, though there are some differences with the Gui version. Only the dark gray background style is supported on terminal vim at this time.
Copy colors/molokai.vim
file into .vim/colors
folder.
If you prefer the scheme to match the original monokai background color, put this in your .vimrc file
:
let g:molokai_original = 1
There is also an alternative scheme under development for color terminals which attempts to bring the 256 color version as close as possible to the the default (dark) GUI version. To access, add this to your .vimrc
:
let g:rehash256 = 1