summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorDavid Paleino <dapal@debian.org>2009-11-28 11:06:11 +0100
committerDavid Paleino <dapal@debian.org>2009-11-28 11:06:11 +0100
commit3191d14a554c4a19bf5c11538da5c0e9a467059e (patch)
treee899fcd97dadbe5742a86140940e7d426e955205 /doc
parentea2a5d2aedabeea6cceefaa3a32596aa886a46a2 (diff)
downloadbash-completion-3191d14a554c4a19bf5c11538da5c0e9a467059e.tar.gz
Wrap lines
Diffstat (limited to 'doc')
-rw-r--r--doc/styleguide.txt13
1 files changed, 10 insertions, 3 deletions
diff --git a/doc/styleguide.txt b/doc/styleguide.txt
index b994ff18..39aedf82 100644
--- a/doc/styleguide.txt
+++ b/doc/styleguide.txt
@@ -3,9 +3,16 @@ Coding Style Guide
Introduction
------------
-This document attempts to explain the basic styles and patterns that are used in the bash completion. New code should try to conform to these standards so that it is as easy to maintain as existing code. Of course every rule has an exception, but it's important to know the rules nonetheless!
-
-This is particularly directed at people new to the bash completion codebase, who are in the process of getting their code reviewed. Before getting a review, please read over this document and make sure your code conforms to the recommendations here.
+This document attempts to explain the basic styles and patterns that
+are used in the bash completion. New code should try to conform to
+these standards so that it is as easy to maintain as existing code.
+Of course every rule has an exception, but it's important to know
+the rules nonetheless!
+
+This is particularly directed at people new to the bash completion
+codebase, who are in the process of getting their code reviewed.
+Before getting a review, please read over this document and make
+sure your code conforms to the recommendations here.
Indentation
-----------