[Bash-completion-commits] [SCM] bash-completion branch, master, updated. 805537670f7f306f8e5062731b77111626921bfb

[Freddy Vulto]

The following commit has been merged in the master branch:
commit ec2e190cbb14aa952499805a534dacd3f3be6fe4
Author: Freddy Vulto <fvulto at gmail.com>
Date:   Mon Apr 20 10:07:29 2009 +0200

    Fixed asciidoc-8.4.3 errors

diff --git a/doc/main.txt b/doc/main.txt
index 93ab106..d9cdd82 100644
--- a/doc/main.txt
+++ b/doc/main.txt
@@ -3,6 +3,14 @@ Bash-completion
 Freddy Vulto (FVu)
 v1.0, Mar 2009
 
+Preface
+=======
+Bash completion extends bashs standard completion behavior to achieve
+complex command lines with just a few keystrokes.  This project was
+conceived to produce programmable completion routines for the most
+common Linux/UNIX commands, reducing the amount of typing sysadmins
+and programmers need to do on a daily basis.
+
 // include::intro.txt[]
 // include::bash_completion.txt[]
 
diff --git a/doc/styleguide.txt b/doc/styleguide.txt
index 7dd7c20..d945b1d 100644
--- a/doc/styleguide.txt
+++ b/doc/styleguide.txt
@@ -1,6 +1,8 @@
 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.
@@ -13,8 +15,8 @@ simple matching vs extended globbing
 ------------------------------------
 in case statements: -@(a|b)) vs -a|-b)
 
-[[ ]] vs [ ]
-------------
+testing with [[ ]] vs [ ]
+-------------------------
 
 indentation
 -----------

-- 
bash-completion