From 6d8e4a641c8dcdaac7b8c65b8755efb35febee66 Mon Sep 17 00:00:00 2001 From: rymdbar Date: Mon, 27 Oct 2025 13:56:35 +0100 Subject: [PATCH] Make documentation mirror custom_linting_rules (#5056) Co-authored-by: cos --- doc/ale-development.txt | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/ale-development.txt b/doc/ale-development.txt index c14da3ba..0809f463 100644 --- a/doc/ale-development.txt +++ b/doc/ale-development.txt @@ -85,9 +85,11 @@ The following general coding standards should be adhered to for Vim code. * Try to keep lines no longer than 80 characters, but this isn't an absolute requirement. * Use 4 spaces for every level of indentation in Vim code. -* Add a blank line before every `function`, `if`, `for`, `while`, or `return`, - which doesn't start a new level of indentation. This makes the logic in - your code easier to follow. +* Add a blank line before every `function`, `if`, `for`, `while`, `try`, or `return`, + which doesn't start a new level of indentation. When adding more code on the + same indentation level, also add blank lines after every corresponding end + for those mentioned keywords. This makes the logic in your code easier to + follow. * End every file with a trailing newline character, but not with extra blank lines. Remove trailing whitespace from the ends of lines. * Write the full names of commands instead of abbreviations. For example, write