Note the documentation files use (4) spaces for indentation.

git-svn-id: https://geany.svn.sourceforge.net/svnroot/geany/trunk@4198 ea778897-0a13-0410-b9d1-a72fbfd435f5

HACKING

@@ -159,6 +159,8 @@ to set warning options (as well as anything else e.g. -g -O2).
 Style
 ^^^^^
 * We use a tab width of 4 and indent completely with tabs not spaces.
+  Note the documentation files use (4) spaces instead, so you may want
+  to use the 'Detect from file' indent pref.
 * Use the multiline comment ``/* */`` to comment small blocks of code,
   functions descriptions or longer explanations of code, etc. C++ single
   line comments will cause portability issues. The more comments are in
@@ -197,7 +199,7 @@ Example::
     {
         gint foo, bar;  /* variables can go on the same line */
         gchar *ptr;     /* pointer symbol must go next to variable name, not type */
-        gchar *another; /* pointers should go on separate lines */
+        gchar *another; /* pointers should normally go on separate lines */
 
         if (foo)
         {