indent  2.2.12
About: GNU Indent makes code easier to read. It can also convert from one style of writing C to another.
  Fossies Dox: indent-2.2.12.tar.xz  ("inofficial" and yet experimental doxygen-generated source code documentation)  

indent Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies
  4. indent-2.2.12.tar.xz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).

README for GNU indent 2.2.12

GNU indent changes the appearance of a C program by inserting or deleting whitespace according to a plethora of options. Some canned styles of formatting are supported as well. GNU indent is a descendant of BSD indent. This file is part of the GNU indent distribution.

GNU indent does NOT work for C++, if it does for you then you're just lucky. Don't expect support for C++.

Read the file NEWS for more information, especially to see what's different from the last version, and what future versions may do.

To install indent, please read the file INSTALL included with the distribution.

For license and copying information, see the file COPYING.


For complete documentation on the Web, please visit:

GNU uses a language called "texinfo" for its documentation source which produces both an on-line, interactive version and a hardcopy version for printing. An HTML version is now produced as well.

The on-line versions, and indent.1, are installed along with the executable by typing "make install". Refer to the Texinfo manual for more information on the info system.

The hardcopy version is produced from the source file indent.texinfo in a pdf or Postscript format file. To produce the pdf version type:

make pdf

To produce the Postscript version, type:

make ps

Note that you must have the TeX typographical system installed for this to work.

The HTML version is included along with the distribution, and consists of the file:


This file can also be accessed at the URL

To create the HTML version from the texinfo version, type:

 make html

Obviously you will need the texi2html tool.

Bug reports

Please address bug-reports and suggestions or comments to:

How to report bugs:

Please begin your bug report with a concise and factual description of the behaviour you consider to be abberant. If you have narrowed the problem down to the use of a particular option, please mention that. In general, also be sure to mention the command line options used to invoke indent, as well as the contents of your if you are using one.

Then include the smallest possible piece of code which generates the described symptom. It is very helpful if you can manage to reduce the size of the sample code.

Finally, if you have investigated the problem further, include debugger stack traces, modifications, or speculation you have.

Sending code

If you send a patch as part of your bug fix, or send us code for new features, please send them as diffs. In particular, include the result of diff -c <old_file> <new_file>.

Please make sure that patches you provide apply cleanly to the latest code published in the Mercurial repo:

Because of the regression testing the project requires of indent, it is extremely unlikely that your code will be installed into indent "as-is"; however it may still be helpful, and will likely have solved your particular problem.