diff options
| author | poohzrn <poohzrn@users.noreply.github.com> | 2016-11-24 20:19:24 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-11-24 20:19:24 +0100 |
| commit | 10bacf09960f91f6917287df806e6e4ab8b63d8c (patch) | |
| tree | aa38b1664634a830830df6b8da4d408c31684b6d | |
| parent | f7e6236fe8c1e9a31750c6d13931e591b44b5e3d (diff) | |
| download | ale-10bacf09960f91f6917287df806e6e4ab8b63d8c.zip | |
Fix links to `handlers.vim`
| -rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6ab1dc5f..890fb8f0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,9 +35,9 @@ If you want to credit multiple authors, you can comma separate them. # 2.1. Adding a New Linter -If you add a new linter, look for existing handlers first in the [handlers.vim](plugin/ale/handlers.vim) file. One of the handlers +If you add a new linter, look for existing handlers first in the [handlers.vim](autoload/ale/handlers.vim) file. One of the handlers there may already be able to handle your lines of output. If you find that your new linter replicates an existing error handler, -consider pulling it up into the [handlers.vim](plugin/ale/handlers.vim) file, and use the generic handler in both places. +consider pulling it up into the [handlers.vim](autoload/ale/handlers.vim) file, and use the generic handler in both places. When you add a linter, make sure the language for the linter and the linter itself are present in the table in the [README.md](README.md) file and in the Vim [help file](doc/ale.txt). The programs and linters are sorted alphabetically in the |