{
    "mode": "info",
    "parameter": "indent",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/indent/json",
    "generated": "2026-06-16T04:50:10Z",
    "sections": {
        "'indent': Indent and Format C Program Source": {
            "content": "The 'indent' program changes the appearance of a C program by inserting\nor deleting whitespace.\n\nThis is Edition 2.2.12, 2 September 2018, of 'The 'indent' Manual',\nfor Indent Version 2.2.12.\n\n* Menu:\n\n* Indent Program::              The 'indent' Program\n* Option Summary::              Option Summary\n* Index::                       Index\n\nFile: indent.info,  Node: Indent Program,  Next: Option Summary,  Prev: Top,  Up: Top\n",
            "subsections": []
        },
        "1 The 'indent' Program": {
            "content": "The 'indent' program can be used to make code easier to read.  It can\nalso convert from one style of writing C to another.\n\n'indent' understands a substantial amount about the syntax of C, but\nit also attempts to cope with incomplete and misformed syntax.\n\nIn version 1.2 and more recent versions, the GNU style of indenting\nis the default.\n\n* Menu:\n\n* Invoking indent::             Invoking 'indent'\n* Backup files::                Backup Files\n* Common styles::               Common styles\n* Blank lines::                 Blank lines\n* Comments::                    Comments\n* Statements::                  Statements\n* Declarations::                Declarations\n* Indentation::                 Indentation\n* Breaking long lines::         Breaking long lines\n* Disabling Formatting::        Disabling Formatting\n* Miscellaneous options::       Miscellaneous options\n* Bugs::                 \tBugs\n* Copyright::                   Copyright\n\nFile: indent.info,  Node: Invoking indent,  Next: Backup files,  Up: Indent Program\n",
            "subsections": [
                {
                    "name": "1.1 Invoking 'indent'",
                    "content": "As of version 1.3, the format of the 'indent' command is:\n\n\nindent [OPTIONS] [INPUT-FILES]\n\nindent [OPTIONS] [SINGLE-INPUT-FILE] [-o OUTPUT-FILE]\n\n\nThis format is different from earlier versions and other versions of\n'indent'.\n\nIn the first form, one or more input files are specified.  'indent'\nmakes a backup copy of each file, and the original file is replaced with\nits indented version.  *Note Backup files::, for an explanation of how\nbackups are made.\n\nIn the second form, only one input file is specified.  In this case,\nor when the standard input is used, you may specify an output file after\nthe '-o' option.\n\nTo cause 'indent' to write to standard output, use the '-st' option.\nThis is only allowed when there is only one input file, or when the\nstandard input is used.\n\nIf no input files are named, the standard input is read for input.\nAlso, if a filename named '-' is specified, then the standard input is\nread.\n\nAs an example, each of the following commands will input the program\n'slithytoves.c' and write its indented text to 'slithytoves.out':\n\n\nindent slithytoves.c -o slithytoves.out\n\nindent -st slithytoves.c > slithytoves.out\n\ncat slithytoves.c | indent -o slithytoves.out\n\n\nMost other options to 'indent' control how programs are formatted.\nAs of version 1.2, 'indent' also recognizes a long name for each option\nname.  Long options are prefixed by either '--' or '+'.  (1)  In most of\nthis document, the traditional, short names are used for the sake of\nbrevity.  *Note Option Summary::, for a list of options, including both\nlong and short names.\n\nHere is another example:\n\nindent -br test/metabolism.c -l85\n\nThis will indent the program 'test/metabolism.c' using the '-br' and\n'-l85' options, write the output back to 'test/metabolism.c', and write\nthe original contents of 'test/metabolism.c' to a backup file in the\ndirectory 'test'.\n\nEquivalent invocations using long option names for this example would\nbe:\n\n\nindent --braces-on-if-line --line-length185 test/metabolism.c\n\nindent +braces-on-if-line +line-length185 test/metabolism.c\n\n\nIf you find that you often use 'indent' with the same options, you\nmay put those options into a file named '.indent.pro'.  'indent' will\nlook for a profile file in three places.  First it will check the\nenvironment variable 'INDENTPROFILE'.  If that exists its value is\nexpected to name the file that is to be used.  If the environment\nvariable does not exist, indent looks for '.indent.pro' in the current\ndirectory and use that if found.  Finally 'indent' will search your home\ndirectory for '.indent.pro' and use that file if it is found.  This\nbehaviour is different from that of other versions of 'indent', which\nload both files if they both exist.\n\nThe format of '.indent.pro' is simply a list of options, just as they\nwould appear on the command line, separated by white space (tabs,\nspaces, and newlines).  Options in '.indent.pro' may be surrounded by C\nor C++ comments, in which case they are ignored.\n\nCommand line switches are handled after processing '.indent.pro'.\nOptions specified later override arguments specified earlier, with one\nexception: Explicitly specified options always override background\noptions (*note Common styles::).  You can prevent 'indent' from reading\nan '.indent.pro' file by specifying the '-npro' option.\n\n---------- Footnotes ----------\n\n(1) '+' is being superseded by '--' to maintain consistency with the\nPOSIX standard.\n\nFile: indent.info,  Node: Backup files,  Next: Common styles,  Prev: Invoking indent,  Up: Indent Program\n"
                },
                {
                    "name": "1.2 Backup Files",
                    "content": "As of version 1.3, GNU 'indent' makes GNU-style backup files, the same\nway GNU Emacs does.  This means that either \"simple\" or \"numbered\"\nbackup filenames may be made.\n\nSimple backup file names are generated by appending a suffix to the\noriginal file name.  The default for this suffix is the one-character\nstring '~' (tilde).  Thus, the backup file for 'python.c' would be\n'python.c~'.\n\nInstead of the default, you may specify any string as a suffix by\nsetting the environment variable 'SIMPLEBACKUPSUFFIX' to your\npreferred suffix.\n\nNumbered backup versions of a file 'momeraths.c' look like\n'momeraths.c.~23~', where 23 is the version of this particular backup.\nWhen making a numbered backup of the file 'src/momeraths.c', the backup\nfile will be named 'src/momeraths.c.~V~', where V is one greater than\nthe highest version currently existing in the directory 'src'.  The\nenvironment variable 'VERSIONWIDTH' controls the number of digits,\nusing left zero padding when necessary.  For instance, setting this\nvariable to \"2\" will lead to the backup file being named\n'momeraths.c.~04~'.\n\nThe type of backup file made is controlled by the value of the\nenvironment variable 'VERSIONCONTROL'.  If it is the string 'simple',\nthen only simple backups will be made.  If its value is the string\n'numbered', then numbered backups will be made.  If its value is\n'numbered-existing', then numbered backups will be made if there\nalready exist numbered backups for the file being indented; otherwise,\na simple backup is made.  If 'VERSIONCONTROL' is not set, then 'indent'\nassumes the behaviour of 'numbered-existing'.\n\nOther versions of 'indent' use the suffix '.BAK' in naming backup\nfiles.  This behaviour can be emulated by setting 'SIMPLEBACKUPSUFFIX'\nto '.BAK'.\n\nNote also that other versions of 'indent' make backups in the current\ndirectory, rather than in the directory of the source file as GNU\n'indent' now does.\n\nFile: indent.info,  Node: Common styles,  Next: Blank lines,  Prev: Backup files,  Up: Indent Program\n"
                },
                {
                    "name": "1.3 Common styles",
                    "content": "There are several common styles of C code, including the GNU style, the\nKernighan & Ritchie style, and the original Berkeley style.  A style may\nbe selected with a single \"background\" option, which specifies a set of\nvalues for all other options.  However, explicitly specified options\nalways override options implied by a background option.\n\nAs of version 1.2, the default style of GNU 'indent' is the GNU\nstyle.  Thus, it is no longer necessary to specify the option '-gnu' to\nobtain this format, although doing so will not cause an error.  Option\nsettings which correspond to the GNU style are:\n\n-nbad -bap -nbc -bbo -bl -bli2 -bls -ncdb -nce -cp1 -cs -di2\n-ndj -nfc1 -nfca -hnl -i2 -ip5 -lp -pcs -nprs -psl -saf -sai\n-saw -nsc -nsob\n\nThe GNU coding style is that preferred by the GNU project.  It is the\nstyle that the GNU Emacs C mode encourages and which is used in the C\nportions of GNU Emacs.  (People interested in writing programs for\nProject GNU should get a copy of 'The GNU Coding Standards', which also\ncovers semantic and portability issues such as memory usage, the size of\nintegers, etc.)\n\nThe Kernighan & Ritchie style is used throughout their well-known\nbook 'The C Programming Language'.  It is enabled with the '-kr' option.\nThe Kernighan & Ritchie style corresponds to the following set of\noptions:\n\n-nbad -bap -bbo -nbc -br -brs -c33 -cd33 -ncdb -ce -ci4 -cli0\n-cp33 -cs -d0 -di1 -nfc1 -nfca -hnl -i4 -ip0 -l75 -lp -npcs\n-nprs -npsl -saf -sai -saw -nsc -nsob -nss -par\n\nKernighan & Ritchie style does not put comments to the right of code in\nthe same column at all times (nor does it use only one space to the\nright of the code), so for this style 'indent' has arbitrarily chosen\ncolumn 33.\n\nThe style of the original Berkeley 'indent' may be obtained by\nspecifying '-orig' (or by specifying '--original', using the long option\nname).  This style is equivalent to the following settings:\n\n-nbad -nbap -bbo -bc -br -brs -c33 -cd33 -cdb -ce -ci4 -cli0\n-cp33 -di16 -fc1 -fca -hnl -i4 -ip4 -l75 -lp -npcs -nprs -psl\n-saf -sai -saw -sc -nsob -nss -ts8\n\nThe Linux style is used in the linux kernel code and drivers.  Code\ngenerally has to follow the Linux coding style to be accepted.  This\nstyle is equivalent to the following settings:\n\n-nbad -bap -nbc -bbo -hnl -br -brs -c33 -cd33 -ncdb -ce -ci4\n-cli0 -d0 -di1 -nfc1 -i8 -ip0 -l80 -lp -npcs -nprs -npsl -sai\n-saf -saw -ncs -nsc -sob -nfca -cp33 -ss -ts8 -il1\n\nFile: indent.info,  Node: Blank lines,  Next: Comments,  Prev: Common styles,  Up: Indent Program\n"
                },
                {
                    "name": "1.4 Blank lines",
                    "content": "Various programming styles use blank lines in different places.\n'indent' has a number of options to insert or delete blank lines in\nspecific places.\n\nThe '-bad' option causes 'indent' to force a blank line after every\nblock of declarations.  The '-nbad' option causes 'indent' not to force\nsuch blank lines.\n\nThe '-bap' option forces a blank line after every procedure body.\nThe '-nbap' option forces no such blank line.\n\nThe '-bbb' option forces a blank line before every boxed comment\n(*Note Comments::.)  The '-nbbb' option does not force such blank lines.\n\nThe '-sob' option causes 'indent' to swallow optional blank lines\n(that is, any optional blank lines present in the input will be removed\nfrom the output).  If the '-nsob' is specified, any blank lines present\nin the input file will be copied to the output file.\n\n* Menu:\n\n* -bad::                        More on the '-bad' option.\n* -bap::                        More on the '-bap' option.\n\nFile: indent.info,  Node: -bad,  Next: -bap,  Up: Blank lines\n\n\nThe '-bad' option forces a blank line after every block of declarations.\nThe '-nbad' option does not add any such blank lines.\n\nFor example, given the input\nchar *foo;\nchar *bar;\n/* This separates blocks of declarations.  */\nint baz;\n\n'indent -bad' produces\n\nchar *foo;\nchar *bar;\n\n/* This separates blocks of declarations.  */\nint baz;\n\nand 'indent -nbad' produces\n\nchar *foo;\nchar *bar;\n/* This separates blocks of declarations.  */\nint baz;\n\nFile: indent.info,  Node: -bap,  Prev: -bad,  Up: Blank lines\n\n\nThe '-bap' option forces a blank line after every procedure body.\n\nFor example, given the input\n\nint\nfoo ()\n{\nputs(\"Hi\");\n}\n/* The procedure bar is even less interesting.  */\nchar *\nbar ()\n{\nputs(\"Hello\");\n}\n\n'indent -bap' produces\n\nint\nfoo ()\n{\nputs (\"Hi\");\n}\n\n/* The procedure bar is even less interesting.  */\nchar *\nbar ()\n{\nputs (\"Hello\");\n}\n\nand 'indent -nbap' produces\n\nint\nfoo ()\n{\nputs (\"Hi\");\n}\n/* The procedure bar is even less interesting.  */\nchar *\nbar ()\n{\nputs (\"Hello\");\n}\n\nNo blank line will be added after the procedure 'foo'.\n\nFile: indent.info,  Node: Comments,  Next: Statements,  Prev: Blank lines,  Up: Indent Program\n"
                },
                {
                    "name": "1.5 Comments",
                    "content": "'indent' formats both C and C++ comments.  C comments are begun with\n'/*', terminated with '*/' and may contain newline characters.  C++\ncomments begin with the delimiter '//' and end at the newline.\n\n'indent' handles comments differently depending upon their context.\n'indent' attempts to distinguish between comments which follow\nstatements, comments which follow declarations, comments following\npreprocessor directives, and comments which are not preceded by code of\nany sort, i.e., they begin the text of the line (although not\nnecessarily in column 1).\n\n'indent' further distinguishes between comments found outside of\nprocedures and aggregates, and those found within them.  In particular,\ncomments beginning a line found within a procedure will be indented to\nthe column at which code is currently indented.  The exception to this\nis a comment beginning in the leftmost column; such a comment is output\nat that column.\n\n'indent' attempts to leave \"boxed comments\" unmodified.  The general\nidea of such a comment is that it is enclosed in a rectangle or \"box\" of\nstars or dashes to visually set it apart.  More precisely, boxed\ncomments are defined as those in which the initial '/*' is followed\nimmediately by the character '*', '=', '', or '-', or those in which\nthe beginning comment delimiter ('/*') is on a line by itself, and the\nfollowing line begins with a '*' in the same column as the star of the\nopening delimiter.\n\nExamples of boxed comments are:\n\n/\n* Comment in a box!! *\n/\n\n/*\n* A different kind of scent,\n* for a different kind of comment.\n*/\n\n'indent' attempts to leave boxed comments exactly as they are found\nin the source file.  Thus the indentation of the comment is unchanged,\nand its length is not checked in any way.  The only alteration made is\nthat an embedded tab character may be converted into the appropriate\nnumber of spaces.\n\nIf the '-bbb' option is specified, all such boxed comments will be\npreceded by a blank line, unless such a comment is preceded by code.\n\nComments which are not boxed comments may be formatted, which means\nthat the line is broken to fit within a right margin and left-filled\nwith whitespace.  Single newlines are equivalent to a space, but blank\nlines (two or more newlines in a row) are taken to mean a paragraph\nbreak.  Formatting of comments which begin after the first column is\nenabled with the '-fca' option.  To format those beginning in column\none, specify '-fc1'.  Such formatting is disabled by default.\n\nThe right margin for formatting defaults to 78, but may be changed\nwith the '-lc' option.  If the margin specified does not allow the\ncomment to be printed, the margin will be automatically extended for the\nduration of that comment.  The margin is not respected if the comment is\nnot being formatted.\n\nIf the '-fnc' option is specified, all comments with '/*' embedded\nwill have that character sequence replaced by a space followed by the\ncharacter '*' thus eliminating nesting.\n\nIf the comment begins a line (i.e., there is no program text to its\nleft), it will be indented to the column it was found in unless the\ncomment is within a block of code.  In that case, such a comment will be\naligned with the indented code of that block (unless the comment began\nin the first column).  This alignment may be affected by the '-d'\noption, which specifies an amount by which such comments are moved to\nthe left, or unindented.  For example, '-d2' places comments two\nspaces to the left of code.  By default, comments are aligned with code,\nunless they begin in the first column, in which case they are left there\nby default -- to get them aligned with the code, specify '-fc1'.\n\nComments to the right of code will appear by default in column 33.\nThis may be changed with one of three options.  '-c' will specify the\ncolumn for comments following code, '-cd' specifies the column for\ncomments following declarations, and '-cp' specifies the column for\ncomments following preprocessor directives '#else' and '#endif'.  '-dj'\ntogether with '-cd0' can be used to suppress alignment of comments to\nthe right of declarations, causing the comment to follow one tabstop\nfrom the end of the declaration.  Normally '-cd0' causes '-c' to become\neffective.\n\nIf the code to the left of the comment exceeds the beginning column,\nthe comment column will be extended to the next tabstop column past the\nend of the code, unless the '-ntac' option is specified.  In the case of\npreprocessor directives,comments are extended to to one space past the\nend of the directive.  This extension lasts only for the output of that\nparticular comment.\n\nThe '-cdb' option places the comment delimiters on blank lines.\nThus, a single line comment like '/* Loving hug */' can be transformed\ninto:\n\n/*\nLoving hug\n*/\n\nStars can be placed at the beginning of multi-line comments with the\n'-sc' option.  Thus, the single-line comment above can be transformed\n(with '-cdb -sc') into:\n\n/*\n* Loving hug\n*/\n\nFile: indent.info,  Node: Statements,  Next: Declarations,  Prev: Comments,  Up: Indent Program\n"
                },
                {
                    "name": "1.6 Statements",
                    "content": "The '-br' or '-bl' option specifies how to format braces.\n\nThe '-br' option formats statement braces like this:\n\nif (x > 0) {\nx--;\n}\n\nThe '-bl' option formats them like this:\n\nif (x > 0)\n{\nx--;\n}\n\nIf you use the '-bl' option, you may also want to specify the '-bli'\noption.  This option specifies the number of spaces by which braces are\nindented.  '-bli2', the default, gives the result shown above.  '-bli0'\nresults in the following:\n\nif (x > 0)\n{\nx--;\n}\n\nIf you are using the '-br' option, you probably want to also use the\n'-ce' option.  This causes the 'else' in an if-then-else construct to\ncuddle up to the immediately preceding '}'.  For example, with '-br -ce'\nyou get the following:\n\nif (x > 0) {\nx--;\n} else {\nfprintf (stderr, \"...something wrong?\\n\");\n}\n\nWith '-br -nce' that code would appear as\n\nif (x > 0) {\nx--;\n}\nelse {\nfprintf (stderr, \"...something wrong?\\n\");\n}\n\nAn exception to the behavior occurs when there is a comment between\nthe right brace and the subsequent else statement.  While the '-br'\noption will cause a left brace to jump over the comment, the else does\nnot jump over the comment to cuddle because it has a strong likelihood\nof changing the meaning of the comment.\n\nThe '-cdw' option causes the 'while' in a do-while loop to cuddle up\nto the immediately preceding '}'.  For example, with '-cdw' you get the\nfollowing:\n\ndo {\nx--;\n} while (x);\n\nWith '-ncdw' that code would appear as\n\ndo {\nx--;\n}\nwhile (x);\n\nThe '-slc' option allows for an unbraced conditional and its inner\nstatement to appear on the same line.  For example:\n\nif (x) x--;\nelse x++;\n\nWithout '-slc' that code would appear as\n\nif (x)\nx--;\nelse\nx++;\n\nThe '-cli' option specifies the number of spaces that case labels\nshould be indented to the right of the containing 'switch' statement.\n\nThe default gives code like:\n\nswitch (i)\n{\ncase 0:\nbreak;\ncase 1:\n{\n++i;\n}\ndefault:\nbreak;\n}\n\nUsing the '-cli2' that would become:\n\nswitch (i)\n{\ncase 0:\nbreak;\ncase 1:\n{\n++i;\n}\ndefault:\nbreak;\n}\n\nThe indentation of the braces below a case statement can be\ncontrolled with the '-cbiN' option.  For example, using '-cli2 -cbi0'\nresults in:\n\nswitch (i)\n{\ncase 0:\nbreak;\ncase 1:\n{\n++i;\n}\ndefault:\nbreak;\n}\n\nIf a semicolon is on the same line as a 'for' or 'while' statement,\nthe '-ss' option will cause a space to be placed before the semicolon.\nThis emphasizes the semicolon, making it clear that the body of the\n'for' or 'while' statement is an empty statement.  '-nss' disables this\nfeature.\n\nThe '-pcs' option causes a space to be placed between the name of the\nprocedure being called and the '(' (for example, 'puts (\"Hi\");'.  The\n'-npcs' option would give 'puts(\"Hi\");').\n\nIf the '-cs' option is specified, 'indent' puts a space between a\ncast operator and the object to be cast.  The '-ncs' ensures that there\nis no space between the cast operator and the object.  Remember that\n'indent' only knows about the standard C data types and so cannot\nrecognise user-defined types in casts.  Thus '(mytype)thing' is not\ntreated as a cast.\n\nThe '-bs' option ensures that there is a space between the keyword\n'sizeof' and its argument.  In some versions, this is known as the\n'BillShannon' option.\n\nThe '-saf' option forces a space between a 'for' and the following\nparenthesis.  This is the default.\n\nThe '-sai' option forces a space between a 'if' and the following\nparenthesis.  This is the default.\n\nThe '-saw' option forces a space between a 'while' and the following\nparenthesis.  This is the default.\n\nThe '-prs' option causes all parentheses to be separated with a space\nfrom whatever is between them.  For example, using '-prs' results in\ncode like:\n\nwhile ( ( ecode - scode ) < ( decind - 1 ) )\n{\nsetbufbreak ( bbdecind );\n*ecode++ = ' ';\n}\n\nFile: indent.info,  Node: Declarations,  Next: Indentation,  Prev: Statements,  Up: Indent Program\n"
                },
                {
                    "name": "1.7 Declarations",
                    "content": "By default 'indent' will line up identifiers, in the column specified by\nthe '-di' option.  For example, '-di16' makes things look like:\n\nint             foo;\nchar           *bar;\n\nUsing a small value (such as one or two) for the '-di' option can be\nused to cause the identifiers to be placed in the first available\nposition; for example:\n\nint foo;\nchar *bar;\n\nThe value given to the '-di' option will still affect variables which\nare put on separate lines from their types, for example '-di2' will lead\nto:\n\nint\nfoo;\n\nIf the '-bc' option is specified, a newline is forced after each\ncomma in a declaration.  For example,\n\nint a,\nb,\nc;\n\nWith the '-nbc' option this would look like\n\nint a, b, c;\n\nThe '-bfda' option causes a newline to be forced after the comma\nseparating the arguments of a function declaration.  The arguments will\nappear at one indention level deeper than the function declaration.\nThis is particularly helpful for functions with long argument lists.\nThe option '-bfde' causes a newline to be forced before the closing\nbracket of the function declaration.  For both options the 'n' setting\nis the default: -nbfda and -nbfde.\n\nFor example,\n\nvoid foo (int arg1, char arg2, int *arg3, long arg4, char arg5);\nWith the '-bfda' option this would look like\n\nvoid foo (\nint arg1,\nchar arg2,\nint *arg3,\nlong arg4,\nchar arg5);\n\nWith, in addition, the '-bfde' option this would look like\n\nvoid foo (\nint arg1,\nchar arg2,\nint *arg3,\nlong arg4,\nchar arg5\n);\n\nThe '-psl' option causes the type of a procedure being defined to be\nplaced on the line before the name of the procedure.  This style is\nrequired for the 'etags' program to work correctly, as well as some of\nthe 'c-mode' functions of Emacs.\n\nYou must use the '-T' option to tell 'indent' the name of all the\ntypenames in your program that are defined by 'typedef'.  '-T' can be\nspecified more than once, and all names specified are used.  For\nexample, if your program contains\n\ntypedef unsigned long CODEADDR;\ntypedef enum {red, blue, green} COLOR;\n\nyou would use the options '-T CODEADDR -T COLOR'.\n\nThe '-brs' or '-bls' option specifies how to format braces in struct\ndeclarations.  The '-brs' option formats braces like this:\n\nstruct foo {\nint x;\n};\n\nThe '-bls' option formats them like this:\n\nstruct foo\n{\nint x;\n};\n\nSimilarly to the structure brace '-brs' and '-bls' options, the\nfunction brace options '-brf' or '-blf' specify how to format the braces\nin function definitions.  The '-brf' option formats braces like this:\n\nint one(void) {\nreturn 1;\n};\n\nThe '-blf' option formats them like this:\n\nint one(void)\n{\nreturn 1;\n};\n\n\nThe '-sar' option affects how 'indent' will render initializer lists.\nWithout '-sar' they are formatted like this:\n\nint a[] = {1, 2, 3, 4};\n\nstruct s {\nconst char *name;\nint x;\n} a[] = {\n{\"name\", 0},\n{\"a\", 1}\n};\n\nWith '-sar' they are formatted like this, with spaces inside the braces:\n\nint a[] = { 1, 2, 3, 4 };\n\nstruct s {\nconst char *name;\nint x;\n} a[] = {\n{ \"name\", 0 },\n{ \"a\", 1 }\n};\n\nFile: indent.info,  Node: Indentation,  Next: Breaking long lines,  Prev: Declarations,  Up: Indent Program\n"
                },
                {
                    "name": "1.8 Indentation",
                    "content": "The most basic, and most controversial issues with regard to code\nformatting is precisely how indentation should be acoomplished.\nFortunately, 'indent' supports several different styles of identation.\nThe default is to use tabs for indentation, which is specified by the\n'-ut' option.  Assuming the default tab size of 8, the code would look\nlike this:\n\nint a(int b)\n{\nreturn b;\n|------|\n1 tab\n}\n\nFor those that prefer spaces to tabs, 'indent' provides the '-nut'\noption.  The same code would look like this:\n\nint a(int b)\n{\nreturn b;\n|------|\n8 spaces\n}\n\nAnother issue in the formatting of code is how far each line should\nbe indented from the left margin.  When the beginning of a statement\nsuch as 'if' or 'for' is encountered, the indentation level is increased\nby the value specified by the '-i' option.  For example, use '-i8' to\nspecify an eight character indentation for each level.  When a statement\nis broken across two lines, the second line is indented by a number of\nadditional spaces specified by the '-ci' option.  '-ci' defaults to 0.\nHowever, if the '-lp' option is specified, and a line has a left\nparenthesis which is not closed on that line, then continuation lines\nwill be lined up to start at the character position just after the left\nparenthesis.  This processing also applies to '[' and applies to '{'\nwhen it occurs in initialization lists.  For example, a piece of\ncontinued code might look like this with '-nlp -ci3' in effect:\n\np1 = firstprocedure (secondprocedure (p2, p3),\nthirdprocedure (p4, p5));\n\nWith '-lp' in effect the code looks somewhat clearer:\n\np1 = firstprocedure (secondprocedure (p2, p3),\nthirdprocedure (p4, p5));\n\nWhen a statement is broken in between two or more paren pairs (...),\neach extra pair causes the indentation level extra indentation:\n\nif ((((i < 2 &&\nk > 0) || p == 0) &&\nq == 1) ||\nn = 0)\n\nThe option '-ipN' can be used to set the extra offset per paren.  For\ninstance, '-ip0' would format the above as:\n\nif ((((i < 2 &&\nk > 0) || p == 0) &&\nq == 1) ||\nn = 0)\n\n'indent' assumes that tabs are placed at regular intervals of both input\nand output character streams.  These intervals are by default 8 columns\nwide, but (as of version 1.2) may be changed by the '-ts' option.  Tabs\nare treated as the equivalent number of spaces.\n\nBy default, 'indent' will use tabs to indent as far as possible, and\nthen pad with spaces until the desired position is reached.  However,\nwith the '-as' option, spaces will be used for alignment beyond the\ncurrent indentation level.  By default, assuming '-lp' is enabled, the\ncode would be indented like so ('t' represents tabs, 's' represents\nspaces):\n\nunsigned long reallylongprocname(unsigned long x, unsigned long y,\nint a)\n|------||-------||------||-------|\nt        t       t       t     ss\n{\np1 = firstprocedure (secondprocedure (p2, p3),\nthirdprocedure (p4, p5));\n|------||------||------|\nt       t       t    sssss\n}\n\nThis is fine, if you assume that whoever is reading the code will honor\nyour assumption of 8-space tabs.  If the reader was using 4-space tabs,\nit would look like this:\n\nunsigned long reallylongprocname(unsigned long x, unsigned long y,\nint a)\n|---||---||---||---|\nt    t    t    t  ss\n{\np1 = firstprocedure (secondprocedure (p2, p3),\nthirdprocedure (p4, p5));\n|---||---||---|\nt    t    t  ssssss\n}\n\nThe '-as' option fixes this so that the code will appear consistent\nregardless of what tab size the user users to read the code.  This looks\nlike:\n\nunsigned long reallylongprocname(unsigned long x, unsigned long y,\nint a)\n\nssssssssssssssssssssssssssssssssssss\n{\np1 = firstprocedure (secondprocedure (p2, p3),\nthirdprocedure (p4, p5));\n|------|\nt    ssssssssssssssssssssss\n}\n\nThe indentation of type declarations in old-style function\ndefinitions is controlled by the '-ip' parameter.  This is a numeric\nparameter specifying how many spaces to indent type declarations.  For\nexample, the default '-ip5' makes definitions look like this:\n\nchar *\ncreateworld (x, y, scale)\nint x;\nint y;\nfloat scale;\n{\n. . .\n}\n\nFor compatibility with other versions of indent, the option '-nip' is\nprovided, which is equivalent to '-ip0'.\n\nANSI C allows white space to be placed on preprocessor command lines\nbetween the character '#' and the command name.  By default, 'indent'\nremoves this space, but specifying the '-lps' option directs 'indent' to\nleave this space unmodified.  The option '-ppi' overrides '-nlps' and\n'-lps'.\n\nThis option can be used to request that preprocessor conditional\nstatements can be indented by to given number of spaces, for example\nwith the option '-ppi 3'\n\n#if X\n#if Y\n#define Z 1\n#else\n#define Z 0\n#endif\n#endif\nbecomes\n#if X\n#   if Y\n#      define Z 1\n#   else\n#      define Z 0\n#   endif\n#endif\n\nThis option sets the offset at which a label (except case labels)\nwill be positioned.  If it is set to zero or a positive number, this\nindicates how far from the left margin to indent a label.  If it is set\nto a negative number, this indicates how far back from the current\nindent level to place the label.  The default setting is -2 which\nmatches the behaviour of earlier versions of indent.  Note that this\nparameter does not affect the placing of case labels; see the '-cli'\nparameter for that.  For example with the option '-il 1'\n\nfunction()\n{\nif (dostuff1() == ERROR)\ngoto cleanup1;\n\nif (dostuff2() == ERROR)\ngoto cleanup2;\n\nreturn SUCCESS;\n\ncleanup2:\ndocleanup2();\n\ncleanup1:\ndocleanup1();\n\nreturn ERROR;\n}\nbecomes\nfunction()\n{\nif (dostuff1() == ERROR)\ngoto cleanup1;\n\nif (dostuff2() == ERROR)\ngoto cleanup2;\n\nreturn SUCCESS;\n\ncleanup2:\ndocleanup2();\n\ncleanup1:\ndocleanup1();\n\nreturn ERROR;\n}\n\nFile: indent.info,  Node: Breaking long lines,  Next: Disabling Formatting,  Prev: Indentation,  Up: Indent Program\n"
                },
                {
                    "name": "1.9 Breaking long lines",
                    "content": "With the option '-lN', or '--line-lengthN', it is possible to specify\nthe maximum length of a line of C code, not including possible comments\nthat follow it.\n\nWhen lines become longer than the specified line length, GNU 'indent'\ntries to break the line at a logical place.  This is new as of version\n2.1 however and not very intelligent or flexible yet.\n\nCurrently there are three options that allow one to interfere with\nthe algorithm that determines where to break a line.\n\nThe '-bbo' option causes GNU 'indent' to prefer to break long lines\nbefore the boolean operators '&&' and '||'.  The '-nbbo' option causes\nGNU 'indent' not have that preference.  For example, the default option\n'-bbo' (together with '--line-length60' and '--ignore-newlines') makes\ncode look like this:\n\nif (mask\n&& ((mask[0] == '\\0')\n|| (mask[1] == '\\0'\n&& ((mask[0] == '0') || (mask[0] == '*')))))\n\nUsing the option '-nbbo' will make it look like this:\n\nif (mask &&\n((mask[0] == '\\0') ||\n(mask[1] == '\\0' &&\n((mask[0] == '0') || (mask[0] == '*')))))\n\nThe default '-hnl', however, honours newlines in the input file by\ngiving them the highest possible priority to break lines at.  For\nexample, when the input file looks like this:\n\nif (mask\n&& ((mask[0] == '\\0')\n|| (mask[1] == '\\0' && ((mask[0] == '0') || (mask[0] == '*')))))\n\nthen using the option '-hnl', or '--honour-newlines', together with the\npreviously mentioned '-nbbo' and '--line-length60', will cause the\noutput not to be what is given in the last example but instead will\nprefer to break at the positions where the code was broken in the input\nfile:\n\nif (mask\n&& ((mask[0] == '\\0')\n|| (mask[1] == '\\0' &&\n((mask[0] == '0') || (mask[0] == '*')))))\n\nThe idea behind this option is that lines which are too long, but are\nalready broken up, will not be touched by GNU 'indent'.  Really messy\ncode should be run through 'indent' at least once using the\n'--ignore-newlines' option though.\n\nThe '-gts' option affects how the gettext standard macros '()' and\n'N()' are treated.  The default behavior (or the use of '-ngts') causes\nindent to treat them as it does other functions, so that a long string\nis broken like the following example.\n\nif (mask)\n{\nwarning (\n(\"This is a long string that stays together.\"));\n}\n\nWith the '-gts' option, the underscore is treated as a part of the\nstring, keeping it tied to the string, and respecting the fact that\ngettext is unobtrusively providing a localized string.  This only works\nif '(\"' is together as a unit at the beginning of the string and '\")'\nis together as a unit at the end.\n\nif (mask)\n{\nwarning\n((\"This is a long string that stays together.\"));\n}\n\nFile: indent.info,  Node: Disabling Formatting,  Next: Miscellaneous options,  Prev: Breaking long lines,  Up: Indent Program\n"
                },
                {
                    "name": "1.10 Disabling Formatting",
                    "content": "Formatting of C code may be disabled for portions of a program by\nembedding special \"control comments\" in the program.  To turn off\nformatting for a section of a program, place the disabling control\ncomment '/* *INDENT-OFF* */' on a line by itself just before that\nsection.  Program text scanned after this control comment is output\nprecisely as input with no modifications until the corresponding\nenabling comment is scanned on a line by itself.  The enabling control\ncomment is '/* *INDENT-ON* */', and any text following the comment on\nthe line is also output unformatted.  Formatting begins again with the\ninput line following the enabling control comment.\n\nMore precisely, 'indent' does not attempt to verify the closing\ndelimiter ('*/') for these C comments, and any whitespace on the line is\ntotally transparent.\n\nThese control comments also function in their C++ formats, namely '//\n*INDENT-OFF*' and '// *INDENT-ON*'.\n\nIt should be noted that the internal state of 'indent' remains\nunchanged over the course of the unformatted section.  Thus, for\nexample, turning off formatting in the middle of a function and\ncontinuing it after the end of the function may lead to bizarre results.\nIt is therefore wise to be somewhat modular in selecting code to be left\nunformatted.\n\nAs a historical note, some earlier versions of 'indent' produced\nerror messages beginning with '*INDENT'.  These versions of 'indent'\nwere written to ignore any input text lines which began with such error\nmessages.  I have removed this incestuous feature from GNU 'indent'.\n\nFile: indent.info,  Node: Miscellaneous options,  Next: Bugs,  Prev: Disabling Formatting,  Up: Indent Program\n"
                },
                {
                    "name": "1.11 Miscellaneous options",
                    "content": "To find out what version of 'indent' you have, use the command 'indent\n-version'.  This will report the version number of 'indent', without\ndoing any of the normal processing.\n\nThe '-v' option can be used to turn on verbose mode.  When in verbose\nmode, 'indent' reports when it splits one line of input into two more\nmore lines of output, and gives some size statistics at completion.\n\nThe '-pmt' option causes 'indent' to preserve the access and\nmodification times on the output files.  Using this option has the\nadvantage that running indent on all source and header files in a\nproject won't cause 'make' to rebuild all targets.  This option is only\navailable on Operating Systems that have the POSIX 'utime(2)' function.\n\nFile: indent.info,  Node: Bugs,  Next: Copyright,  Prev: Miscellaneous options,  Up: Indent Program\n"
                },
                {
                    "name": "1.12 Bugs",
                    "content": "Please report any bugs to <bug-indent@gnu.org>.\n\nWhen 'indent' is run twice on a file, with the same profile, it\nshould never change that file the second time.  With the current\ndesign of 'indent', this can not be guaranteed, and it has not been\nextensively tested.\n\n'indent' does not understand C. In some cases this leads to the\ninability to join lines.  The result is that running a file through\n'indent' is irreversible, even if the used input file was the result\nof running 'indent' with a given profile ('.indent.pro').\n\nWhile an attempt was made to get 'indent' working for C++, it will\nnot do a good job on any C++ source except the very simplest.\n\n'indent' does not look at the given '--line-length' option when\nwriting comments to the output file.  This results often in comments\nbeing put far to the right.  In order to prohibit 'indent' from joining\na broken line that has a comment at the end, make sure that the comments\nstart on the first line of the break.\n\n'indent' does not count lines and comments (see the '-v' option) when\n'indent' is turned off with '/* *INDENT-OFF* */'.\n\nComments of the form '/*UPPERCASE*/' are not treated as comment but\nas an identifier, causing them to be joined with the next line.  This\nrenders comments of this type useless, unless they are embedded in the\ncode to begin with.\n\nFile: indent.info,  Node: Copyright,  Prev: Bugs,  Up: Indent Program\n"
                },
                {
                    "name": "1.13 Copyright",
                    "content": "The following copyright notice applies to the 'indent' program.  The\ncopyright and copying permissions for this manual appear near the\nbeginning of 'indent.texinfo' and 'indent.info', and near the end of\n'indent.1'.\n\nCopyright (C) 2015 Tim Hentenaar.\nCopyright (C) 2001 David Ingamells.\nCopyright (C) 1999 Carlo Wood.\nCopyright (C) 1995, 1996 Joseph Arceneaux.\nCopyright (C) 1989, 1992, 1993, 1994, 1995, 1996, 2014 Free Software Foundation\nCopyright (C) 1985 Sun Microsystems, Inc.\nCopyright (C) 1980 The Regents of the University of California.\nCopyright (C) 1976 Board of Trustees of the University of Illinois.\nAll rights reserved.\n\nRedistribution and use in source and binary forms are permitted\nprovided that the above copyright notice and this paragraph are\nduplicated in all such forms and that any documentation,\nadvertising materials, and other materials related to such\ndistribution and use acknowledge that the software was developed\nby the University of California, Berkeley, the University of Illinois,\nUrbana, and Sun Microsystems, Inc.  The name of either University\nor Sun Microsystems may not be used to endorse or promote products\nderived from this software without specific prior written permission.\nTHIS SOFTWARE IS PROVIDED \"AS IS\" AND WITHOUT ANY EXPRESS OR\nIMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED\nWARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR\nPURPOSE.\n\nFile: indent.info,  Node: Option Summary,  Next: Index,  Prev: Indent Program,  Up: Top\n"
                }
            ]
        },
        "Appendix A Option Summary": {
            "content": "Here is a list of all the options for 'indent', alphabetized by short\noption.  It is followed by a cross key alphabetized by long option.\n\n'-as'\n'--align-with-spaces'\nIf using tabs for indentation, use spaces for alignment.\n*Note Indentation::.\n\n'-bad'\n'--blank-lines-after-declarations'\nForce blank lines after the declarations.\n*Note Blank lines::.\n\n'-bap'\n'--blank-lines-after-procedures'\nForce blank lines after procedure bodies.\n*Note Blank lines::.\n\n'-bbb'\n'--blank-lines-before-block-comments'\nForce blank lines before block comments.\n*Note Blank lines::.\n\n'-bbo'\n'--break-before-boolean-operator'\nPrefer to break long lines before boolean operators.\n*Note Breaking long lines::.\n\n'-bc'\n'--blank-lines-after-commas'\nForce newline after comma in declaration.\n*Note Declarations::.\n\n'-bl'\n'--braces-after-if-line'\nPut braces on line after 'if', etc.\n*Note Statements::.\n\n'-blf'\n'--braces-after-func-def-line'\nPut braces on line following function definition line.\n*Note Declarations::.\n\n'-bliN'\n'--brace-indentN'\nIndent braces N spaces.\n*Note Statements::.\n\n'-bls'\n'--braces-after-struct-decl-line'\nPut braces on the line after 'struct' declaration lines.\n*Note Declarations::.\n\n'-br'\n'--braces-on-if-line'\nPut braces on line with 'if', etc.\n*Note Statements::.\n\n'-brf'\n'--braces-on-func-def-line'\nPut braces on function definition line.\n*Note Declarations::.\n\n'-brs'\n'--braces-on-struct-decl-line'\nPut braces on 'struct' declaration line.\n*Note Declarations::.\n\n'-bs'\n'--Bill-Shannon'\n'--blank-before-sizeof'\nPut a space between 'sizeof' and its argument.\n*Note Statements::.\n\n'-cN'\n'--comment-indentationN'\nPut comments to the right of code in column N.\n*Note Comments::.\n\n'-cbiN'\n'--case-brace-indentationN'\nIndent braces after a case label N spaces.\n*Note Statements::.\n\n'-cdN'\n'--declaration-comment-columnN'\nPut comments to the right of the declarations in column N.\n*Note Comments::.\n\n'-cdb'\n'--comment-delimiters-on-blank-lines'\nPut comment delimiters on blank lines.\n*Note Comments::.\n\n'-cdw'\n'--cuddle-do-while'\nCuddle while of 'do {} while;' and preceding '}'.\n*Note Comments::.\n\n'-ce'\n'--cuddle-else'\nCuddle else and preceding '}'.\n*Note Comments::.\n\n'-ciN'\n'--continuation-indentationN'\nContinuation indent of N spaces.\n*Note Statements::.\n\n'-cliN'\n'--case-indentationN'\nCase label indent of N spaces.\n*Note Statements::.\n\n'-cpN'\n'--else-endif-columnN'\nPut comments to the right of '#else' and '#endif' statements in\ncolumn N.\n*Note Comments::.\n\n'-cs'\n'--space-after-cast'\nPut a space after a cast operator.\n*Note Statements::.\n\n'-dN'\n'--line-comments-indentationN'\nSet indentation of comments not to the right of code to N spaces.\n*Note Comments::.\n\n'-bfda'\n'--break-function-decl-args'\nBreak the line before all arguments in a declaration.\n*Note Declarations::.\n\n'-bfde'\n'--break-function-decl-args-end'\nBreak the line after the last argument in a declaration.\n*Note Declarations::.\n\n'-dj'\n'--left-justify-declarations'\nIf -cd 0 is used then comments after declarations are left\njustified behind the declaration.\n*Note Declarations::.\n\n'-diN'\n'--declaration-indentationN'\nPut variables in column N.\n*Note Declarations::.\n\n'-fc1'\n'--format-first-column-comments'\nFormat comments in the first column.\n*Note Comments::.\n\n'-fca'\n'--format-all-comments'\nDo not disable all formatting of comments.\n*Note Comments::.\n\n'-fnc'\n'--fix-nested-comments'\nFix nested comments.\n*Note Comments::.\n\n'-gnu'\n'--gnu-style'\nUse GNU coding style.  This is the default.\n*Note Common styles::.\n\n'-gts'\n'--gettext-strings'\nTreat gettext '(\"...\")' and 'N(\"...\")' as strings rather than as\nfunctions.\n*Note Breaking long lines::.\n\n'-hnl'\n'--honour-newlines'\nPrefer to break long lines at the position of newlines in the\ninput.\n*Note Breaking long lines::.\n\n'-iN'\n'--indent-levelN'\nSet indentation level to N spaces.\n*Note Indentation::.\n\n'-ilN'\n'--indent-labelN'\nSet offset for labels to column N.\n*Note Indentation::.\n\n'-ipN'\n'--parameter-indentationN'\nIndent parameter types in old-style function definitions by N\nspaces.\n*Note Indentation::.\n\n'-kr'\n'--k-and-r-style'\nUse Kernighan & Ritchie coding style.\n*Note Common styles::.\n\n'-lN'\n'--line-lengthN'\nSet maximum line length for non-comment lines to N.\n*Note Breaking long lines::.\n\n'-lcN'\n'--comment-line-lengthN'\nSet maximum line length for comment formatting to N.\n*Note Comments::.\n\n'-linux'\n'--linux-style'\nUse Linux coding style.\n*Note Common styles::.\n\n'-lp'\n'--continue-at-parentheses'\nLine up continued lines at parentheses.\n*Note Indentation::.\n\n'-lps'\n'--leave-preprocessor-space'\nLeave space between '#' and preprocessor directive.\n*Note Indentation::.\n\n'-nbad'\n'--no-blank-lines-after-declarations'\nDo not force blank lines after declarations.\n*Note Blank lines::.\n\n'-nbap'\n'--no-blank-lines-after-procedures'\nDo not force blank lines after procedure bodies.\n*Note Blank lines::.\n\n'-nbbo'\n'--break-after-boolean-operator'\nDo not prefer to break long lines before boolean operators.\n*Note Breaking long lines::.\n\n'-nbc'\n'--no-blank-lines-after-commas'\nDo not force newlines after commas in declarations.\n*Note Declarations::.\n\n'-nbfda'\n'--dont-break-function-decl-args'\nDon't put each argument in a function declaration on a separate\nline.\n*Note Declarations::.\n\n'-ncdb'\n'--no-comment-delimiters-on-blank-lines'\nDo not put comment delimiters on blank lines.\n*Note Comments::.\n\n'-ncdw'\n'--dont-cuddle-do-while'\nDo not cuddle '}' and the 'while' of a 'do {} while;'.\n*Note Statements::.\n\n'-nce'\n'--dont-cuddle-else'\nDo not cuddle '}' and 'else'.\n*Note Statements::.\n\n'-ncs'\n'--no-space-after-casts'\nDo not put a space after cast operators.\n*Note Statements::.\n\n'-ndjN'\n'--dont-left-justify-declarations'\nComments after declarations are treated the same as comments after\nother statements.\n*Note Declarations::.\n\n'-nfc1'\n'--dont-format-first-column-comments'\nDo not format comments in the first column as normal.\n*Note Comments::.\n\n'-nfca'\n'--dont-format-comments'\nDo not format any comments.\n*Note Comments::.\n\n'-ngts'\n'--no-gettext-strings'\nTreat gettext '(\"...\")' and 'N(\"...\")' as normal functions.  This\nis the default.\n*Note Breaking long lines::.\n\n'-nhnl'\n'--ignore-newlines'\nDo not prefer to break long lines at the position of newlines in\nthe input.\n*Note Breaking long lines::.\n\n'-nip'\n'--no-parameter-indentation'\nZero width indentation for parameters.\n*Note Indentation::.\n\n'-nlp'\n'--dont-line-up-parentheses'\nDo not line up parentheses.\n*Note Statements::.\n\n'-npcs'\n'--no-space-after-function-call-names'\nDo not put space after the function in function calls.\n*Note Statements::.\n\n'-nprs'\n'--no-space-after-parentheses'\nDo not put a space after every '(' and before every ')'.\n*Note Statements::.\n\n'-npsl'\n'--dont-break-procedure-type'\nPut the type of a procedure on the same line as its name.\n*Note Declarations::.\n\n'-nsaf'\n'--no-space-after-for'\nDo not put a space after every 'for'.\n*Note Statements::.\n\n'-nsai'\n'--no-space-after-if'\nDo not put a space after every 'if'.\n*Note Statements::.\n\n'-nsaw'\n'--no-space-after-while'\nDo not put a space after every 'while'.\n*Note Statements::.\n\n'-nsc'\n'--dont-star-comments'\nDo not put the '*' character at the left of comments.\n*Note Comments::.\n\n'-nsob'\n'--leave-optional-blank-lines'\nDo not swallow optional blank lines.\n*Note Blank lines::.\n\n'-nss'\n'--dont-space-special-semicolon'\nDo not force a space before the semicolon after certain statements.\nDisables '-ss'.\n*Note Statements::.\n\n'-ntac'\n'--dont-tab-align-comments'\nDo not pad comments out to the nearest tabstop.\n*Note Comments::.\n\n'-nut'\n'--no-tabs'\nUse spaces instead of tabs.\n*Note Indentation::.\n\n'-nv'\n'--no-verbosity'\nDisable verbose mode.\n*Note Miscellaneous options::.\n\n'-orig'\n'--original'\nUse the original Berkeley coding style.\n*Note Common styles::.\n\n'-npro'\n'--ignore-profile'\nDo not read '.indent.pro' files.\n*Note Invoking indent::.\n\n'-pal'\n'--pointer-align-left'\nPut asterisks in pointer declarations on the left of spaces, next\nto types: \"char* p\".\n\n'-par'\n'--pointer-align-right'\nPut asterisks in pointer declarations on the right of spaces, next\nto variable names: \"char *p\".  This is the default behavior.\n\n'-pcs'\n'--space-after-procedure-calls'\nInsert a space between the name of the procedure being called and\nthe '('.\n*Note Statements::.\n\n'-piN'\n'--paren-indentationN'\nSpecify the extra indentation per open parentheses '(' when a\nstatement is broken.  *Note Statements::.\n\n'-pmt'\n'--preserve-mtime'\nPreserve access and modification times on output files.  *Note\nMiscellaneous options::.\n\n'-ppiN'\n'--preprocessor-indentationN'\nSpecify the indentation for preprocessor conditional statements.\n*Note Indentation::.\n\n'-prs'\n'--space-after-parentheses'\nPut a space after every '(' and before every ')'.\n*Note Statements::.\n\n'-psl'\n'--procnames-start-lines'\nPut the type of a procedure on the line before its name.\n*Note Declarations::.\n\n'-saf'\n'--space-after-for'\nPut a space after each 'for'.\n*Note Statements::.\n\n'-sai'\n'--space-after-if'\nPut a space after each 'if'.\n*Note Statements::.\n\n'-sar'\n'--spaces-around-initializers'\nPut a space after the '{' and before the '}' in initializers.\n*Note Declarations::.\n\n'-saw'\n'--space-after-while'\nPut a space after each 'while'.\n*Note Statements::.\n\n'-sbiN'\n'--struct-brace-indentationN'\nIndent braces of a struct, union or enum N spaces.\n*Note Statements::.\n\n'-sc'\n'--start-left-side-of-comments'\nPut the '*' character at the left of comments.\n*Note Comments::.\n\n'-slc'\n'--single-line-conditionals'\nAllow for unbraced conditionals ('if', 'else', etc.)  to have their\ninner statement on the same line.\n*Note Statements::.\n\n'-sob'\n'--swallow-optional-blank-lines'\nSwallow optional blank lines.\n*Note Blank lines::.\n\n'-ss'\n'--space-special-semicolon'\nOn one-line 'for' and 'while' statements, force a blank before the\nsemicolon.\n*Note Statements::.\n\n'-st'\n'--standard-output'\nWrite to standard output.\n*Note Invoking indent::.\n\n'-T'\nTell 'indent' the name of typenames.\n*Note Declarations::.\n\n'-tsN'\n'--tab-sizeN'\nSet tab size to N spaces.\n*Note Indentation::.\n\n'-ut'\n'--use-tabs'\nUse tabs.  This is the default.\n*Note Indentation::.\n\n'-v'\n'--verbose'\nEnable verbose mode.\n*Note Miscellaneous options::.\n\n'-version'\nOutput the version number of 'indent'.\n*Note Miscellaneous options::.\n\n\nHere is a list of options alphabetized by long option, to help you find\nthe corresponding short option.\n\n--align-with-spaces                             -as\n--blank-lines-after-commas                      -bc\n--blank-lines-after-declarations                -bad\n--blank-lines-after-procedures                  -bap\n--blank-lines-before-block-comments             -bbb\n--braces-after-if-line                          -bl\n--braces-after-func-def-line                    -blf\n--brace-indent                                  -bli\n--braces-after-struct-decl-line                 -bls\n--braces-on-if-line                             -br\n--braces-on-func-def-line                       -brf\n--braces-on-struct-decl-line                    -brs\n--break-after-boolean-operator                  -nbbo\n--break-before-boolean-operator                 -bbo\n--break-function-decl-args                      -bfda\n--break-function-decl-args-end                  -bfde\n--case-indentation                              -cliN\n--case-brace-indentation                        -cbiN\n--comment-delimiters-on-blank-lines             -cdb\n--comment-indentation                           -cN\n--continuation-indentation                      -ciN\n--continue-at-parentheses                       -lp\n--cuddle-do-while                               -cdw\n--cuddle-else                                   -ce\n--declaration-comment-column                    -cdN\n--declaration-indentation                       -diN\n--dont-break-function-decl-args                 -nbfda\n--dont-break-function-decl-args-end             -nbfde\n--dont-break-procedure-type                     -npsl\n--dont-cuddle-do-while                          -ncdw\n--dont-cuddle-else                              -nce\n--dont-format-comments                          -nfca\n--dont-format-first-column-comments             -nfc1\n--dont-line-up-parentheses                      -nlp\n--dont-left-justify-declarations                -ndj\n--dont-space-special-semicolon                  -nss\n--dont-star-comments                            -nsc\n--dont-tab-align-comments                       -ntac\n--else-endif-column                             -cpN\n--format-all-comments                           -fca\n--format-first-column-comments                  -fc1\n--gnu-style                                     -gnu\n--honour-newlines                               -hnl\n--ignore-newlines                               -nhnl\n--ignore-profile                                -npro\n--indent-label                                  -ilN\n--indent-level                                  -iN\n--k-and-r-style                                 -kr\n--leave-optional-blank-lines                    -nsob\n--leave-preprocessor-space                      -lps\n--left-justify-declarations                     -dj\n--line-comments-indentation                     -dN\n--line-length                                   -lN\n--linux-style                                   -linux\n--no-blank-lines-after-commas                   -nbc\n--no-blank-lines-after-declarations             -nbad\n--no-blank-lines-after-procedures               -nbap\n--no-blank-lines-before-block-comments          -nbbb\n--no-comment-delimiters-on-blank-lines          -ncdb\n--no-space-after-casts                          -ncs\n--no-parameter-indentation                      -nip\n--no-space-after-for\t\t\t\t-nsaf\n--no-space-after-function-call-names            -npcs\n--no-space-after-if\t\t\t\t-nsai\n--no-space-after-parentheses                    -nprs\n--no-space-after-while\t\t\t\t-nsaw\n--no-tabs                                       -nut\n--no-verbosity                                  -nv\n--original                                      -orig\n--parameter-indentation                         -ipN\n--paren-indentation                             -piN\n--preserve-mtime\t\t\t\t-pmt\n--preprocessor-indentation                      -ppiN\n--procnames-start-lines                         -psl\n--single-line-conditionals                      -slc\n--space-after-cast                              -cs\n--space-after-for\t\t\t\t-saf\n--space-after-if\t\t\t\t-sai\n--space-after-parentheses                       -prs\n--space-after-procedure-calls                   -pcs\n--space-after-while\t\t\t\t-saw\n--space-special-semicolon                       -ss\n--spaces-around-initializers                    -sar\n--standard-output                               -st\n--start-left-side-of-comments                   -sc\n--struct-brace-indentation                      -sbiN\n--swallow-optional-blank-lines                  -sob\n--tab-size                                      -tsN\n--use-tabs                                      -ut\n--verbose                                       -v\n\nFile: indent.info,  Node: Index,  Prev: Option Summary,  Up: Top\n",
            "subsections": []
        },
        "Index": {
            "content": "* Menu:\n\n* --align-with-spaces:                   Indentation.         (line  73)\n* --blank-after-sizeof:                  Statements.          (line 149)\n* --blank-lines-after-commas:            Declarations.        (line  26)\n* --blank-lines-after-declarations:      -bad.                (line  15)\n* --blank-lines-after-procedures:        -bap.                (line   6)\n* --blank-lines-before-block-comments:   Blank lines.         (line  17)\n* --brace-indentN:                       Statements.          (line  21)\n* --braces-after-func-def-line:          Declarations.        (line  96)\n* --braces-after-if-line:                Statements.          (line   6)\n* --braces-after-struct-decl-line:       Declarations.        (line  82)\n* --braces-on-func-def-line:             Declarations.        (line  96)\n* --braces-on-if-line:                   Statements.          (line   6)\n* --braces-on-struct-decl-line:          Declarations.        (line  82)\n* --break-after-boolean-operator:        Breaking long lines. (line  14)\n* --break-before-boolean-operator:       Breaking long lines. (line  14)\n* --break-function-decl-args:            Declarations.        (line  37)\n* --break-function-decl-args-end:        Declarations.        (line  37)\n* --case-brace-indentationN:             Statements.          (line 116)\n* --case-indentationN:                   Statements.          (line  85)\n* --comment-delimiters-on-blank-lines:   Comments.            (line  99)\n* --comment-indentationN:                Comments.            (line  82)\n* --continuation-indentationN:           Indentation.         (line  30)\n* --continue-at-parentheses:             Indentation.         (line  30)\n* --cuddle-do-while:                     Statements.          (line  57)\n* --cuddle-else:                         Statements.          (line  31)\n* --declaration-comment-columnN:         Comments.            (line  82)\n* --declaration-indentationN:            Declarations.        (line   6)\n* --dont-break-function-decl-args:       Declarations.        (line  37)\n* --dont-break-function-decl-args-end:   Declarations.        (line  37)\n* --dont-break-procedure-type:           Declarations.        (line  67)\n* --dont-cuddle-do-while:                Statements.          (line  57)\n* --dont-cuddle-else:                    Statements.          (line  31)\n* --dont-format-comments:                Comments.            (line  53)\n* --dont-format-first-column-comments:   Comments.            (line  53)\n* --dont-left-justify-declarations:      Comments.            (line  82)\n* --dont-line-up-parentheses:            Indentation.         (line  30)\n* --dont-space-special-semicolon:        Statements.          (line 132)\n* --dont-star-comments:                  Comments.            (line 107)\n* --dont-tab-align-comments:             Comments.            (line  82)\n* --else-endif-columnN:                  Comments.            (line  82)\n* --fix-nested-comments:                 Comments.            (line  67)\n* --format-all-comments:                 Comments.            (line  53)\n* --format-first-column-comments:        Comments.            (line  53)\n* --gettext-strings:                     Breaking long lines. (line  14)\n* --gettext-strings <1>:                 Breaking long lines. (line  14)\n* --gnu-style:                           Common styles.       (line  12)\n* --honour-newlines:                     Breaking long lines. (line  14)\n* --ignore-newlines:                     Breaking long lines. (line  14)\n* --ignore-profile:                      Invoking indent.     (line  70)\n* --indent-labelN:                       Indentation.         (line 164)\n* --indent-levelN:                       Indentation.         (line  30)\n* --k-and-r-style:                       Common styles.       (line  28)\n* --leave-optional-blank-lines:          Blank lines.         (line  20)\n* --leave-preprocessor-space:            Indentation.         (line 138)\n* --left-justify-declarations:           Comments.            (line  82)\n* --line-comments-indentationN:          Comments.            (line  71)\n* --line-lengthN:                        Breaking long lines. (line   6)\n* --linux-style:                         Common styles.       (line  50)\n* --no-blank-lines-after-commas:         Declarations.        (line  26)\n* --no-blank-lines-after-declarations:   -bad.                (line  15)\n* --no-blank-lines-after-procedures:     -bap.                (line   6)\n* --no-blank-lines-before-block-comments: Blank lines.        (line  17)\n* --no-comment-delimiters-on-blank-lines: Comments.           (line  99)\n* --no-parameter-indentation:            Indentation.         (line 121)\n* --no-space-after-cast:                 Statements.          (line 142)\n* --no-space-after-for:                  Statements.          (line 153)\n* --no-space-after-function-call-names:  Statements.          (line 138)\n* --no-space-after-if:                   Statements.          (line 156)\n* --no-space-after-while:                Statements.          (line 159)\n* --no-tabs:                             Declarations.        (line 136)\n* --no-tabs <1>:                         Indentation.         (line  23)\n* --no-verbosity:                        Miscellaneous options.\n(line  10)\n* --original:                            Common styles.       (line  42)\n* --output-file:                         Invoking indent.     (line  22)\n* --parameter-indentationN:              Indentation.         (line 121)\n* --preprocessor-indentationN:           Indentation.         (line 144)\n* --preserve-mtime:                      Miscellaneous options.\n(line  14)\n* --procnames-start-lines:               Declarations.        (line  67)\n* --remove-preprocessor-space:           Indentation.         (line 138)\n* --single-line-conditionals:            Statements.          (line  72)\n* --space-after-cast:                    Statements.          (line 142)\n* --space-after-for:                     Statements.          (line 153)\n* --space-after-if:                      Statements.          (line 156)\n* --space-after-parentheses:             Statements.          (line 162)\n* --space-after-procedure-calls:         Statements.          (line 138)\n* --space-after-while:                   Statements.          (line 159)\n* --space-special-semicolon:             Statements.          (line 132)\n* --spaces-around-initializers:          Declarations.        (line 111)\n* --standard-output:                     Invoking indent.     (line  26)\n* --star-left-side-of-comments:          Comments.            (line 107)\n* --swallow-optional-blank-lines:        Blank lines.         (line  20)\n* --tab-sizeN:                           Indentation.         (line  52)\n* --use-tabs:                            Declarations.        (line 137)\n* --verbose:                             Miscellaneous options.\n(line  10)\n* -as:                                   Indentation.         (line  73)\n* -bad:                                  -bad.                (line  15)\n* -bap:                                  -bap.                (line   6)\n* -bbb:                                  Blank lines.         (line  17)\n* -bbo:                                  Breaking long lines. (line  14)\n* -bc:                                   Declarations.        (line  26)\n* -bfda:                                 Declarations.        (line  37)\n* -bfde:                                 Declarations.        (line  37)\n* -bl:                                   Statements.          (line   6)\n* -blf:                                  Declarations.        (line  96)\n* -bliN:                                 Statements.          (line  21)\n* -bls:                                  Declarations.        (line  82)\n* -br:                                   Statements.          (line   6)\n* -brs:                                  Declarations.        (line  82)\n* -brs <1>:                              Declarations.        (line  96)\n* -bs:                                   Statements.          (line 149)\n* -cbiN:                                 Statements.          (line 116)\n* -cdb:                                  Comments.            (line  99)\n* -cdN:                                  Comments.            (line  82)\n* -cdw:                                  Statements.          (line  57)\n* -ce:                                   Statements.          (line  31)\n* -ciN:                                  Indentation.         (line  30)\n* -cliN:                                 Statements.          (line  85)\n* -cN:                                   Comments.            (line  82)\n* -cpN:                                  Comments.            (line  82)\n* -cs:                                   Statements.          (line 142)\n* -dce:                                  Statements.          (line  31)\n* -diN:                                  Declarations.        (line   6)\n* -dj:                                   Comments.            (line  82)\n* -dN:                                   Comments.            (line  71)\n* -fc1:                                  Comments.            (line  53)\n* -fca:                                  Comments.            (line  53)\n* -fnc:                                  Comments.            (line  67)\n* -gnu:                                  Common styles.       (line  12)\n* -gts:                                  Breaking long lines. (line  14)\n* -hnl:                                  Breaking long lines. (line  14)\n* -ilN:                                  Indentation.         (line 164)\n* -iN:                                   Indentation.         (line  30)\n* -ipN:                                  Indentation.         (line 121)\n* -kr:                                   Common styles.       (line  28)\n* -linux:                                Common styles.       (line  50)\n* -lN:                                   Breaking long lines. (line   6)\n* -lp:                                   Indentation.         (line  30)\n* -lps:                                  Indentation.         (line 138)\n* -nbad:                                 -bad.                (line  15)\n* -nbap:                                 -bap.                (line   6)\n* -nbbb:                                 Blank lines.         (line  17)\n* -nbbo:                                 Breaking long lines. (line  14)\n* -nbc:                                  Declarations.        (line  26)\n* -nbfda:                                Declarations.        (line  37)\n* -nbfde:                                Declarations.        (line  37)\n* -ncdb:                                 Comments.            (line  99)\n* -ncdw:                                 Statements.          (line  57)\n* -ncs:                                  Statements.          (line 142)\n* -ndj:                                  Comments.            (line  82)\n* -nfc1:                                 Comments.            (line  53)\n* -nfca:                                 Comments.            (line  53)\n* -ngts:                                 Breaking long lines. (line  14)\n* -nhnl:                                 Breaking long lines. (line  14)\n* -nip:                                  Indentation.         (line 121)\n* -nlp:                                  Indentation.         (line  30)\n* -nlps:                                 Indentation.         (line 138)\n* -npcs:                                 Statements.          (line 138)\n* -npmt:                                 Miscellaneous options.\n(line  14)\n* -npro:                                 Invoking indent.     (line  70)\n* -npsl:                                 Declarations.        (line  67)\n* -nsaf:                                 Statements.          (line 153)\n* -nsai:                                 Statements.          (line 156)\n* -nsaw:                                 Statements.          (line 159)\n* -nsc:                                  Comments.            (line 107)\n* -nsob:                                 Blank lines.         (line  20)\n* -nss:                                  Statements.          (line 132)\n* -ntac:                                 Comments.            (line  82)\n* -nut:                                  Declarations.        (line 137)\n* -nut <1>:                              Indentation.         (line  23)\n* -nv:                                   Miscellaneous options.\n(line  10)\n* -o:                                    Invoking indent.     (line  22)\n* -orig:                                 Common styles.       (line  42)\n* -pcs:                                  Statements.          (line 138)\n* -pmt:                                  Miscellaneous options.\n(line  14)\n* -ppiN:                                 Indentation.         (line 144)\n* -prs:                                  Statements.          (line 162)\n* -psl:                                  Declarations.        (line  67)\n* -saf:                                  Statements.          (line 153)\n* -sai:                                  Statements.          (line 156)\n* -sar:                                  Declarations.        (line 111)\n* -saw:                                  Statements.          (line 159)\n* -sc:                                   Comments.            (line 107)\n* -slc:                                  Statements.          (line  72)\n* -sob:                                  Blank lines.         (line  20)\n* -ss:                                   Statements.          (line 132)\n* -st:                                   Invoking indent.     (line  26)\n* -T:                                    Declarations.        (line  72)\n* -tsN:                                  Indentation.         (line  52)\n* -ut:                                   Declarations.        (line 137)\n* -v:                                    Miscellaneous options.\n(line  10)\n* -version:                              Miscellaneous options.\n(line   6)\n* .indent.pro file:                      Invoking indent.     (line  70)\n* backup files:                          Backup files.        (line   6)\n* Beginning indent:                      Invoking indent.     (line   6)\n* Berkeley style:                        Common styles.       (line  42)\n* Blank lines:                           Blank lines.         (line   6)\n* Comments:                              Comments.            (line   6)\n* etags requires -psl:                   Declarations.        (line  67)\n* GNU style:                             Common styles.       (line  12)\n* Initialization file:                   Invoking indent.     (line  70)\n* Invoking indent:                       Invoking indent.     (line   6)\n* Kernighan & Ritchie style:             Common styles.       (line  28)\n* Linux style:                           Common styles.       (line  50)\n* Long options, use of:                  Invoking indent.     (line  45)\n* Original Berkeley style:               Common styles.       (line  42)\n* Output File Specification:             Invoking indent.     (line  22)\n* Standard Output:                       Invoking indent.     (line  26)\n* Starting indent:                       Invoking indent.     (line   6)\n* typedef:                               Declarations.        (line  72)\n* Typenames:                             Declarations.        (line  72)\n* Using Standard Input:                  Invoking indent.     (line  30)\n\n",
            "subsections": []
        }
    },
    "flags": [],
    "examples": [],
    "see_also": []
}