This repository contains the indentation, syntax and ftplugin scripts which are shipped with Vim for the Erlang programming language. Here you can download the newest version and contribute.
Vim's built-in package manager
This is the recommended installation method if you use at least Vim 8 and you don't use another package manager.
Information about Vim's built-in package manager: :help packages
.
Installation steps:
-
Clone this repository (you can replace
foo
with the directory name of your choice):$ git clone https://github.com/vim-erlang/vim-erlang-runtime.git \ ~/.vim/pack/foo/start/vim-erlang-runtime
-
Restart Vim.
Pathogen
Information about Pathogen: Pathogen repository.
Installation steps:
-
Clone this repository:
$ git clone https://github.com/vim-erlang/vim-erlang-runtime.git \ ~/.vim/bundle/vim-erlang-runtime
-
Restart Vim.
Vundle
Information about Vundle: Vundle repository.
Installation steps:
-
Add
vim-erlang-runtime
to your plugin list in.vimrc
by inserting the line that starts withPlugin
:call vundle#begin() [...] Plugin 'vim-erlang/vim-erlang-runtime' [...] call vundle#end()
-
Restart Vim.
-
Run
:PluginInstall
.
Vim-Plug
Information about Vim-Plug: vim-plug repository.
Installation steps:
-
Add
vim-erlang-runtime
to your plugin list in.vimrc
by inserting the line that starts withPlug
:call plug#begin() [...] Plug 'vim-erlang/vim-erlang-runtime' [...] call plug#end()
-
Restart Vim.
-
Run
:PlugInstall
.
The following snippet re-indents all src/*.?rl
files using the indentation
shipped with Vim:
vim -ENn -u NONE \
-c 'filetype plugin indent on' \
-c 'set expandtab shiftwidth=4' \
-c 'args src/*.?rl' \
-c 'argdo silent execute "normal gg=G" | update' \
-c q
Notes:
-
This can be for example added to a Makefile as a "re-indent rule".
-
You can use the
expandtab
,shiftwidth
andtabstop
options to customize how to use space and tab characters. The command above uses only spaces, and one level of indentation is 4 spaces. -
If you would like to use a different version of the indentation script from that one shipped in Vim, then also add the following as the first command parameter (replace the
/path/to
part):-c ':set runtimepath^=/path/to/vim-erlang-runtime/'
This plugin augments vim's path
setting to include common Erlang source and
header file paths. These paths are relative to the current directory so ensure
that your vim working directory is at your project's root (see :help current-directory
).
To disable this feature, add the following setting:
set g:erlang_extend_path=0
This repository contains the following files and directories:
-
ftdetect/erlang.vim
: Script for detecting Erlang files based on file extension. See:help ftdetect
.File type detection based on content (e.g., when the first line is
#!/usr/bin/escript
) is not in this file. See:help new-filetype-scripts
. -
ftplugin/erlang.vim
File type plugin for Erlang files. See:help ftplugin
.This file is also distributed with Vim as
runtime/ftplugin/erlang.vim
. -
indent/erlang.vim
: Indentation plugin for Erlang files. See:help indent-expression
.This file is also distributed with Vim as
runtime/indent/erlang.vim
. -
syntax/erlang.vim
: Syntax highlight plugin for Erlang files. See:help syntax
.This file is also distributed with Vim as
runtime/syntax/erlang.vim
. -
test
: Manual and automatic test that help the development and testing of vim-erlang-runtime.
The Vim repository contains the following Erlang-related files:
-
runtime/compiler/erlang.vim
: Allows simple Erlang files to be compiled after calling:compiler erlang
.vim-erlang-compiler
has a similar but broader scope. -
runtime/doc/syntax.txt
: Contains documentation about configuringruntime/syntax/erlang.vim
. -
runtime/filetype.vim
: Sets the file type toerlang
if the file name matches either*.erl
,*.hrl
or*.yaws
. The list of patterns is a subset of the patterns inftdetect/erlang.vim
in this repository. -
runtime/ftplugin/erlang.vim
: Same asftplugin/erlang.vim
in this repository. -
runtime/indent/erlang.vim
: Same asindent/erlang.vim
in this repository. -
runtime/makemenu.vim
: Allows Erlang to be selected in the syntax menu. See alsoruntime/synmenu.vim
. -
runtime/scripts.vim
: Sets the file type toerlang
if the first line of the file matches^#! [...]escript
. (It is not trivial what is accepted in the[...]
part.) -
runtime/synmenu.vim
: Allows Erlang to be selected in the syntax menu. See alsoruntime/makemenu.vim
. -
runtime/syntax/erlang.vim
: Same assyntax/erlang.vim
in this repository. -
src/testdir/test_filetype.vim
: An automatic test for setting file types.
The indentation script can be tested in the following way:
-
Copy
syntax/erlang.vim
into~/syntax
. -
Change to the
test
directory and opentest/test_indent.erl
.Note:
test_indent.erl
always shows how the Erlang code is indented by the script – not how it should be. -
Source
helper.vim
(:source helper.vim
) -
Press F1 to load the new indentation (
indent/erlang.vim
). -
Press F3 to re-indent the current line. Press shift-F3 to print a log.
-
Press F4 to re-indent the current buffer.
-
Press F5 to show the tokens of the current line.
Note: When the indentation scripts detects a syntax error in test mode (i.e.
when it was loaded with F1
from helper.vim
), it indents the line to column
40 instead of leaving it as it is. This behavior is useful for testing.
The tests for the include
and define
options in test_include_search.vader
are run using the Vader Vim plugin.
A common pattern to use for test cases is to do the following:
Given:
text to test
Do:
daw
Expect:
to text
The text that should be tested is placed in the Given
block. A normal command
is placed in the Do
block and the expected output in the Expect
block. The
cursor is by default on the first column in the first line, and doing daw
should therefore delete around the first word.
The simplest way to run a Vader test file is to open the test file in Vim and
run :Vader
. To run it from the command line, do vim '+Vader!*' && echo Success || echo Failure
. If the environment variable VADER_OUTPUT_FILE
is
set, the results are written to this file.
To test the code with only the wanted plugins loaded and without a vimrc, you
can go to the test
directory and execute the following command:
vim -N -u NONE \
-c 'set runtimepath=..,$VIMRUNTIME,~/.vim/plugged/vader.vim' \
-c 'runtime plugin/vader.vim' \
-c 'filetype plugin indent on' \
-c 'Vader!*' \
&& echo Success || echo Failure
The command does the following:
-
Starts Vim with
nocompatible
set and without sourcing any vimrc. -
Puts the directory above the current one, i.e. the root directory of this repository, first in the
runtimepath
, such that the ftplugin, indent etc. from this repository are sourced first. Then the regular runtime path is added and finally the path to where Vader is installed is added (this will be different depending on which plugin manager you use, the path below is where vim-plug puts it). -
Sources the Vader plugin file so that the
Vader
command can be used. -
Enables using filetype specific settings and indentation.
-
Runs all Vader test files found in the current directory and then exits Vim.
-
Echoes
Success
if all test cases pass, elseFailure
.
For more details, see the Vader repository.
- Please read the Contributing section of the
vim-erlang
README.