# HG changeset patch # User thomas_-_s # Date 1213262102 0 # Node ID 6dda59f4cc5a990abf856dfce0481536761f1c56 # Parent d2b86d5446786b7ecb17c25581033bf5cef0027c [change] Feature Request ID 1989587 : There is no longer any need to have a current value setting in the ini files. A default value is enough. http://universalindent.sf.net/issue/1989587 git-svn-id: svn://svn.code.sf.net/p/universalindent/code/trunk@722 59b1889a-e5ac-428c-b0c7-476e01d41282 diff -r d2b86d544678 -r 6dda59f4cc5a doc/iniFileFormat.html --- a/doc/iniFileFormat.html Thu Jun 12 06:57:31 2008 +0000 +++ b/doc/iniFileFormat.html Thu Jun 12 09:15:02 2008 +0000 @@ -73,9 +73,7 @@
"EditorType" defines whether the parameter is boolean, numeric, string or multiple.

-"Value" is the current defined value for the parameter. For boolean 0 is equal to false and 1 is equal to true. In case of multiple the number defines which of the multiple choice parameters is selected, starting with 0.
-
-"ValueDefault" is the default value that is normally used by the indenter if this parameter is not defined. It is needed if the config file of an indenter is loaded but this value is not defined there.
+"ValueDefault" is the default value that is normally used by the indenter if this parameter is not defined. It is needed if the config file of an indenter is loaded but this parameter value is not defined there. For boolean 0 is equal to false and 1 is equal to true. In case of multiple the number defines which of the multiple choice parameters is selected, starting with 0.

"Enabled" is not used for boolean but for all other parameters. Defines whether the value should be written to the indenters config file or not. If it is disabled it will not be written and the indenter uses its default value.

diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_CblBeau.ini --- a/indenters/uigui_CblBeau.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_CblBeau.ini Thu Jun 12 09:15:02 2008 +0000 @@ -20,7 +20,6 @@ [Add value clause] Category=0 Description="Add VALUE clauses to WS data items that have no VALUE clause" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -29,7 +28,6 @@ [Norm dd levels] Category=0 Description="Normalize data item level numbers" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -38,7 +36,6 @@ [Add end stmts] Category=0 Description="Add END-IF, END-SEARCH, END-EVALUATE, END-PERFORM closing statements" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -50,7 +47,6 @@ Description="Section name format, smth like T1%dT2%sT3" EditorType=string Enabled=false -Value="" ValueDefault="T1%dT2%sT3" [Section name start] @@ -61,7 +57,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Section name step] @@ -72,7 +67,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Para name fmt] @@ -81,7 +75,6 @@ Description="Paragraph name format, smth like T1%dT2%sT3" EditorType=string Enabled=false -Value="" ValueDefault="T1%dT2%sT3" [Para name start] @@ -92,7 +85,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Para name step] @@ -103,7 +95,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Data name fmt] @@ -112,7 +103,6 @@ Description="Data name format, smth like T1%dT2%sT3" EditorType=string Enabled=false -Value="" ValueDefault="T1%dT2%sT3" [Data name start] @@ -123,7 +113,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Data name step] @@ -134,13 +123,11 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Conv warn] Category=2 Description="Warn about transformation problems" -Value=1 ValueDefault=1 Enabled=true EditorType=boolean @@ -149,7 +136,6 @@ [Conv info] Category=2 Description="Inform about every transformation performed" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -158,7 +144,6 @@ [Conv list] Category=2 Description="List all transformations applied" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -167,7 +152,6 @@ [Find only] Category=2 Description="Only list potential transformations, do not execute them" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -176,7 +160,6 @@ [Silent] Category=2 Description="Do not print short summary of the conversion" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -185,7 +168,6 @@ [Primary Cobol dialect] Category=3 Description="Set the primary Cobol dialect" -Value=1 ValueDefault=1 Enabled=false EditorType=multiple @@ -195,7 +177,6 @@ [Secondary Cobol dialect] Category=3 Description="Set the secondary Cobol dialect" -Value=0 ValueDefault=0 Enabled=false EditorType=multiple @@ -205,7 +186,6 @@ [Line format] Category=3 Description="Set the secondary Cobol dialect" -Value=0 ValueDefault=0 Enabled=false EditorType=multiple @@ -215,7 +195,6 @@ [Progid comments] Category=3 Description="Allow Program-Id line comments" -Value=0 ValueDefault=0 Enabled=false EditorType=boolean @@ -224,7 +203,6 @@ [Separators follow spaces] Category=3 Description="Separators must be followed by spaces" -Value=0 ValueDefault=0 Enabled=false EditorType=multiple @@ -237,7 +215,6 @@ Description="Excluded keywords (separated by spaces?)" EditorType=string Enabled=false -Value="" ValueDefault="" [Indent size] @@ -248,5 +225,4 @@ Enabled=true MaxVal=99 MinVal=1 -Value=2 ValueDefault=2 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_astyle.ini --- a/indenters/uigui_astyle.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_astyle.ini Thu Jun 12 09:15:02 2008 +0000 @@ -23,7 +23,6 @@ Description=Sets the bracket style. EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [brackets-break-closing] @@ -31,7 +30,6 @@ Description=Breaks closing headers from their immediately preceding closing brackets. EditorType=boolean TrueFalse="--brackets=break-closing|" -Value=0 ValueDefault=0 [break-blocks] @@ -39,7 +37,6 @@ Description=Pad empty lines around header blocks (e.g. 'if' 'while'...). Be sure to read the Supplemental Documentation before using this option. EditorType=boolean TrueFalse=--break-blocks| -Value=0 ValueDefault=0 [break-blocks-all] @@ -47,7 +44,6 @@ Description=Pad empty lines around header blocks (e.g. 'if' 'while'...). Treat closing header blocks (e.g. 'else' 'catch') as stand-alone blocks. Be sure to read the Supplemental Documentation before using this option. EditorType=boolean TrueFalse="--break-blocks=all|" -Value=0 ValueDefault=0 [break-elseifs] @@ -55,7 +51,6 @@ Description=Break 'else if()' header combinations into separate lines. EditorType=boolean TrueFalse=--break-elseifs| -Value=0 ValueDefault=0 [convert-tabs] @@ -63,7 +58,6 @@ Description=Converts tabs into single spaces. EditorType=boolean TrueFalse=--convert-tabs| -Value=0 ValueDefault=0 [fill-empty-lines] @@ -71,7 +65,6 @@ Description=Fill empty lines with the white space of the previous line EditorType=boolean TrueFalse=--fill-empty-lines| -Value=0 ValueDefault=0 [force indent tab] @@ -82,7 +75,6 @@ Enabled=false MaxVal=20 MinVal=2 -Value=4 ValueDefault=4 [indent blocks] @@ -90,7 +82,6 @@ Description=Add extra indentation to entire blocks. EditorType=boolean TrueFalse=--indent-blocks| -Value=0 ValueDefault=0 [indent brackets] @@ -98,7 +89,6 @@ Description=Add extra indentation to brackets. EditorType=boolean TrueFalse=--indent-brackets| -Value=0 ValueDefault=0 [indent cases] @@ -106,7 +96,6 @@ Description=Indent 'case X:' blocks from the 'case X:' headers. Case statements not enclosed in blocks are NOT indented. EditorType=boolean TrueFalse=--indent-cases| -Value=0 ValueDefault=0 [indent classes] @@ -114,7 +103,6 @@ Description=Indent 'class' blocks so that the headers 'public:' 'protected:' and 'private:' are indented in the class block. EditorType=boolean TrueFalse=--indent-classes| -Value=0 ValueDefault=0 [indent lables] @@ -122,7 +110,6 @@ Description=Add extra indentation to labels so they appear 1 indent less than the current indentation rather than being flushed to the left (the default). EditorType=boolean TrueFalse=--indent-labels| -Value=0 ValueDefault=0 [indent namespaces] @@ -130,7 +117,6 @@ Description=Add extra indentation to namespaces. EditorType=boolean TrueFalse=--indent-namespaces| -Value=0 ValueDefault=0 [indent preprocessor] @@ -138,7 +124,6 @@ Description=Indent multi-line preprocessor definitions. should be used with --convert-tabs for proper results. Does a pretty good job but can not perform miracles in obfuscated preprocessor definitions. EditorType=boolean TrueFalse=--indent-preprocessor| -Value=0 ValueDefault=0 [indent spaces] @@ -149,7 +134,6 @@ Enabled=false MaxVal=20 MinVal=2 -Value=4 ValueDefault=4 [indent switches] @@ -157,7 +141,6 @@ Description=Indent 'switch' blocks so that the 'case X:' headers are indented in the switch block. EditorType=boolean TrueFalse=--indent-switches| -Value=0 ValueDefault=0 [indent tab] @@ -168,7 +151,6 @@ Enabled=false MaxVal=20 MinVal=2 -Value=4 ValueDefault=4 [max-instatement-indent] @@ -179,7 +161,6 @@ Enabled=false MaxVal=79 MinVal=0 -Value=40 ValueDefault=40 [min-conditional-indent] @@ -190,7 +171,6 @@ Enabled=false MaxVal=39 MinVal=0 -Value=8 ValueDefault=8 [one-line-keep-blocks] @@ -198,7 +178,6 @@ Description=Don't break one-line blocks EditorType=boolean TrueFalse="--one-line=keep-blocks|" -Value=0 ValueDefault=0 [one-line-keep-statements] @@ -206,7 +185,6 @@ Description=Don't break complex statements and multiple statements residing on a single line. EditorType=boolean TrueFalse="--one-line=keep-statements|" -Value=0 ValueDefault=0 [override-language] @@ -215,7 +193,6 @@ Description=Indent a C or C++ or Java file. The option is set from the file extension for each file. You can override the setting with this entry. It allows the formatter to identify language specific syntax such as C classes and C templates. EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [pad-oper] @@ -223,7 +200,6 @@ Description=Insert space padding around operators. Operators inside brackets [] are not padded. Note that there is no option to unpad. Once padded they stay padded. EditorType=boolean TrueFalse="--pad=oper|" -Value=0 ValueDefault=0 [pad-paren] @@ -231,7 +207,6 @@ Description=Insert space padding around parenthesis on both the outside and the inside. EditorType=boolean TrueFalse="--pad=paren|" -Value=0 ValueDefault=0 [pad-paren-in] @@ -239,7 +214,6 @@ Description="Insert space padding around parenthesis on the inside only. This can be used with unpad=paren below to remove unwanted spaces." EditorType=boolean TrueFalse="--pad=paren-in|" -Value=0 ValueDefault=0 [pad-paren-out] @@ -247,7 +221,6 @@ Description="Insert space padding around parenthesis on the outside only. This can be used with unpad=paren below to remove unwanted spaces." EditorType=boolean TrueFalse="--pad=paren-out|" -Value=0 ValueDefault=0 [predefined style] @@ -256,7 +229,6 @@ Description=Sets the general style. EditorType=multiple Enabled=false -Value=3 ValueDefault=3 [unpad-paren] @@ -264,5 +236,4 @@ Description="Remove space padding around parenthesis on the inside and outside. Can be used in combination with the paren padding options pad=paren-out and pad=paren-in above. Only padding that has not been requested by other options will be removed." EditorType=boolean TrueFalse="--unpad=paren|" -Value=0 ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_bcpp.ini --- a/indenters/uigui_bcpp.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_bcpp.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description=Setting this parameter to yes will strip any non-printable non-ASCII characters from the input file. Any non-printable characters that lie within quotes will be transformed into octal/character notation if NonAscii_Quotes_To_Octal is set to True. Comment out this parameter if you are using Leave_Graphic_Chars parameter as this parameter will override it. EditorType=boolean TrueFalse="ascii_chars_only=yes|ascii_chars_only=no" -Value=1 ValueDefault=1 [Backup_File] @@ -29,7 +28,6 @@ Description=This option will backup the input file to a file with the extension .bac and overwrite the input file with the reformatted version. EditorType=boolean TrueFalse="backup_file=yes|backup_file=no" -Value=0 ValueDefault=0 [Comments_With_Code] @@ -40,7 +38,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=50 ValueDefault=50 [Comments_With_Nocode] @@ -51,7 +48,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=0 ValueDefault=0 [Function_Spacing] @@ -62,7 +58,6 @@ Enabled=false MaxVal=99 MinVal=0 -Value=2 ValueDefault=2 [Indent_Exec_Sql] @@ -70,7 +65,6 @@ Description=If true bcpp looks for embedded SQL statements (e.g. EXEC SQL) and formats them specially. EditorType=boolean TrueFalse="indent_exec_sql=yes|indent_exec_sql=no" -Value=0 ValueDefault=0 [Indent_Preprocessor] @@ -78,7 +72,6 @@ Description=If true bcpp will indent preprocessor lines to the indention of the C(++) code. If false preprocessor lines will be in the first column. Unrecognized (i.e. nonstandard) preprocessor lines are always put into the first column. EditorType=boolean TrueFalse="indent_preprocessor=yes|indent_preprocessor=no" -Value=0 ValueDefault=0 [Indent_Spacing] @@ -89,7 +82,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=4 ValueDefault=4 [Leave_Comments_NoCode] @@ -97,7 +89,6 @@ Description=This options overrides the Comments_With_Nocodeoption. Setting this option On will indent comments that do not occur on the same line as code to the same indention as code. EditorType=boolean TrueFalse="leave_comments_nocode=yes|leave_comments_nocode=no" -Value=0 ValueDefault=0 [Leave_Graphic_Chars] @@ -105,7 +96,6 @@ Description=Setting this parameter to yes will strip non-printable characters from the source file but leave any characters that are IBM graphics alone. Any non-printable characters that lie within quotes will be transformed into octal/character notation if NonAscii_Quotes_To_Octal parameter is set to True. EditorType=boolean TrueFalse="leave_graphic_chars=yes|leave_graphic_chars=no" -Value=1 ValueDefault=1 [NonAscii_Quotes_To_Octal] @@ -113,7 +103,6 @@ Description=se this option to change non-ASCII (non-printable) chars to octal notation if they lie within quotes. This parameter doesn't take effect unless either the Ascii_Chars_Only or Leave_Graphic_Chars parameters have been set. EditorType=boolean TrueFalse="nonascii_quotes_to_octal=yes|nonascii_quotes_to_octal=no" -Value=0 ValueDefault=0 [Place_Brace_On_New_Line] @@ -121,7 +110,6 @@ Description=When set to 'on' bcpp will place opening braces on new lines (Pascalstyle C coding) when set to 'off' bcpp will use K&Rstyle C coding. EditorType=boolean TrueFalse="place_brace_on_new_line=yes|place_brace_on_new_line=no" -Value=1 ValueDefault=1 [Program_Output] @@ -129,7 +117,6 @@ Description=This parameter will stop output from the program corrupting output that may exit from the program via the standard output. If this parameter is set to off/no then no output is generated from the program unless an error is encountered. The standard error is used to display any errors encountered while processing. EditorType=boolean TrueFalse="program_output=yes|program_output=no" -Value=0 ValueDefault=0 [Queue_Buffer] @@ -140,7 +127,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=2 ValueDefault=2 [Use_Tabs] @@ -148,5 +134,4 @@ Description=Specifies whether to use tabs in indenting code. EditorType=boolean TrueFalse="use_tabs=yes|use_tabs=no" -Value=0 ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_csstidy.ini --- a/indenters/uigui_csstidy.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_csstidy.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description=Add Timestamp. EditorType=boolean TrueFalse="--timestamp=true|--timestamp=false" -Value=1 ValueDefault=0 [Allow HTML in templates] @@ -29,7 +28,6 @@ Description=Allow HTML in templates. EditorType=boolean TrueFalse="--allow_html_in_templates=true|--allow_html_in_templates=false" -Value=0 ValueDefault=1 [Case for properties] @@ -38,7 +36,6 @@ Description=
  0 - None.
  1 - Lowercase.
  2 - Uppercase.
EditorType=multiple Enabled=false -Value=1 ValueDefault=1 [Compress colors] @@ -46,7 +43,6 @@ Description=Compress colors. EditorType=boolean TrueFalse="--compress_colors=true|--compress_colors=false" -Value=1 ValueDefault=1 [Compress font-weight] @@ -54,7 +50,6 @@ Description=Compress font weight. EditorType=boolean TrueFalse="--compress_font=true|--compress_font=false" -Value=1 ValueDefault=1 [Lowercase selectors] @@ -62,7 +57,6 @@ Description=Lowercase selectors names needed for XHTML. EditorType=boolean TrueFalse="--lowercase_s=true|--lowercase_s=false" -Value=0 ValueDefault=0 [Optimise shorthands] @@ -71,7 +65,6 @@ Description=
  0 - Do not optimise.
  1 - Safe optimisations.
  2 - All optimisations.
EditorType=multiple Enabled=false -Value=1 ValueDefault=1 [Preserve CSS] @@ -79,7 +72,6 @@ Description="Save comments, hacks, etc.
Most optimisations can NOT be applied if this is enabled." EditorType=boolean TrueFalse="--preserve_css=true|--preserve_css=false" -Value=0 ValueDefault=0 [Regroup selectors] @@ -88,7 +80,6 @@ Description="
  0 - Do not change anything
  1 - Only seperate selectors (split at , )
  2 - Merge selectors with the same properties (fast)
" EditorType=multiple Enabled=false -Value=2 ValueDefault=2 [Remove last semikolon] @@ -96,7 +87,6 @@ Description="Remove last ;" EditorType=boolean TrueFalse="--remove_last_;=true|--remove_last_;=false" -Value=0 ValueDefault=0 [Remove unnecessary backslashes] @@ -104,7 +94,6 @@ Description=Remove backslashes. EditorType=boolean TrueFalse="--remove_bslash=true|--remove_bslash=false" -Value=1 ValueDefault=1 [Sort properties] @@ -112,7 +101,6 @@ Description=Sort properties. EditorType=boolean TrueFalse="--sort_properties=true|--sort_properties=false" -Value=0 ValueDefault=0 [Sort selectors %28caution%29] @@ -120,7 +108,6 @@ Description=Attention: This may change the behavior of your CSS code! EditorType=boolean TrueFalse="--sort_selectors=true|--sort_selectors=false" -Value=0 ValueDefault=0 [Template] @@ -129,5 +116,4 @@ Description="
  Highest - No readability, smallest size.
  High - Moderate readability, smaller size.
  Default - balance between readability and size.
  Low - Higher readability.
" EditorType=multiple Enabled=false -Value=2 ValueDefault=2 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_gnuindent.ini --- a/indenters/uigui_gnuindent.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_gnuindent.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description=original Berkeley indent EditorType=boolean TrueFalse=-orig| -Value=1 ValueDefault=0 [GNU style formatting] @@ -29,7 +28,6 @@ Description=GNU style formatting/indenting. EditorType=boolean TrueFalse=-gnu| -Value=1 ValueDefault=0 [KR style formatting] @@ -37,7 +35,6 @@ Description=Kernighan&Ritchie style formatting/indenting. EditorType=boolean TrueFalse=-kr| -Value=1 ValueDefault=0 [blank-before-sizeof] @@ -45,7 +42,6 @@ Description=Put a space between sizeof and its argument. EditorType=boolean TrueFalse=-bs| -Value=0 ValueDefault=0 [blank-lines-after-commas] @@ -53,7 +49,6 @@ Description=Force newline after comma in declaration. EditorType=boolean TrueFalse=-bc| -Value=0 ValueDefault=0 [blank-lines-after-declarations] @@ -61,7 +56,6 @@ Description=The -bad option forces a blank line after every block of declarations. EditorType=boolean TrueFalse=-bad| -Value=0 ValueDefault=0 [blank-lines-after-procedures] @@ -69,7 +63,6 @@ Description=The -bap option forces a blank line after every procedure body. EditorType=boolean TrueFalse=-bap| -Value=0 ValueDefault=0 [blank-lines-before-block-comments] @@ -77,7 +70,6 @@ Description=Force blank lines before block comments. EditorType=boolean TrueFalse=-bbb| -Value=0 ValueDefault=0 [brace-indentn] @@ -88,7 +80,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=3 ValueDefault=3 [braces-after-if-line] @@ -96,7 +87,6 @@ Description="Put braces on line after if, etc." EditorType=boolean TrueFalse=-bl| -Value=0 ValueDefault=0 [braces-after-struct-decl-line] @@ -104,7 +94,6 @@ Description=Put braces on the line after struct declaration lines. EditorType=boolean TrueFalse=-bls| -Value=0 ValueDefault=0 [braces-on-if-line] @@ -112,7 +101,6 @@ Description="Put braces on line with if, etc." EditorType=boolean TrueFalse=-br| -Value=0 ValueDefault=0 [braces-on-struct-decl-line] @@ -120,7 +108,6 @@ Description=Put braces on struct declaration line. EditorType=boolean TrueFalse=-brs| -Value=0 ValueDefault=0 [break-after-boolean-operator] @@ -128,7 +115,6 @@ Description=Do not prefer to break long lines before boolean operators. EditorType=boolean TrueFalse=-nbbo| -Value=0 ValueDefault=0 [break-before-boolean-operator] @@ -136,7 +122,6 @@ Description=Prefer to break long lines before boolean operators. EditorType=boolean TrueFalse=-bbo| -Value=0 ValueDefault=0 [break-function-decl-args] @@ -144,7 +129,6 @@ Description=Break the line after the last argument in a declaration. EditorType=boolean TrueFalse=-bfde| -Value=0 ValueDefault=0 [case-brace-indentationn] @@ -155,7 +139,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [case-indentationn] @@ -166,7 +149,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [comment-delimiters-on-blank-lines] @@ -174,7 +156,6 @@ Description=Put comment delimiters on blank lines. EditorType=boolean TrueFalse=-cdb| -Value=0 ValueDefault=0 [comment-indentationn] @@ -185,7 +166,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=33 ValueDefault=33 [comment-line-lengthn] @@ -196,7 +176,6 @@ Enabled=false MaxVal=120 MinVal=1 -Value=78 ValueDefault=78 [continuation-indentationn] @@ -207,7 +186,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [continue-at-parentheses] @@ -215,7 +193,6 @@ Description=Line up continued lines at parentheses. EditorType=boolean TrueFalse=-lp| -Value=0 ValueDefault=0 [cuddle-do-while] @@ -223,7 +200,6 @@ Description="Cuddle while of do {} while; and preceeding `}'." EditorType=boolean TrueFalse=-cdw| -Value=0 ValueDefault=0 [cuddle-else] @@ -231,7 +207,6 @@ Description=Cuddle else and preceeding `}'. EditorType=boolean TrueFalse=-ce| -Value=0 ValueDefault=0 [declaration-comment-columnn] @@ -242,7 +217,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=33 ValueDefault=33 [declaration-indentationn] @@ -253,7 +227,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [dont-break-function-decl-args] @@ -261,7 +234,6 @@ Description=Don't put each argument in a function declaration on a seperate line. EditorType=boolean TrueFalse=-nbfda| -Value=0 ValueDefault=0 [dont-break-procedure-type] @@ -269,7 +241,6 @@ Description=Put the type of a procedure on the same line as its name. EditorType=boolean TrueFalse=-npsl| -Value=0 ValueDefault=0 [dont-cuddle-do-while] @@ -277,7 +248,6 @@ Description="Do not cuddle } and the while of a do {} while;." EditorType=boolean TrueFalse=-ncdw| -Value=0 ValueDefault=0 [dont-cuddle-else] @@ -285,7 +255,6 @@ Description=Do not cuddle } and else. EditorType=boolean TrueFalse=-nce| -Value=0 ValueDefault=0 [dont-line-up-parentheses] @@ -293,7 +262,6 @@ Description=Do not line up parentheses. EditorType=boolean TrueFalse=-nlp| -Value=0 ValueDefault=0 [dont-space-special-semicolon] @@ -301,7 +269,6 @@ Description=Do not force a space before the semicolon after certain statements. Disables `-ss'. EditorType=boolean TrueFalse=-nss| -Value=0 ValueDefault=0 [else-endif-columnn] @@ -312,7 +279,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=33 ValueDefault=33 [format-all-comments] @@ -320,7 +286,6 @@ Description=Do not disable all formatting of comments. EditorType=boolean TrueFalse=-fca| -Value=0 ValueDefault=0 [format-first-column-comments] @@ -328,7 +293,6 @@ Description=Format comments in the first column. EditorType=boolean TrueFalse=-fc1| -Value=0 ValueDefault=0 [honour-newlines] @@ -336,7 +300,6 @@ Description=Prefer to break long lines at the position of newlines in the input. EditorType=boolean TrueFalse=-hnl| -Value=0 ValueDefault=0 [ignore-newlines] @@ -344,7 +307,6 @@ Description=Do not prefer to break long lines at the position of newlines in the input. EditorType=boolean TrueFalse=-nhnl| -Value=0 ValueDefault=0 [indent-leveln] @@ -355,7 +317,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [leave-preprocessor-space] @@ -363,7 +324,6 @@ Description=Leave space between `#' and preprocessor directive. EditorType=boolean TrueFalse=-lps| -Value=0 ValueDefault=0 [line-comments-indentationn] @@ -374,7 +334,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=33 ValueDefault=33 [line-lengthn] @@ -385,7 +344,6 @@ Enabled=false MaxVal=220 MinVal=1 -Value=99 ValueDefault=120 [no-blank-lines-after-commas] @@ -393,7 +351,6 @@ Description=Do not force newlines after commas in declarations. EditorType=boolean TrueFalse=-nbc| -Value=0 ValueDefault=0 [no-parameter-indentation] @@ -401,7 +358,6 @@ Description=Zero width indentation for parameters. EditorType=boolean TrueFalse=-nip| -Value=0 ValueDefault=0 [no-space-after-casts] @@ -409,7 +365,6 @@ Description=Do not put a space after cast operators. EditorType=boolean TrueFalse=-ncs| -Value=0 ValueDefault=0 [no-space-after-for] @@ -417,7 +372,6 @@ Description=Do not put a space after every for. EditorType=boolean TrueFalse=-nsaf| -Value=0 ValueDefault=0 [no-space-after-function-call-names] @@ -425,7 +379,6 @@ Description=Do not put space after the function in function calls. EditorType=boolean TrueFalse=-npcs| -Value=0 ValueDefault=0 [no-space-after-if] @@ -433,7 +386,6 @@ Description=Do not put a space after every if. EditorType=boolean TrueFalse=-nsai| -Value=0 ValueDefault=0 [no-space-after-parentheses] @@ -441,7 +393,6 @@ Description=Do not put a space after every '(' and before every ')'. EditorType=boolean TrueFalse=-nprs| -Value=0 ValueDefault=0 [no-space-after-while] @@ -449,7 +400,6 @@ Description=Do not put a space after every while. EditorType=boolean TrueFalse=-nsaw| -Value=0 ValueDefault=0 [no-tabs] @@ -457,7 +407,6 @@ Description=Use spaces instead of tabs. EditorType=boolean TrueFalse=-nut| -Value=1 ValueDefault=1 [parameter-indentationn] @@ -468,7 +417,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [paren-indentationn] @@ -479,7 +427,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [procnames-start-lines] @@ -487,7 +434,6 @@ Description=Put the type of a procedure on the line before its name. EditorType=boolean TrueFalse=-psl| -Value=0 ValueDefault=0 [space-after-cast] @@ -495,7 +441,6 @@ Description=Put a space after a cast operator. EditorType=boolean TrueFalse=-cs| -Value=0 ValueDefault=0 [space-after-for] @@ -503,7 +448,6 @@ Description=Put a space after each for. EditorType=boolean TrueFalse=-saf| -Value=0 ValueDefault=0 [space-after-if] @@ -511,7 +455,6 @@ Description=Put a space after each if. EditorType=boolean TrueFalse=-sai| -Value=0 ValueDefault=0 [space-after-parentheses] @@ -519,7 +462,6 @@ Description=Put a space after every '(' and before every ')'. EditorType=boolean TrueFalse=-prs| -Value=0 ValueDefault=0 [space-after-procedure-calls] @@ -527,7 +469,6 @@ Description=Insert a space between the name of the procedure being called and the `('. EditorType=boolean TrueFalse=-pcs| -Value=0 ValueDefault=0 [space-after-while] @@ -535,7 +476,6 @@ Description=Put a space after each while. EditorType=boolean TrueFalse=-saw| -Value=0 ValueDefault=0 [space-special-semicolon] @@ -543,7 +483,6 @@ Description="On one-line for and while statements, force a blank before the semicolon." EditorType=boolean TrueFalse=-ss| -Value=0 ValueDefault=0 [start-left-side-of-comments] @@ -551,7 +490,6 @@ Description=Put the `*' character at the left of comments. EditorType=boolean TrueFalse=-sc| -Value=0 ValueDefault=0 [struct-brace-indentationn] @@ -562,7 +500,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [swallow-optional-blank-lines] @@ -570,7 +507,6 @@ Description=The -sob option causes indent to swallow optional blank lines. EditorType=boolean TrueFalse=-sob| -Value=0 ValueDefault=0 [tab-sizen] @@ -581,7 +517,6 @@ Enabled=false MaxVal=120 MinVal=0 -Value=4 ValueDefault=4 [use-tabs] @@ -589,5 +524,4 @@ Description=Use tabs. EditorType=boolean TrueFalse=-ut| -Value=0 ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_greatcode.ini --- a/indenters/uigui_greatcode.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_greatcode.ini Thu Jun 12 09:15:02 2008 +0000 @@ -24,7 +24,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_add_class_access] @@ -32,7 +31,6 @@ Description="Add an empty comment before class access (if not already present).
Comment level is set by -cmt_sep_force_class_access- option.
Example :
        -cmt_add_class_access-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class a
        {
        public:
            void v(void)
        protected:
            int c
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class a
        {
        /*      <= by default. cmt level is 2
         ==========================================
         ==========================================
         */
        public:
            void v(void)

        /*
         ==========================================
         ==========================================
         */
        protected:
            int c
        }

        See option(s) :
        -cmt_sep_char_2-
        -cmt_sep_len-
        -cmt_sep_force_class_access-
" EditorType=boolean TrueFalse=-cmt_add_class_access-|-no-cmt_add_class_access- -Value=0 ValueDefault=1 [cmt_add_fct_def] @@ -40,7 +38,6 @@ Description="Add an empty comment before function definition (if not already
present).
Comment is level is set by -cmt_sep_force_fct_def- option.

** file.c **

/*
==========================================
==========================================
*/
int a(void)
{
}

** EOF **

See option(s) :
-cmt_sep_char_3-
-cmt_sep_len-
-cmt_sep_force_fct_def-

Note(s) :
- Actual comments before function are included in the separator." EditorType=boolean TrueFalse=-cmt_add_fct_def-|-no-cmt_add_fct_def- -Value=0 ValueDefault=1 [cmt_add_fct_def_class] @@ -48,7 +45,6 @@ Description=Same as -cmt_add_fct_def-. but for functions defined inside a class
\t\t(inline functions).

See option(s) :
\t\t-cmt_add_fct_def- EditorType=boolean TrueFalse=-cmt_add_fct_def_class-|-no-cmt_add_fct_def_class- -Value=0 ValueDefault=1 [cmt_add_file] @@ -56,7 +52,6 @@ Description=Add a special comment at the beginning of file (if not already
present). The type of the comment is set by -cmt_add_file_style-.

-cmt_add_file-
-cmt_add_file_style-0
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

** file.c **
/*$6
++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++
*/
...
** EOF **

-cmt_add_file-
-cmt_add_file_style-1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

** file.c **
/*$I0
...
*/
...
** EOF **

See option(s) :
-cmt_sep_char_6-
-cmt_sep_len-
-cmt_add_file_style- EditorType=boolean TrueFalse=-cmt_add_file-|-no-cmt_add_file- -Value=0 ValueDefault=1 [cmt_add_file_style] @@ -67,7 +62,6 @@ Enabled=true MaxVal=1 MinVal=0 -Value=0 ValueDefault=0 [cmt_add_gc_tag] @@ -75,7 +69,6 @@ Description=Add the GC mark at the beginning of the file.

/*$T test.c GC 1.102 01/06/01 16:47:25 */ EditorType=boolean TrueFalse=-cmt_add_gc_tag-|-no-cmt_add_gc_tag- -Value=0 ValueDefault=1 [cmt_align_max_blanks] @@ -86,7 +79,6 @@ Enabled=true MaxVal=2000 MinVal=1 -Value=1 ValueDefault=10 [cmt_c2cpp] @@ -94,7 +86,6 @@ Description=Convert all C comments to the C++ form. Only end of lines comments are
converted.
See option(s) :
-cmt_keep_cpp-

Note(s) :
- This option set the -cmt_keep_cpp- to true. EditorType=boolean TrueFalse=-cmt_c2cpp-|-no-cmt_c2cpp- -Value=1 ValueDefault=0 [cmt_cpp2c_keep_eol] @@ -102,7 +93,6 @@ Description="Keep trace of EOL characters when converting C++ comments to C
comment. -cmt_keep_cpp- must be enabled.
Example :
        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        // this is a comment
        // this is another comment

        -cmt_cpp2c_keep_eol-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * this is a comment           <=  is the default break character
         * this is another comment
         */

        -no-cmt_cpp2c_keep_eol-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* this is a comment this is another comment */

        See option(s) :
        [no]-cmt_keep_cpp-
        -cmt_sep_char_split-
" EditorType=boolean TrueFalse=-cmt_cpp2c_keep_eol-|-no-cmt_cpp2c_keep_eol- -Value=1 ValueDefault=1 [cmt_decl] @@ -110,7 +100,6 @@ Description="Add separators in local variable declaration (before and/or after).
Separators are by default level 1.
Example :
        -cmt_decl-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a(void)
        {
            unsigned int    var
            long b
            var = 0
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a(void)
        {
            /*~~~~~~~~~~~~~~~~~~*/
            unsigned int    var
            long            b
            /*~~~~~~~~~~~~~~~~~~*/

            var = 0
        }

        See options(s) :
        -cmt_decl_max_level-
        [-no]-cmt_decl_before-
        -cmt_decl_len-
        [-no]-cmt_decl_auto_len-
        -cmt_decl_auto_len_add-

        Note(s) :
        - Can't be used with -cmt_dont_modify- option.
" EditorType=boolean TrueFalse=-cmt_decl-|-no-cmt_decl- -Value=0 ValueDefault=1 [cmt_decl_auto_len] @@ -118,7 +107,6 @@ Description="Co
mpute the length of the decl separator depending on code.
        Is disabled. the length is set by -cmt_decl_len- option.
" EditorType=boolean TrueFalse=-cmt_decl_auto_len-|-no-cmt_decl_auto_len- -Value=1 ValueDefault=1 [cmt_decl_auto_len_add] @@ -129,7 +117,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [cmt_decl_before] @@ -137,7 +124,6 @@ Description="Add a separator before local declarations.
-cmt_decl- must be enabled.
Example :
        -cmt_decl_before-

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a(void)
        {
            /*~~~~~~~~~~~~~~~~~~*/
            unsigned int    var
            long            b
            /*~~~~~~~~~~~~~~~~~~*/

            var = 0
        }

        -no-cmt_decl_before-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a(void)
        {
            unsigned int    var
            long            b
            /*~~~~~~~~~~~~~~~~~~*/

            var = 0
        }
" EditorType=boolean TrueFalse=-cmt_decl_before-|-no-cmt_decl_before- -Value=0 ValueDefault=1 [cmt_decl_len] @@ -148,7 +134,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=120 [cmt_decl_max_level] @@ -159,7 +144,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=100 [cmt_dont_modify] @@ -167,7 +151,6 @@ Description="Pr
ocess or not all the comments of the file.
" EditorType=boolean TrueFalse=-cmt_dont_modify-|-no-cmt_dont_modify- -Value=1 ValueDefault=0 [cmt_fct_categ] @@ -176,7 +159,6 @@ Description="-cmt_fct_categ- Define a special word when indenting function
comments.
-cmt_fct_categ_in- This word is a special category to describe
function parameters.

GC can indent function definition comments in a special form
depending of special words defined with those options.
Example :
        options
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        -cmt_fct_categ-main
        -cmt_fct_categ-output
        -cmt_fct_categ_in-parameters


        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Description: Description of the function. Return: none
        Parameters: a - entering value b - increment value */
        int function(int a. int b)
        {
        }


        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         ==========================================
         Description:\tDescription of the function.

         Return:\tnone

         Parameters:    a   - entering value
                        b   - increment value
         ==========================================
         */
        int function(int a. int b)
        {
        }

        See option(s) :
        [-no]-cmt_add_fct_def-
\t\t-cmt_fct_categ_style-

        Note(s) :
        - In comment. special words must be followed by ':'.
        - A parameter must be followed by '-'. and then by the comment.
        - This option can't be set in a source file with special comment
          /*$O */
" EditorType=string Enabled=false -Value= ValueDefault= [cmt_fct_categ_in] @@ -185,7 +167,6 @@ Description="-cmt_fct_categ- Define a special word when indenting function
comments.
-cmt_fct_categ_in- This word is a special category to describe
function parameters.

GC can indent function definition comments in a special form
depending of special words defined with those options.
Example :
        options
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        -cmt_fct_categ-main
        -cmt_fct_categ-output
        -cmt_fct_categ_in-parameters


        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Description: Description of the function. Return: none
        Parameters: a - entering value b - increment value */
        int function(int a. int b)
        {
        }


        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         ==========================================
         Description:\tDescription of the function.

         Return:\tnone

         Parameters:    a   - entering value
                        b   - increment value
         ==========================================
         */
        int function(int a. int b)
        {
        }

        See option(s) :
        [-no]-cmt_add_fct_def-
\t\t-cmt_fct_categ_style-

        Note(s) :
        - In comment. special words must be followed by ':'.
        - A parameter must be followed by '-'. and then by the comment.
        - This option can't be set in a source file with special comment
          /*$O */
" EditorType=string Enabled=false -Value= ValueDefault= [cmt_fct_categ_style] @@ -196,7 +177,6 @@ Enabled=true MaxVal=1 MinVal=0 -Value=0 ValueDefault=0 [cmt_fct_java_doc] @@ -204,7 +184,6 @@ Description=Enable the java doc type comments for functions only. Also enables -cmt_sep_fill_star-. EditorType=boolean TrueFalse=-cmt_fct_java_doc-|-no-cmt_fct_java_doc- -Value=1 ValueDefault=0 [cmt_first_line_blank] @@ -212,7 +191,6 @@ Description="Add an empty line between two adjacent first line comments.
-cmt_first_line_concat- must be disabled.
Example :
        -cmt_first_line_blank-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* comment1 */
        /* comment2 */
        /* comment3 */
        if(a)
        {
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* comment1 */
        
        /* comment2 */
        
        /* comment3 */
        if(a)
        {
        }

        See options(s) :
        [-no]-cmt_first_line_concat-
" EditorType=boolean TrueFalse=-cmt_first_line_blank-|-no-cmt_first_line_blank- -Value=0 ValueDefault=1 [cmt_first_line_break_first] @@ -220,7 +198,6 @@ Description="Add an EOL after /* of first line comments.
Add an EOL before */ of first line comments.
Example :
        -cmt_first_line_break_first-
        -cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * Comment 
         * Comment
         */

        -no-cmt_first_line_break_first-
        -cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Comment 
         * Comment
         */

        -no-cmt_first_line_break_first-
        -no-cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Comment 
         * Comment */
" EditorType=boolean TrueFalse=-cmt_first_line_break_first-|-no-cmt_first_line_break_first- -Value=1 ValueDefault=1 [cmt_first_line_break_last] @@ -228,7 +205,6 @@ Description="Add an EOL after /* of first line comments.
Add an EOL before */ of first line comments.
Example :
        -cmt_first_line_break_first-
        -cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * Comment 
         * Comment
         */

        -no-cmt_first_line_break_first-
        -cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Comment 
         * Comment
         */

        -no-cmt_first_line_break_first-
        -no-cmt_first_line_break_last-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* Comment 
         * Comment */
" EditorType=boolean TrueFalse=-cmt_first_line_break_last-|-no-cmt_first_line_break_last- -Value=1 ValueDefault=1 [cmt_first_line_concat] @@ -236,7 +212,6 @@ Description="Concat adjacent first line comments.
Example :
        -cmt_first_line_concat-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* first line comment */
        /* another first line comment */

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * first line comment 
         * another first line comment
         */
" EditorType=boolean TrueFalse=-cmt_first_line_concat-|-no-cmt_first_line_concat- -Value=0 ValueDefault=1 [cmt_first_line_fill_star] @@ -244,7 +219,6 @@ Description="Add a '*' character at the beginning of lines of first line comments.
Example :
        -cmt_first_line_fill_star-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * Comment 
         * Comment
         */

        -no-cmt_first_line_fill_star-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
           Comment 
           Comment
         */

        See options(s) :
        [-no]-cmt_sep_fill_star-

        Note(s) :
        - Separators are not concerned.
" EditorType=boolean TrueFalse=-cmt_first_line_fill_star-|-no-cmt_first_line_fill_star- -Value=0 ValueDefault=1 [cmt_first_line_len] @@ -255,7 +229,6 @@ Enabled=true MaxVal=2000 MinVal=8 -Value=80 ValueDefault=80 [cmt_first_space_cpp] @@ -263,7 +236,6 @@ Description="Force a space after the opening comment delimiter.
Example :
        -cmt_first_space_cpp-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        // coucou

        -no-cmt_first_space_cpp-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        //coucou
" EditorType=boolean TrueFalse=-cmt_first_space_cpp-|-no-cmt_first_space_cpp- -Value=1 ValueDefault=1 [cmt_fixme] @@ -271,8 +243,7 @@ Category=5 Description="Specify the string for FIXME comment the default is /* FIXME: Comment */
Example :
        -cmt_fixme-/* TODO: add comment */
" EditorType=string -Enabled=true -Value= +Enabled=false ValueDefault=/* */ [cmt_force_fct_def_decl_split] @@ -280,7 +251,6 @@ Description="Fo
rce function definitions to split at each paramenter according
        to the sytle defined by -code_split_fctdef_style-
" EditorType=boolean TrueFalse=-cmt_force_fct_def_decl_split-|-no-cmt_force_fct_def_decl_split- -Value=1 ValueDefault=0 [cmt_java_doc] @@ -288,7 +258,6 @@ Description=Enable the java doc type comments for all comments. Also enables -cmt_sep_fill_star- and -cmt_fct_java_doc- EditorType=boolean TrueFalse=-cmt_java_doc-|-no-cmt_java_doc- -Value=1 ValueDefault=0 [cmt_keep-char_1] @@ -297,7 +266,6 @@ Description=(1) Keep the comment identical to /*$F but apply to the character next to the * in /* EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_2] @@ -306,7 +274,6 @@ Description=(2) Keep the comment identical to /*$F but apply to the character next to the * in /* EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_3] @@ -315,7 +282,6 @@ Description=(3) Keep the comment identical to /*$F but apply to the character next to the * in /* EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_4] @@ -324,7 +290,6 @@ Description=(4) Keep the comment identical to /*$F but apply to the character next to the * in /* EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_cpp_1] @@ -333,7 +298,6 @@ Description=(1) Keep the cpp comment as is character after the //. EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_cpp_2] @@ -342,7 +306,6 @@ Description=(2) Keep the cpp comment as is character after the //. EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_cpp_3] @@ -351,7 +314,6 @@ Description=(3) Keep the cpp comment as is character after the //. EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep-char_cpp_4] @@ -360,7 +322,6 @@ Description=(4) Keep the cpp comment as is character after the //. EditorType=string Enabled=false -Value= ValueDefault= [cmt_keep_cpp] @@ -368,7 +329,6 @@ Description="Keep C++ comments. and do not change them to the C form.
Example :
        -no-cmt_keep_cpp-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        // this is a comment
        // this is another comment

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * this is a comment 
         * this is another comment
         */

        See option(s) :
        [no]-cmt_cpp2c_keep_eol-
        -cmt_sep_char_split-

        Note(s) :
        - This option can't be set in a source file with special comment
          /*$O */
" EditorType=boolean TrueFalse=-cmt_keep_cpp-|-no-cmt_keep_cpp- -Value=1 ValueDefault=0 [cmt_sep_break] @@ -376,7 +336,6 @@ Description="Force /* and */ to be alone on their lines for separators.
Example :
        -cmt_sep_break-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         ===================
           comment 
           comment
         ===================
         */

        //
        // =================
        // comment
        // =================
        //

        -no-cmt_sep_break-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* =================
           comment 
           comment
         =================== */

        // =================
        // comment
        // =================
" EditorType=boolean TrueFalse=-cmt_sep_break-|-no-cmt_sep_break- -Value=1 ValueDefault=1 [cmt_sep_char_1] @@ -385,7 +344,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value=~ ValueDefault=~ [cmt_sep_char_2] @@ -394,7 +352,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value=- ValueDefault=- [cmt_sep_char_3] @@ -403,7 +360,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value="=" ValueDefault="=" [cmt_sep_char_4] @@ -412,7 +368,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value=* ValueDefault=* [cmt_sep_char_5] @@ -421,7 +376,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value=# ValueDefault=# [cmt_sep_char_6] @@ -430,7 +384,6 @@ Description="Set the special character to fill automatic comments.
Example :
        -cmt_sep_char_1-O
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$1-OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO*/
        /*$1
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
         */

        -cmt_sep_char_2-#
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$2-####################################*/
        /*$2
         ##########################################
         ##########################################
         */

        Note(s) :
        - /*$- */ is a special form comment recognized by GC.
          This is a single line comment.
        - /*$ */ is a special form comment recognized by GC.
          This is a multiline comment.
" EditorType=string Enabled=true -Value=+ ValueDefault=+ [cmt_sep_char_split] @@ -439,7 +392,6 @@ Description="Define the special break line character in comments.
        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /* coucou  salut */

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*
         * coucou 
         * salut
         */

        See option(s) :
        [-no]-cmt_first_line_concat-
        [-no]-cmt_cpp2c_keep_eol-

        Note(s) :
        - GC uses this special character to keep trace of EOL when converting
          C++ comments to C comments. or to concat first line comments.
" EditorType=string Enabled=true -Value= ValueDefault= [cmt_sep_eol_after] @@ -450,7 +402,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [cmt_sep_eol_after_1] @@ -461,7 +412,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_after_2] @@ -472,7 +422,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_after_3] @@ -483,7 +432,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_after_4] @@ -494,7 +442,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_after_5] @@ -505,7 +452,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_after_6] @@ -516,7 +462,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=2 [cmt_sep_eol_before] @@ -527,7 +472,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_1] @@ -538,7 +482,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_2] @@ -549,7 +492,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_3] @@ -560,7 +502,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_4] @@ -571,7 +512,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_5] @@ -582,7 +522,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [cmt_sep_eol_before_6] @@ -593,7 +532,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=2 [cmt_sep_eol_before_fct_def] @@ -604,7 +542,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [cmt_sep_fill_star] @@ -612,7 +549,6 @@ Description="Add a star at the beginning of all lines of a separator.
Example :
        -cmt_sep_fill_star-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$4
         *******************
         *    comment 
         *    comment
         *******************
         */

        -no-cmt_sep_fill_star-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        /*$4
         *******************
           comment 
           comment
         *******************
         */

        See option(s) :
        -cmt_sep_char_4-
        -cmt_sep_char_split-
        [-no]-cmt_first_line_fill_star-
" EditorType=boolean TrueFalse=-cmt_sep_fill_star-|-no-cmt_sep_fill_star- -Value=1 ValueDefault=0 [cmt_sep_force_class] @@ -623,7 +559,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=3 [cmt_sep_force_class_access] @@ -634,7 +569,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=2 [cmt_sep_force_fct_def] @@ -645,7 +579,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=3 [cmt_sep_force_fct_macro] @@ -656,7 +589,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=3 [cmt_sep_force_fct_proto] @@ -667,7 +599,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [cmt_sep_force_struct] @@ -678,7 +609,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=2 [cmt_sep_len] @@ -689,7 +619,6 @@ Enabled=true MaxVal=2000 MinVal=8 -Value=99 ValueDefault=120 [cmt_split_before_%40_in_fct_cmts] @@ -697,7 +626,6 @@ Description=Split lines in fucntion comments before @ EditorType=boolean TrueFalse=-cmt_split_before_@_in_fct_cmts-|-no-cmt_split_before_@_in_fct_cmts- -Value=0 ValueDefault=0 [cmt_trailing_style] @@ -708,7 +636,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [code_align_max_blanks] @@ -719,7 +646,6 @@ Enabled=true MaxVal=2000 MinVal=1 -Value=1 ValueDefault=1000 [code_class_access_eol_after] @@ -730,7 +656,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [code_class_access_eol_before] @@ -741,7 +666,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [code_concat_strings] @@ -749,7 +673,6 @@ Description="Concat adjacent string constants.
Example :
        -no-code_concat_strings-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        printf(coucoulafoule)

        -code_concat_strings-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        printf(coucoulafoule)
" EditorType=boolean TrueFalse=-code_concat_strings-|-no-code_concat_strings- -Value=1 ValueDefault=0 [code_constructor_style] @@ -760,7 +683,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [code_decl_access_to_type] @@ -768,7 +690,6 @@ Description="Move * and & access specifier just after the type if TRUE. or
just before the name if FALSE.
Example :
        -code_decl_access_to_type-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int**   p
        int function(int* b. int& ref)
        {
        }

        -no-code_decl_access_to_type-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int     **p
        int function(int *b. int &ref)
        {
        }
" EditorType=boolean TrueFalse=-code_decl_access_to_type-|-no-code_decl_access_to_type- -Value=1 ValueDefault=0 [code_decl_add_void] @@ -776,7 +697,6 @@ Description="Force the voidkeyword in a function declaration if nothing is
specified.
Example :
        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int function()
        {
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int function(void)
        {
        }
" EditorType=boolean TrueFalse=-code_decl_add_void-|-no-code_decl_add_void- -Value=1 ValueDefault=0 [code_decl_break_template] @@ -784,7 +704,6 @@ Description="Force an EOL after a template declaration.
Example :
        -code_decl_break_template-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        template    <= EOL
        class TestClass
        {
        public:
            char    buffer[i]
            T\t\ttestFunc(T *p1)
        }

        -no-code_decl_break_template-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        template class TestClass
        {
        public:
            char    buffer[i]
            T\t\ttestFunc(T *p1)
        }
" EditorType=boolean TrueFalse=-code_decl_break_template-|-no-code_decl_break_template- -Value=1 ValueDefault=1 [code_decl_move_affect] @@ -792,7 +711,6 @@ Description="Move initialization in local variables declaration just after the
declaration.
Example :
        -code_decl_move_affect-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a = 0
            int     c = a + 1
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a
            int     c

            a = 0      <= initializations has been moved
            c = a + 1
        }

        Note(s) :
        - Be careful because this option sometimes does not work well. That's
          why it's set to FALSE by default.
" EditorType=boolean TrueFalse=-code_decl_move_affect-|-no-code_decl_move_affect- -Value=1 ValueDefault=0 [code_decl_move_top] @@ -800,7 +718,6 @@ Description="Move all local variables declaration to the top of the corresponding
statement.
Example :
        -code_decl_move_top-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a. b

            a = b = 0
            while(a)
            {
            }

            int c          <= declaration
            c = 10
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a. b
            int c          <= declaration has been moved

            a = b = 0
            while(a)
            {
            }

            c = 10
        }
" EditorType=boolean TrueFalse=-code_decl_move_top-|-no-code_decl_move_top- -Value=1 ValueDefault=0 [code_def_fct_break_return_type] @@ -808,7 +725,6 @@ Description="Force a line break after the return type in a function definition.
Example :
        -code_def_fct_break_return_type-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int
        function(void)
        {
        }

        int 
        class::func(void)
        {
        }

        -no-code_def_fct_break_return_type-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int function(void)
        {
        }

        int class::func(void)
        {
        }
" EditorType=boolean TrueFalse=-code_def_fct_break_return_type-|-no-code_def_fct_break_return_type- -Value=1 ValueDefault=0 [code_empty_fct_blanks] @@ -819,7 +735,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [code_eol_after_close_brace] @@ -830,7 +745,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [code_force_return_paren] @@ -838,7 +752,6 @@ Description="Force parentheses around a returnexpression.
Example :
        -code_force_return_paren-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a()
        {
            return 0
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a()
        {
            return(0)
        }

        See option(s) :
        [-no]-code_remove_return_paren-

        Note(s) :
        - This option can't be set in a source file with special comment
          /*$O */
        - Can't be used with -code_remove_return_paren- option.
" EditorType=boolean TrueFalse=-code_force_return_paren-|-no-code_force_return_paren- -Value=0 ValueDefault=0 [code_keep_empty_lines] @@ -846,7 +759,6 @@ Description=Keep empty lines in original file EditorType=boolean TrueFalse=-code_keep_empty_lines-|-no-code_keep_empty_lines- -Value=1 ValueDefault=1 [code_keep_more_empty_lines] @@ -854,7 +766,6 @@ Description=Make more effort to preserve empty lines in the original file - even in the face of other reformatting EditorType=boolean TrueFalse=-code_keep_more_empty_lines-|-no-code_keep_more_empty_lines- -Value=1 ValueDefault=0 [code_labels_eol_after] @@ -865,7 +776,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=1 [code_len] @@ -876,7 +786,6 @@ Enabled=true MaxVal=2000 MinVal=8 -Value=99 ValueDefault=120 [code_remove_empty_lines] @@ -887,7 +796,6 @@ Enabled=true MaxVal=2000 MinVal=1 -Value=3 ValueDefault=2 [code_remove_return_paren] @@ -895,7 +803,6 @@ Description=Remove all parentheses around a return parameter EditorType=boolean TrueFalse=-code_remove_return_paren-|-no-code_remove_return_paren- -Value=0 ValueDefault=0 [code_split_bool_before] @@ -903,7 +810,6 @@ Description="Determine the aspect of boolean expressions when they must be split
because they are too long.
Example :
        -code_split_bool_before-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if
        (
            (A + main(func) + 6 > 60)
        &&  (B - 50 > 10)
        ||  var
        )
        {
        }

        -no-code_split_bool_before-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if
        (
            (A + main(func) + 6 > 60) &&
            (B - 50 > 10) ||
            var
        )
        {
        }
" EditorType=boolean TrueFalse=-code_split_bool_before-|-no-code_split_bool_before- -Value=0 ValueDefault=1 [code_split_decl_style] @@ -914,7 +820,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [code_split_fctcall_style] @@ -925,7 +830,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=1 ValueDefault=0 [code_split_fctdecl_style] @@ -936,7 +840,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=1 ValueDefault=0 [code_split_fctdef_style] @@ -947,7 +850,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=1 ValueDefault=0 [code_split_for_style] @@ -958,7 +860,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=1 ValueDefault=0 [code_split_if_style] @@ -969,7 +870,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=1 ValueDefault=0 [code_wizard_indent] @@ -977,7 +877,6 @@ Description="Indent code between to devstudio appwizard special comments.
Example :
        -code_wizard_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class   a
        {
        protected:
        //{{AFX_MSG(CDocument)
        enum a              <= has been touched
        {
            id = 0
        }
        afx_msg void    OnFileClose(void)
        afx_msg void    OnFileSave(void)
        afx_msg void    OnFileSaveAs(void)
        //}}AFX_MSG
        DECLARE_MESSAGE_MAP()
        }

        -no-code_wizard_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class   a
        {
        protected:
        //{{AFX_MSG(CDocument)
        enum a { id = 0 }          <= same as original file
        afx_msg void    OnFileClose(void)
        afx_msg void    OnFileSave(void)
        afx_msg void    OnFileSaveAs(void)
        //}}AFX_MSG
        DECLARE_MESSAGE_MAP()
        }

        Note(s) :
        - This option must be set to FALSE if you want to indent special
          appwizard headers with auto generated code. This is because touching
          that code can make appwizard fail to recognize its special marks.
        - This option can't be set in a source file with special comment
          /*$O */
" EditorType=boolean TrueFalse=-code_wizard_indent-|-no-code_wizard_indent- -Value=0 ValueDefault=1 [dependencies] @@ -985,7 +884,6 @@ Description="-d
ependencies- Activate/Deactivate the output of file dependencies.
        With -dependencies_all- Real dependencies will be computed (instead of
        just includes dependencies). This option takes much longer. but does a
        better job.

        -dependencies- is ignored if -dependencies_all- is set to TRUE.

        typical report
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Processing C:oulotCourcesndent.c   (136 lines. 3360 characters)
Processing ctype.h
** Warning: Unable to open source file ==> ctype.h
Processing malloc.h
** Warning: Unable to open source file ==> malloc.h
Processing stdlib.h
** Warning: Unable to open source file ==> stdlib.h
Processing string.h
** Warning: Unable to open source file ==> string.h
Processing config.h
Processing in.h
Processing grammar.h
Processing lexi.h
Processing error.h
Processing tools.h
Processing indent.h
Processing assert.h
** Warning: Unable to open source file ==> assert.h
- Includes files --------------------------------------------------------
(     1) #include config.h
(     2) #include in.h
(     1) #include grammar.h
(     2) #include lexi.h
(     1) #include error.h
(     1) #include tools.h
(     1) #include indent.h
******** Unresolved 5 Total 12
- Scanning   1 ----------------------------------------------------------
.
- Direct dependencies ---------------------------------------------------
(     1) #include config.h
(     3) #include in.h
(     8) #include lexi.h
(     5) #include tools.h
(    21) #include indent.h
******** Total 5
- No dependencies -------------------------------------------------------
(     1) #include grammar.h
Included by C:oulotCourcesndent.c
(     1) #include error.h
Included by C:oulotCourcesndent.c
******** Total 2
-------------------------------------------------------------------------
" EditorType=boolean TrueFalse=-dependencies-|-no-dependencies- -Value=0 ValueDefault=0 [dependencies_all] @@ -993,7 +891,6 @@ Description="-d
ependencies- Activate/Deactivate the output of file dependencies.
        With -dependencies_all- Real dependencies will be computed (instead of
        just includes dependencies). This option takes much longer. but does a
        better job.

        -dependencies- is ignored if -dependencies_all- is set to TRUE.

        typical report
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Processing C:oulotCourcesndent.c   (136 lines. 3360 characters)
Processing ctype.h
** Warning: Unable to open source file ==> ctype.h
Processing malloc.h
** Warning: Unable to open source file ==> malloc.h
Processing stdlib.h
** Warning: Unable to open source file ==> stdlib.h
Processing string.h
** Warning: Unable to open source file ==> string.h
Processing config.h
Processing in.h
Processing grammar.h
Processing lexi.h
Processing error.h
Processing tools.h
Processing indent.h
Processing assert.h
** Warning: Unable to open source file ==> assert.h
- Includes files --------------------------------------------------------
(     1) #include config.h
(     2) #include in.h
(     1) #include grammar.h
(     2) #include lexi.h
(     1) #include error.h
(     1) #include tools.h
(     1) #include indent.h
******** Unresolved 5 Total 12
- Scanning   1 ----------------------------------------------------------
.
- Direct dependencies ---------------------------------------------------
(     1) #include config.h
(     3) #include in.h
(     8) #include lexi.h
(     5) #include tools.h
(    21) #include indent.h
******** Total 5
- No dependencies -------------------------------------------------------
(     1) #include grammar.h
Included by C:oulotCourcesndent.c
(     1) #include error.h
Included by C:oulotCourcesndent.c
******** Total 2
-------------------------------------------------------------------------
" EditorType=boolean TrueFalse=-dependencies_all-|-no-dependencies_all- -Value=0 ValueDefault=0 [dependencies_dir] @@ -1002,7 +899,6 @@ Description="When -dependencies- option is activated. defines a path where GC
will find includes.
Example :
        -dependencies_dir-c:/system/includes
        -dependencies_dir-c:/GC/sources
" EditorType=string Enabled=false -Value=./ ValueDefault=./ [dependencies_dir_rec] @@ -1010,7 +906,6 @@ Description="Al
l directories set with -dependencies_dir- are recurs scan.

        See options(s) :
        [-no]-dependencies_dir-
" EditorType=boolean TrueFalse=-dependencies_dir_rec-|-no-dependencies_dir_rec- -Value=0 ValueDefault=0 [eol_unix] @@ -1018,7 +913,6 @@ Description=Unix format for carriage returns EditorType=boolean TrueFalse=-eol_unix-|-no-eol_unix- -Value=0 ValueDefault=0 [file_end_eol] @@ -1029,7 +923,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=1 ValueDefault=1 [overwrite_read_only] @@ -1037,7 +930,6 @@ Description=Process read only files (change status) EditorType=boolean TrueFalse=-overwrite_read_only-|-no-overwrite_read_only- -Value=1 ValueDefault=0 [pp_align_breakline] @@ -1045,7 +937,6 @@ Description="Al
ign (or not) breakline characters '' in macros.

        -pp_align_breakline-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

\t\t#define a(A)         
\t\t\tA += 2\t\t\t 
\t\t\tA = c(fonc) + 3 

        -no-pp_align_breakline-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

\t\t#define a(A) 
\t\t\tA += 2\t
\t\t\tA = c(fonc) + 3
" EditorType=boolean TrueFalse=-pp_align_breakline-|-no-pp_align_breakline- -Value=1 ValueDefault=0 [pp_align_to_code] @@ -1053,7 +944,6 @@ Description="Align or not PP directive to the code just below.
Example :
        -pp_align_to_code-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #define a   0
        void main(void)
        {
            #define a       0
            #define coucou  0
            #define coucou() 
                while(a) 
                { 
                    a = a + func(a) 
                }

            #if 0
            if(a) a++
            #endif
        }

        -no-pp_align_to_code-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #define a   0
        void main(void)
        {
        #define a       0
        #define coucou  0
        #define coucou() 
            while(a) 
            { 
                a = a + func(a) 
            }

        #if 0
            if(a) a++
        #endif
        }

        Note(s) :
        - This option can't be used in source file file special comment /*$O*/.
" EditorType=boolean TrueFalse=-pp_align_to_code-|-no-pp_align_to_code- -Value=1 ValueDefault=0 [pp_include_unix] @@ -1061,7 +951,6 @@ Description="Change '' to '/' in an include expression.
Example :
        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #include gll.h
        #include 

        -pp_include_unix-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #include gl/gl.h
        #include 

        -no-pp_include_unix-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #include gll.h
        #include
" EditorType=boolean TrueFalse=-pp_include_unix-|-no-pp_include_unix- -Value=1 ValueDefault=1 [pp_style] @@ -1072,7 +961,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [replace] @@ -1081,7 +969,6 @@ Description="GC will replace all occurrences of by
.
-replace_on- option must be enabled.
Example :
        -replace-int$uint
        -replace-a$variable

        before
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int a
        int     b

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        uint    variable
        uint    b

        See options(s) :
        [-no]-replace_on-
" EditorType=string Enabled=false -Value=$ ValueDefault=$ [replace_on] @@ -1089,7 +976,6 @@ Description="Ac
tivate/disactivate the word replacement mode.

        See options(s) :
        -replace-$
" EditorType=boolean TrueFalse=-replace_on-|-no-replace_on- -Value=0 ValueDefault=1 [space_affect_style] @@ -1100,7 +986,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [space_autoaffect_style] @@ -1111,7 +996,6 @@ Enabled=true MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [space_cast] @@ -1119,7 +1003,6 @@ Description="Add spaces after '(' and before ')' for cast operators.
Example :
        -space_cast-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(( int * ) b)
        {
        }

        return ( int * ) b

        -no-space_cast-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if((int *) b)
        {
        }

        return (int *) b

        See option(s) :
        -space_paren-
" EditorType=boolean TrueFalse=-space_cast-|-no-space_cast- -Value=1 ValueDefault=0 [space_cast_after] @@ -1127,7 +1010,6 @@ Description="Add a space after a cast expression.
Example :
        -space_cast_after-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if((int *) b)
        {
        }

        return ( int * ) b

        -no-space_cast_after-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if((int *)b)
        {
        }

        return (int *)b

        See option(s) :
        [-no]-space_cast-
" EditorType=boolean TrueFalse=-space_cast_after-|-no-space_cast_after- -Value=1 ValueDefault=1 [space_fctcall] @@ -1135,7 +1017,6 @@ Description="Output a blank character before the open parenthese of a function call.
Example :
        -space_fctcall-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call (out)
        loop (100)

        -no-space_fctcall-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100)
" EditorType=boolean TrueFalse=-space_fctcall-|-no-space_fctcall- -Value=1 ValueDefault=0 [space_fctcall_firstparam] @@ -1143,7 +1024,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctcall_firstparam-|-no-space_fctcall_firstparam- -Value=1 ValueDefault=0 [space_fctcall_inparam] @@ -1151,7 +1031,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctcall_inparam-|-no-space_fctcall_inparam- -Value=1 ValueDefault=1 [space_fctcall_lastparam] @@ -1159,7 +1038,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctcall_lastparam-|-no-space_fctcall_lastparam- -Value=1 ValueDefault=0 [space_fctdecl] @@ -1167,7 +1045,6 @@ Description="Output a blank character before the open parenthese of a function
definition / declaration.
Example :
        -space_fctdecl-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        extern func (a)

        -space_fctdef-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int func (a)
        {
        }

        -no-space_fctdef-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int func(a)
        {
        }
" EditorType=boolean TrueFalse=-space_fctdecl-|-no-space_fctdecl- -Value=1 ValueDefault=0 [space_fctdecl_firstparam] @@ -1175,7 +1052,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctdecl_firstparam-|-no-space_fctdecl_firstparam- -Value=1 ValueDefault=0 [space_fctdecl_lastparam] @@ -1183,7 +1059,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctdecl_lastparam-|-no-space_fctdecl_lastparam- -Value=1 ValueDefault=0 [space_fctdef] @@ -1191,7 +1066,6 @@ Description="Output a blank character before the open parenthese of a function
definition / declaration.
Example :
        -space_fctdecl-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        extern func (a)

        -space_fctdef-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int func (a)
        {
        }

        -no-space_fctdef-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        int func(a)
        {
        }
" EditorType=boolean TrueFalse=-space_fctdef-|-no-space_fctdef- -Value=1 ValueDefault=0 [space_fctdef_firstparam] @@ -1199,7 +1073,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctdef_firstparam-|-no-space_fctdef_firstparam- -Value=1 ValueDefault=0 [space_fctdef_lastparam] @@ -1207,7 +1080,6 @@ Description="Output a blank character before the first/last/inside parameter of a function
\t\tcall. definition or declaration.
Example :
        -space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1. 2. 3. 4)

        -no-space_fctcall_inparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(1.2.3.4)

        -space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call( out)
        loop( 100. 200)

        -no-space_fctcall_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        main_call(out)
        loop(100. 200)

        -space_fctdef_firstparam-
        -space_fctdef_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out )
        {
        }

        -space_fctdecl_firstparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call( int out. int in)

        -space_fctdecl_lastparam-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main_call(int out. int in )
" EditorType=boolean TrueFalse=-space_fctdef_lastparam-|-no-space_fctdef_lastparam- -Value=1 ValueDefault=0 [space_if] @@ -1215,7 +1087,6 @@ Description="Output a blank character after if. while. for and switch keywords.
Example :
        -space_if-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if (a)
        {
            while (a--)
            {
            }
        }

        -no-space_if-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a)
        {
            while(a--)
            {
            }
        }
" EditorType=boolean TrueFalse=-space_if-|-no-space_if- -Value=1 ValueDefault=0 [space_paren] @@ -1226,7 +1097,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=3 ValueDefault=0 [space_return] @@ -1234,7 +1104,6 @@ Description="Output a blank character after return if return is followed by an open
parenthesis.
Example :
        -space_return-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        return (6)

        -no-space_return-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        return(6)
" EditorType=boolean TrueFalse=-space_return-|-no-space_return- -Value=1 ValueDefault=0 [space_scope_access] @@ -1242,7 +1111,6 @@ Description="Add a space before and after the scope resolution operator '::' when
accessing a static method.
Example :
        -space_scope_access-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void func::Ping(void)
        {
            Base :: Ping()
            Base :: Pong()
        }

        -no-space_scope_access-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void func::Ping(void)
        {
            Base::Ping()
            Base::Pong()
        }

        See option(s) :
        [-no]-space_scope_def-
" EditorType=boolean TrueFalse=-space_scope_access-|-no-space_scope_access- -Value=1 ValueDefault=0 [space_scope_def] @@ -1250,7 +1118,6 @@ Description="Add a space before and after the scope resolution operator '::' in the
function definition.
Example :
        -space_scope_def-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void func :: Ping(void)
        {
        }

        -no-space_scope_def-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void func::Ping(void)
        {
        }

        See option(s) :
        [-no]-space_scope_access-
" EditorType=boolean TrueFalse=-space_scope_def-|-no-space_scope_def- -Value=1 ValueDefault=0 [stmt_brace_style] @@ -1261,7 +1128,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=2 ValueDefault=0 [stmt_brace_style_class] @@ -1272,7 +1138,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=2 ValueDefault=0 [stmt_brace_style_decl] @@ -1283,7 +1148,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=2 ValueDefault=0 [stmt_brace_style_fct] @@ -1294,7 +1158,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=2 ValueDefault=0 [stmt_break_alone] @@ -1302,7 +1165,6 @@ Description="Force an empty statement to be alone on its line.
Example :
        -stmt_break_alone-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        for(a = 0 a < 10 a++)
            

        -no-stmt_break_alone-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        for(a = 0 a < 10 a++)

        Note(s) :
        - Concerns if. while. for and switch statements.
" EditorType=boolean TrueFalse=-stmt_break_alone-|-no-stmt_break_alone- -Value=1 ValueDefault=0 [stmt_break_dowhile] @@ -1310,7 +1172,6 @@ Description="Force a break line before the while of a do...while statement.
Example :
\t\t-stmt_break_dowhile-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

\t\tdo
\t\t{
\t\t\t...
\t\t} 
\t\twhile(1)

\t\t-no-stmt_break_dowhile-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

\t\tdo
\t\t{
\t\t\t...
\t\t} while(1)
" EditorType=boolean TrueFalse=-stmt_break_dowhile-|-no-stmt_break_dowhile- -Value=1 ValueDefault=0 [stmt_class_indent] @@ -1321,7 +1182,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=0 [stmt_concat_else_2_stmt] @@ -1329,7 +1189,6 @@ Description="Put the else on the same line as the previous statement.
Example :
        -stmt_concat_else_2_stmt-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a)
        {
        } else
        {
        }

        -no-stmt_concat_else_2_stmt-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a)
        {
        } 
        else
        {
        }
" EditorType=boolean TrueFalse=-stmt_concat_else_2_stmt-|-no-stmt_concat_else_2_stmt- -Value=0 ValueDefault=0 [stmt_concat_else_if] @@ -1337,7 +1196,6 @@ Description="Close up any gap between else and if in else ... ifstructures.
Example :
        -stmt_concat_else_if-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(foo) 
\t\t{
        } 
\t\telse if(bar) 
\t\t{
        }

        -no-stmt_concat_else_if-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(foo) 
\t\t{
        } else
        if(bar) 
\t\t{
        }
" EditorType=boolean TrueFalse=-stmt_concat_else_if-|-no-stmt_concat_else_if- -Value=1 ValueDefault=1 [stmt_concat_enum] @@ -1345,7 +1203,6 @@ Description="Concat content of enum if possible.
Example :
        -stmt_concat_enum-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        enum a
        {
            id1.
            id2
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        enum a { id1. id2 }
" EditorType=boolean TrueFalse=-stmt_concat_enum-|-no-stmt_concat_enum- -Value=0 ValueDefault=1 [stmt_concat_if] @@ -1353,7 +1210,6 @@ Description="Try to output if. while or for expression on a single line if the
length of the statement is not too long.
Example :
        -stmt_concat_if-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        while(a && b)
            a = b + 6
        if(a)
            a++
        if(b)
        {
            b++
        }


        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        while(a && b) a = b + 6
        if(a) a++
        if(b)
        {
            b++
        }

        See options(s) :
        -code_len-

        Note(s) :
        - This option does not modify statements with { }.
" EditorType=boolean TrueFalse=-stmt_concat_if-|-no-stmt_concat_if- -Value=0 ValueDefault=1 [stmt_concat_if_and_else] @@ -1361,7 +1217,6 @@ Description="Try to output if ... else expression on two lines - if possible...
Example :
        -stmt_concat_if_and_else-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a)
            a++
        else
            b++

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a) a++
        else b++

        See options(s) :
        -code_len-

        Note(s) :
        - This option does not modify statements with { }.
" EditorType=boolean TrueFalse=-stmt_concat_if_and_else-|-no-stmt_concat_if_and_else- -Value=0 ValueDefault=0 [stmt_concat_if_remove_empty] @@ -1369,7 +1224,6 @@ Description="Remove empty lines between concat if/while/for.
Example :
        -stmt_concat_if_remove_empty-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a) a++
                        <= Empty line
                        <= Empty line
        if(b) b = b + a

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        if(a) a++
        if(b) b = b + a

        See option(s) :
        [-no]-stmt_concat_if- to concat if/while/for expressions if possible.
" EditorType=boolean TrueFalse=-stmt_concat_if_remove_empty-|-no-stmt_concat_if_remove_empty- -Value=0 ValueDefault=1 [stmt_concat_inline_class] @@ -1377,7 +1231,6 @@ Description="Concat if possible inline function body inside a class.
Example :
        -stmt_concat_inline_class-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class a
        {
            int previous(int a)
            {
                return a - 1
            }
            int next(int a)
            {
                return a + 1
            }
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        class   a
        {
            int previous(int a) { return a - 1 }
            int next(int a)     { return a + 1 }
        }

        See options(s) :
        -code_len-
" EditorType=boolean TrueFalse=-stmt_concat_inline_class-|-no-stmt_concat_inline_class- -Value=0 ValueDefault=1 [stmt_concat_macros] @@ -1385,7 +1238,6 @@ Description="Concat a macro body if possible.
Example :
        -stmt_concat_macros-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #define macro()
        {
            a = a + 18 - b
            if(!a) return 10
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        #define macro() { a = a + 18 - b if(!a) return 10 }
" EditorType=boolean TrueFalse=-stmt_concat_macros-|-no-stmt_concat_macros- -Value=0 ValueDefault=1 [stmt_concat_switch] @@ -1393,7 +1245,6 @@ Description="Concat all cases of a switch if possible. Empty lines are removed if
\t\tconcatenation is done.
Example :
        -stmt_concat_switch-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        switch(a)
        {
        case 10:
            break

        case 11:
            a = a + 6 return a

        case 12:
            if(a) a++
            break
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        switch(a)
        {
        case 10:    break
        case 11:    a = a + 6 return a
        case 12:    if(a) a++ break
        }
" EditorType=boolean TrueFalse=-stmt_concat_switch-|-no-stmt_concat_switch- -Value=0 ValueDefault=1 [stmt_decl_remove_empty] @@ -1401,7 +1252,6 @@ Description="Remove empty lines in declaration statements.
Example :
        -stmt_decl_remove_empty-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a
                        <= Empty line
            int b
            int c

            a = b = c = 0
        }

        after
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void main(void)
        {
            int a
            int b
            int c

            a = b = c = 0
        }
" EditorType=boolean TrueFalse=-stmt_decl_remove_empty-|-no-stmt_decl_remove_empty- -Value=0 ValueDefault=1 [stmt_extern_c_indent] @@ -1409,7 +1259,6 @@ Description="Indent one level an extern Cstatement.
Example :
        -no-stmt_extern_c_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        extern C
        {
        int a(void)
        {
        }
        }

        -stmt_extern_c_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        extern C
        {
            int a(void)
            {
            }
        }
" EditorType=boolean TrueFalse=-stmt_extern_c_indent-|-no-stmt_extern_c_indent- -Value=1 ValueDefault=0 [stmt_force_brace] @@ -1420,7 +1269,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=1 ValueDefault=100 [stmt_namespace_indent] @@ -1428,7 +1276,6 @@ Description="Indent one level a namespace statement.
Example :
        -no-stmt_namespace_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        namespace com
        {
        int a(void)
        {
        }
        }

        -stmt_namespace_indent-
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        namespace com
        {
            int a(void)
            {
            }
        }
" EditorType=boolean TrueFalse=-stmt_namespace_indent-|-no-stmt_namespace_indent- -Value=1 ValueDefault=0 [stmt_static_init_len] @@ -1439,7 +1286,6 @@ Enabled=true MaxVal=2000 MinVal=0 -Value=0 ValueDefault=80 [stmt_static_init_style] @@ -1450,7 +1296,6 @@ Enabled=true MaxVal=3 MinVal=0 -Value=2 ValueDefault=0 [stmt_switch_eol] @@ -1461,7 +1306,6 @@ Enabled=true MaxVal=1 MinVal=0 -Value=1 ValueDefault=0 [stmt_switch_style] @@ -1472,7 +1316,6 @@ Enabled=true MaxVal=5 MinVal=0 -Value=4 ValueDefault=0 [tab_out] @@ -1480,7 +1323,6 @@ Description=Output tab characters instead of spaces EditorType=boolean TrueFalse=-tab_out-|-no-tab_out- -Value=0 ValueDefault=1 [tab_size] @@ -1491,7 +1333,6 @@ Enabled=true MaxVal=2000 MinVal=1 -Value=4 ValueDefault=4 [token_ext] @@ -1500,5 +1341,4 @@ Description="Tell GC to consider the user keyword as the given C/C++ keyword.
Example :
        -token_ext-typedef$tt
        => tt has the same meaning as typedef

        -token_ext-extern$extern_all
        => extern_all has the same meaning as extern

        -token_ext-int$uint8
        -token_ext-int$uint16
        => uint8 and uint16 are some types (same as int).

        GC knows special keywordsyou can specify as a C/C++ keyword.
        GC will indent the corresponding source file word depending of the
        special word :

        -token_ext-single_word$tt
            tt will be alone on a line. Indent at the correct indentation
            level.

        -token_ext-single_word_0$tt
            tt will be alone on a line. and at column 0.

        Example :        -token_ext-single_word_0$WORD
        -token_ext-single_word_0$WORD1
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        void a(int b)
        {
            if(b)
            {
        WORD
                b++
        WORD1
            }
        }
" EditorType=string Enabled=false -Value= ValueDefault= diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_hindent.ini --- a/indenters/uigui_hindent.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_hindent.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description="Forces all tags to lowercase. By default, hindent forces all tags to uppercase." EditorType=boolean TrueFalse=-c| -Value=0 ValueDefault=0 @@ -30,7 +29,6 @@ Description="Prints just tags without any data between the tags. Damages the HTML in a big way, so save a copy of your original HTML. This option helps you follow the HTML code flow visually." EditorType=boolean TrueFalse=-f| -Value=0 ValueDefault=0 [Indent level] @@ -41,7 +39,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=4 ValueDefault=4 [List tags] @@ -49,7 +46,6 @@ Description="Causes hindent to print a complete list of tags that it recognizes to stdout, and exits." EditorType=boolean TrueFalse=-l| -Value=0 ValueDefault=0 [Strict] @@ -57,7 +53,6 @@ Description="Multiple tags per line are broken out onto separate lines. Can damage the HTML in minor ways by drawing an extra space character in certain parts of the web page, so save a copy of your original HTML. This option helps you follow the HTML code flow visually, especially with computer-generated HTML that comes out all on one line." EditorType=boolean TrueFalse=-s| -Value=0 ValueDefault=0 [Tab stop] @@ -68,5 +63,4 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=4 ValueDefault=8 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_htb.ini --- a/indenters/uigui_htb.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_htb.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description="

The -a command-line option causes all tags containing more that one attribute to be broken over multiple lines, each with a single attribute. The attributes are aligned vertically with the first attribute. A similar attribute break will occur by default, but only on tags exceeding the column 80 limit, and each line may contain more than one attribute.

Before:

<BODY BGCOLOR="#FFFFFF" MARGINWIDTH="0" MARGINHEIGHT="0" LINK="#666666" VLINK="#666666" ALINK="#000000">\n<TABLE WIDTH="800" BORDER="0" CELLPADDING="0" CELLSPACING="0">\n<TR>\n<TD COLSPAN="2" WIDTH="196" BGCOLOR="cccccc" VALIGN="top"><IMG SRC="/images/homepage/rev/logo_06.gif" WIDTH="196" HEIGHT="63"></TD>\n<TD BGCOLOR="cccccc" WIDTH="600" VALIGN="top">\n<TABLE WIDTH="600" BORDER="0" CELLPADDING="0" CELLSPACING="0" VALIGN="top">\n<TR>\n<TD VALIGN="top" HEIGHT="17" BGCOLOR="#CCCCCC"><IMG SRC="/images/homepage/rev/comp8_07.gif" WIDTH="600" HEIGHT="17"></TD>\n</TR>
After: 
<BODY ALINK="#000000"\n      BGCOLOR="#FFFFFF"\n      LINK="#666666"\n      MARGINHEIGHT="0"\n      MARGINWIDTH="0"\n      VLINK="#666666">\n<TABLE BORDER="0"\n       CELLPADDING="0"\n       CELLSPACING="0"\n       WIDTH="800">\n   <TR>\n      <TD BGCOLOR="cccccc"\n          COLSPAN="2"\n          VALIGN="top"\n          WIDTH="196"><IMG HEIGHT="63"\n                           SRC="/images/homepage/rev/logo_06.gif"\n                           WIDTH="196"></TD>\n      <TD BGCOLOR="cccccc"\n          VALIGN="top"\n          WIDTH="600"> \n         <TABLE BORDER="0"\n                CELLPADDING="0"\n                CELLSPACING="0"\n                VALIGN="top"\n                WIDTH="600">\n            <TR>\n               <TD BGCOLOR="#CCCCCC"\n                   HEIGHT="17"\n                   VALIGN="top"><IMG HEIGHT="17"\n                                    SRC="/images/homepage/rev/comp8_07.gif"\n                                    WIDTH="600"></TD>\n            </TR>
" EditorType=boolean TrueFalse=-a| -Value=0 ValueDefault=0 @@ -30,7 +29,6 @@ Description="

The -b command-line option causes all tag attributes to be broken on succeeding lines. The attributes are aligned vertically with the last character in the tag name.

Before:

<BODY BGCOLOR="#FFFFFF" MARGINWIDTH="0" MARGINHEIGHT="0" LINK="#666666" VLINK="#666666" ALINK="#000000">\n<TABLE WIDTH="800" BORDER="0" CELLPADDING="0" CELLSPACING="0">\n<TR>\n<TD COLSPAN="2" WIDTH="196" BGCOLOR="cccccc" VALIGN="top"><IMG SRC="/images/homepage/rev/logo_06.gif" WIDTH="196" HEIGHT="63"></TD>\n<TD BGCOLOR="cccccc" WIDTH="600" VALIGN="top">\n<TABLE WIDTH="600" BORDER="0" CELLPADDING="0" CELLSPACING="0" VALIGN="top">\n<TR>\n<TD VALIGN="top" HEIGHT="17" BGCOLOR="#CCCCCC"><IMG SRC="/images/homepage/rev/comp8_07.gif" WIDTH="600" HEIGHT="17"></TD>\n</TR>
After:
<BODY\n    ALINK="#000000"\n    BGCOLOR="#FFFFFF"\n    BOTMARGIN="0"\n    MARGINHEIGHT="0"\n    MARGINWIDTH="0"\n    LEFTMARGIN="0"\n    LINK="#666666"\n    TOPMARGIN="0"\n    VLINK="#666666">\n<TABLE\n     BORDER="0"\n     CELLPADDING="0"\n     CELLSPACING="0"\n     WIDTH="800">\n   <TR>\n      <TD\n        BGCOLOR="cccccc"\n        COLSPAN="2"\n        VALIGN="top"\n        WIDTH="196"><IMG\n                       HEIGHT="63"\n                       SRC="/images/homepage/rev/logo_06.gif"\n                       WIDTH="196"></TD>\n      <TD\n        BGCOLOR="cccccc"\n        VALIGN="top"\n        WIDTH="600"> \n         <TABLE\n              BORDER="0"\n              VALIGN="top"\n              CELLPADDING="0"\n              CELLSPACING="0"\n              WIDTH="600">\n            <TR>\n               <TD\n                 BGCOLOR="#CCCCCC"\n                 HEIGHT="17"\n                 VALIGN="top"><IMG\n                                HEIGHT="17"\n                                SRC="/images/homepage/rev/comp8_07.gif"\n                                WIDTH="600"></TD>\n            </TR>\n
" EditorType=boolean TrueFalse=-b| -Value=0 ValueDefault=0 [Add Carriage Returns] @@ -38,7 +36,6 @@ Description="The -c command-line option adds an extra carriage return character to each output line of reformatted data. This allows Unix versions of HTB to create a DOS/Windows compatible text files directly." EditorType=boolean TrueFalse=-c| -Value=0 ValueDefault=0 [Omit Carriage Returns] @@ -46,7 +43,6 @@ Description="The -d command-line option inhibits extra carriage return character output even if present in the source data. This allows the Windows version of HTB to create a Unix compatible text file directly. This is the default behavior and correctly creates a natively compatible format whether Unix or Windows." EditorType=boolean TrueFalse=-d| -Value=0 ValueDefault=0 [Escaped Tag Conversion] @@ -54,7 +50,6 @@ Description="The -e command-line option replaces the special markup characters '<', '>', and '&' with escape strings '<', '>', and '&' respectively. Also, the tag sequence '
' is added to the beginning of the output data and the sequence '
' is appended to the end of the data. This creates an entirely new HTML document, which when viewed with a Web Browser, will appear as source instead of normal rendering. This is useful in creating markup tag documentation and is the mechanism used to create the examples in this document. Use in combination with the -k option to do the conversion without applying other reformatting options." EditorType=boolean TrueFalse=-e| -Value=0 ValueDefault=0 [Join Lines - Compress Output] @@ -62,7 +57,6 @@ Description="The -j command-line option removes all unnecessary whitespace & comments and joins the output lines together whenever possible. The result is totally 'unbeautified' output, but the size will be reduced from 10-40% for quicker transfer over the network. Use this option whenever performance is more important than readability." EditorType=boolean TrueFalse=-j| -Value=0 ValueDefault=0 [Keep Layout - Case Changes Only] @@ -70,7 +64,6 @@ Description="

When the current indenting and appearance of your tagged document is acceptable, the -k command-line option may be used to change only the case of the tag names and attributes with no other changes applied.

Example:

- Keep the current layout of an HTML document, but change the tag attribute names to lower case (-m option, opposite of tag name case which by default is upper)...

htb -km myfile.html

Before:
<FORM ENCTYPE="multipart/form-data" NAME="coreform" METHOD="POST">\n<INPUT TYPE="submit" VALUE="Submit Request"> \n<INPUT NAME="cgi" TYPE="button" VALUE="cgi2xml">cgi2xml \n<TABLE BORDER="5" CELLPADDING="5">\n   <TR>\n      <TD> <FONT COLOR="purple"> \n         <H4>Output formatting:</H4> </FONT>Debug: \n         <INPUT NAME="debug"><BR> \n         <BR> Filter: \n         <INPUT NAME="filter"><BR> Output: \n         <INPUT NAME="output"><BR> \n         <BR> Pagestart: \n         <INPUT SIZE="4" NAME="pagestart"><BR> Pagesize: \n         <INPUT SIZE="4" NAME="pagesize"><BR> \n      </TD>\n   </TR>\n</TABLE>\n</FORM>
After:
<FORM enctype="multipart/form-data" name="coreform" method="POST">\n<INPUT type="submit" value="Submit Request"> \n<INPUT name="cgi" type="button" value="cgi2xml">cgi2xml \n<TABLE border="5" cellpadding="5">\n   <TR>\n      <TD> <FONT color="purple"> \n         <H4>Output formatting:</H4> </FONT>Debug: \n         <INPUT name="debug"><BR> \n         <BR> Filter: \n         <INPUT name="filter"><BR> Output: \n         <INPUT name="output"><BR> \n         <BR> Pagestart: \n         <INPUT size="4" name="pagestart"><BR> Pagesize: \n         <INPUT size="4" name="pagesize"><BR> \n      </TD>\n   </TR>\n</TABLE>\n</FORM>
" EditorType=boolean TrueFalse=-k| -Value=0 ValueDefault=0 [Tag Names Lower Case] @@ -78,7 +71,6 @@ Description="

The -l command-line option changes all HTML tag names and their attributes to lower case. Combine with the -m (mixed case) option to keep the tag names lower case, but make the attribute names upper case.

Before:

<FORM ENCTYPE="multipart/form-data" NAME="coreform" METHOD="POST">\n<INPUT TYPE="submit" VALUE="Submit Request"> \n<INPUT NAME="cgi" TYPE="button" VALUE="cgi2xml">cgi2xml \n<TABLE BORDER="5" CELLPADDING="5">\n   <TR>\n      <TD> <FONT COLOR="purple"> \n         <H4>Output formatting:</H4> </FONT>Debug: \n         <INPUT NAME="debug"><BR> \n         <BR> Filter: \n         <INPUT NAME="filter"><BR> Output: \n         <INPUT NAME="output"><BR> \n         <BR> Pagestart: \n         <INPUT SIZE="4" NAME="pagestart"><BR> Pagesize: \n         <INPUT SIZE="4" NAME="pagesize"><BR> \n      </TD>\n   </TR>\n</TABLE>\n</FORM>
After:
<form enctype="multipart/form-data" method="post" name="coreform">\n<input type="submit" value="Submit Request"> \n<input name="cgi" type="button" value="cgi2xml">cgi2xml \n<table border="5" cellpadding="5">\n   <tr>\n      <td> <font color="purple"> \n         <h4>Output formatting:</h4> </font>Debug: \n         <input name="debug"><br> \n         <br> Filter: \n         <input name="filter"><br> Output: \n         <input name="output"><br> \n         <br> Pagestart: \n         <input name="pagestart" size="4"><br> Pagesize: \n         <input name="pagesize size="4"><br> \n      </td>\n   </tr>\n</table>\n</form>\n
" EditorType=boolean TrueFalse=-l| -Value=0 ValueDefault=0 [Tag Attributes Opposite Case] @@ -86,7 +78,6 @@ Description="The -m command-line option makes the tag attribute case the opposite of the tag name. Since the HTB default is to make tag names upper case, the addition of this option will make the tag attributes lower case. If combined with the -l option (lower case) the tag names will be lower case, and the tag attributes will be upper case. See the -k option for an example." EditorType=boolean TrueFalse=-m| -Value=0 ValueDefault=0 [Never Break Tags Between Lines] @@ -94,7 +85,6 @@ Description="The -n command-line option cancels the default behavior of breaking tags which exceed the 80 column limit and keeps tags intact within a single line of output regardless of their length. This is often desirable, especially on XSL files." EditorType=boolean TrueFalse=-n| -Value=0 ValueDefault=0 [Remove Non-HTML Tags] @@ -102,7 +92,6 @@ Description="

The -r command-line option strips any tag which is not part of the HTML 4.01 specification (and a group of widely recognized, commonly used legacy tags) from the output. Its a convenient way to separate HTML from hybrid files like ASP, JSP, XSL or files containing custom tags. The stripped tags are reported along with any errors to "standard error".

Example:

- Remove all non-HTML tags from an XSL/XHTML file...

htb -r myfile.xsl

Before:
\n   <xsl:for-each select="ELEMENT/NODE1"> \n      <xsl:variable select="position()-1" name="vpos" /> \n      <TR VALIGN="top">\n         <TD ALIGN="center"><FONT SIZE="1" FACE="Helvetica"><xsl:value-of select="$vpos" /></FONT> \n         </TD>\n         <TD ALIGN="center"><FONT FACE="Helvetica"> \n            <INPUT NAME="ELEM{$vpos}" TYPE="text" VALUE="Element {$vpos}" /></FONT> \n         </TD>\n         <TD ALIGN="center"><FONT FACE="Helvetica"> \n            <INPUT NAME="NUMB{$vpos}" TYPE="text" VALUE="2" /></FONT> \n         </TD>\n         <TD ALIGN="center"><FONT FACE="Helvetica"> \n            <xsl:variable select="count(//NODE1[@id &gt; -1)" name="pcnt" /> \n            <xsl:variable name="selsize"> \n               <xsl:choose><xsl:when test="$pcnt &lt; 5"> \n                  <xsl:value-of select="$pcnt" /> \n               </xsl:when><xsl:otherwise> \n                  <xsl:value-of select="'5'" /> \n               </xsl:otherwise></xsl:choose> \n            </xsl:variable> \n            <SELECT SIZE="{$selsize}" NAME="VALU{$vpos}">\n               <xsl:for-each select="//VALUE[@id &gt; -1]"> \n                  <OPTION VALUE="{@id}">\n                  <xsl:value-of select="NAME" /></OPTION> \n               </xsl:for-each> \n            </SELECT></FONT> \n         </TD>\n      </TR>\n   </xsl:for-each>
After: 
\n   <TR VALIGN="top">\n      <TD ALIGN="center"><FONT FACE="Helvetica" SIZE="1"></FONT> \n      </TD>\n      <TD ALIGN="center"><FONT FACE="Helvetica"> \n         <INPUT NAME="ELEM{$vpos}" TYPE="text" VALUE="Element {$vpos}" /></FONT> \n      </TD>\n      <TD ALIGN="center"><FONT FACE="Helvetica"> \n         <INPUT NAME="NUMB{$vpos}" TYPE="text" VALUE="2" /></FONT> \n      </TD>\n      <TD ALIGN="center"><FONT FACE="Helvetica"> \n         <SELECT NAME="VALU{$vpos}" SIZE="{$selsize}">\n            <OPTION VALUE="{@id}"></OPTION>\n         </SELECT></FONT> \n      </TD>\n   </TR>
" EditorType=boolean TrueFalse=-r| -Value=0 ValueDefault=0 [Remove Tabs from SCRIPTs] @@ -110,7 +99,6 @@ Description="HTB automatically removes any tab characters found in the source document during the indenting process, but by default SCRIPTs are kept intact. To completely remove all tabs, specify the -s option and tab characters found within SCRIPT elements will be replaced with sets if of indented spaces. This could make the indented script statements look slightly worse and may require minor editing, but the beautified output is clear of any tab characters." EditorType=boolean TrueFalse=-r| -Value=0 ValueDefault=0 [Convert to Plain Text] @@ -118,7 +106,6 @@ Description="The -t command-line option strips all markup tags, comments and converts the input to plain text. All ASCII and ISO8859-1 HTML escape strings are converted back to the characters they represent. An attempt is made to compress extra whitespace, but in general the text will require additional re-formatting to be made presentable. Use this option to isolate the textual content within tagged documents (not necessarily HTML) for use in other documentation." EditorType=boolean TrueFalse=-t| -Value=0 ValueDefault=0 [Tag Names Upper Case] @@ -126,7 +113,6 @@ Description="

The -u command-line option changes all HTML tag names and their attributes to upper case. Since this is the default behavior of HTB, it is not required. Use the -m (mixed case) option to keep the tag names upper case, but make the attribute names lower case.

Before:

<form enctype="multipart/form-data" name="coreform" method="POST">\n<input type="submit" value="Submit Request"> \n<input name="cgi" type="button" value="cgi2xml">cgi2xml \n<table border="5" cellpadding="5">\n   <tr>\n      <td> <font color="purple"> \n         <h4>Output formatting:</h4> </font>Debug: \n         <input name="debug"><br> \n         <br> Filter: \n         <input name="filter"><br> Output: \n         <input name="output"><br> \n         <br> Pagestart: \n         <input size="4" name="pagestart"><br> Pagesize: \n         <input size="4" name="pagesize"><br> \n      </td>\n   </tr>\n</table>\n</form>
After:
<FORM ENCTYPE="multipart/form-data" METHOD="POST" NAME="coreform">\n<INPUT TYPE="submit" VALUE="Submit Request"> \n<INPUT NAME="cgi" TYPE="button" VALUE="cgi2xml">cgi2xml \n<TABLE BORDER="5" CELLPADDING="5">\n   <TR>\n      <TD> <FONT COLOR="purple"> \n         <H4>Output formatting:</H4> </FONT>Debug: \n         <INPUT NAME="debug"><BR> \n         <BR> Filter: \n         <INPUT NAME="filter"><BR> Output: \n         <INPUT NAME="output"><BR> \n         <BR> Pagestart: \n         <INPUT NAME="pagestart" SIZE="4"><BR> Pagesize: \n         <INPUT NAME="pagesize" SIZE="4"><BR> \n      </TD>\n   </TR>\n</TABLE>\n</FORM>
" EditorType=boolean TrueFalse=-u| -Value=0 ValueDefault=0 [Unknown Tags are XML] @@ -134,7 +120,6 @@ Description="

HTB automatically detects XML compliant files and is able to apply reformatting to unknown tags since they meet the predictable behavior of the XML specification. If the input document is not strictly XML compliant, but does contain custom tagging which may be considered "well-formed" XML, the -x option may be used to apply XML handling on these otherwise ignored tags. If XML is detected, either automatically, or with the -x option, the tag case is NOT changed for these non-HTML tags, since they are often case-sensitive. Also, the attributes of unknown tags will remain in original order instead of being sorted as with HTML attributes. To turn off XML auto-detection and apply case changes and attribute sorting to all tags known and unknown, use the -y option.

Example:

- Make tag names and attributes lower case, never break tags, and treat unknown tags in an HTML file as well formed XML...

htb -lnx myfile.html

Before:
<TR><TD WIDTH=182 ALIGN=left BGCOLOR="#ffffff">\n<NYT_HEADLINE>\n<A\n\nHREF="/onthisday/20020619.html"><FONT SIZE="3" FACE="times"><B>On June 19 ...<BR></B></FONT></A>\n</NYT_HEADLINE>\n<NYT_BYLINE>\n<FONT SIZE="-1"></FONT>\n</NYT_BYLINE>\n<NYT_SUMMARY>\n<FONT SIZE="-1">\n<B>1964:</B> The Civil Rights Act of 1964 was approved.   (<A \nHREF="/onthisday/big/0619.html">See this front page.</A>) <BR>\n<B>1903:</B> Lou Gehrig was born.  <A \nHREF="/onthisday/bday/0619.html">(Read about his life.)</A> <BR>\n<B>1886:</B> Harper's Weekly featured a cartoon about the proposed annexation of Nova Scotia. <A \nHREF="/onthisday/harp/0619.html">(See the cartoon.)</A></FONT>\n</TD></TR>
After:
<tr>\n   <td align="left" bgcolor="#ffffff" width="182"> \n      <NYT_HEADLINE> \n         <a href="/onthisday/20020619.html"><font face="times" size="3"><b>On June 19 ...<br></b></font></a> \n      </NYT_HEADLINE> \n      <NYT_BYLINE> <font size="-1"></font> \n      </NYT_BYLINE> \n      <NYT_SUMMARY> <font size="-1"> <b>1964:</b> The Civil Rights Act of 1964 was approved. (<a href="/onthisday/big/0619.html">See this front page.</a>) \n         <br> <b>1903:</b> Lou Gehrig was born. \n         <a href="/onthisday/bday/0619.html">(Read about his life.)</a> \n         <br> <b>1886:</b> Harper's Weekly featured a cartoon about the proposed annexation of Nova Scotia. \n         <a href="/onthisday/harp/0619.html">(See the cartoon.)</a></font> \n   </td>\n</tr>
" EditorType=boolean TrueFalse=-x| -Value=0 ValueDefault=0 [Turn off XML detection] @@ -142,7 +127,6 @@ Description="

HTB automatically detects XML compliant files and treats the unknown tags differently than HTML tags. XML tags are indented as whitespace permits and case changes & attribute sorting are not applied. To turn off this default behavior and apply case changes & sorting to all tags known and unknown, specify the -y option.

Example:

- Never break tags, make all tags lower case whether HTML or not, and do not change indenting for unknown tags...

htb -lny myfile.html

Before: 
<TR><TD WIDTH=182 ALIGN=left BGCOLOR="#ffffff">\n<NYT_HEADLINE>\n<A\n\nHREF="/onthisday/20020619.html"><FONT SIZE="3" FACE="times"><B>On June 19 ...<BR></B></FONT></A>\n</NYT_HEADLINE>\n<NYT_BYLINE>\n<FONT SIZE="-1"></FONT>\n</NYT_BYLINE>\n<NYT_SUMMARY>\n<FONT SIZE="-1">\n<B>1964:</B> The Civil Rights Act of 1964 was approved.   (<A \nHREF="/onthisday/big/0619.html">See this front page.</A>) <BR>\n<B>1903:</B> Lou Gehrig was born.  <A \nHREF="/onthisday/bday/0619.html">(Read about his life.)</A> <BR>\n<B>1886:</B> Harper's Weekly featured a cartoon about the proposed annexation of Nova Scotia. <A \nHREF="/onthisday/harp/0619.html">(See the cartoon.)</A></FONT>\n</TD></TR>
After:
<tr>\n   <td align="left" bgcolor="#ffffff" width="182"> \n      <nyt_headline> \n      <a href="/onthisday/20020619.html"><font face="times" size="3"><b>On June 19 ...<br></b></font></a> \n      </nyt_headline> \n      <nyt_byline> <font size="-1"></font> \n      </nyt_byline> \n      <nyt_summary> <font size="-1"> <b>1964:</b> The Civil Rights Act of 1964 was approved. (<a href="/onthisday/big/0619.html">See this front page.</a>) \n      <br> <b>1903:</b> Lou Gehrig was born. \n      <a href="/onthisday/bday/0619.html">(Read about his life.)</a> \n      <br> <b>1886:</b> Harper's Weekly featured a cartoon about the proposed annexation of Nova Scotia. \n      <a href="/onthisday/harp/0619.html">(See the cartoon.)</a></font> \n   </td>\n</tr>
" EditorType=boolean TrueFalse=-y| -Value=0 ValueDefault=0 [Remove Comments] @@ -150,7 +134,6 @@ Description="The -z command-line option removes all stand-alone comments from the input data. This does not include JavaScript comments or comment blocks within APPLET, OBJECT, SCRIPT, and STYLE tags used to hide text from browsers. The revised output should render and function as the original. The -z option is useful in reducing tagged file sizes when the comment blocks are no longer needed, or in removing dead, commented-out sections within documents which tend to collect over time. The stripped comments are not lost, however. These are sent to the 'standard error' stream and may be collected in another file for reference or for use in documentation by 'standard error' redirection ('2>' or '2>>'). If 'standard error' is not redirected, the stripped comments will be seen scrolling by on the screen. Use in combination with the -k option to strip comments without otherwise changing the document layout." EditorType=boolean TrueFalse=-z| -Value=0 ValueDefault=0 [Spaces for Indenting] @@ -161,5 +144,4 @@ Enabled=false MaxVal=9 MinVal=0 -Value=4 ValueDefault=3 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_perltidy.ini --- a/indenters/uigui_perltidy.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_perltidy.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description="

By default, perltidy will add line breaks when necessary to create continuations of long lines and to improve the script appearance. Use -nanl or --noadd-newlines to prevent any new line breaks.

This flag does not prevent perltidy from eliminating existing line breaks; see --freeze-newlines to completely prevent changes to line break points.

" EditorType=boolean TrueFalse=-anl|-nanl -Value=0 ValueDefault=0 [Add semicolons] @@ -29,7 +28,6 @@ Description="

Setting -asc allows perltidy to add any missing optional semicolon at the end of a line which is followed by a closing curly brace on the next line. This is the default, and may be deactivated with -nasc or --noadd-semicolons.

" EditorType=boolean TrueFalse=--add-semicolons| -Value=0 ValueDefault=0 [Add whitespace] @@ -37,7 +35,6 @@ Description="

Setting this option allows perltidy to add certain whitespace improve code readability. This is the default. If you do not want any whitespace added, but are willing to have some whitespace deleted, use -naws. (Use -fws to leave whitespace completely unchanged).

" EditorType=boolean TrueFalse=--add-whitespace| -Value=0 ValueDefault=0 [Block brace tightness] @@ -48,7 +45,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=1 ValueDefault=1 [Block brace vertical tightness] @@ -59,7 +55,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Brace left and indent] @@ -67,7 +62,6 @@ Description="

The flag -bli is the same as -bl but in addition it causes one unit of continuation indentation ( see -ci ) to be placed before an opening and closing block braces.

For example,

\n        if ( $input_file eq '-' )    # -bli\n          {\n            important_function();\n          }

By default, this extra indentation occurs for blocks of type:if, elsif, else, unless, for, foreach, sub, while, until, and also with a preceding label. The next item shows how to change this.

" EditorType=boolean TrueFalse=-bli| -Value=0 ValueDefault=0 [Brace left and indent list] @@ -76,7 +70,6 @@ Description="

Use this parameter to change the types of block braces for which the -bli flag applies; see Specifying Block Types. For example, -blil='if elsif else' would apply it to only if/elsif/else blocks.

" EditorType=string Enabled=false -Value= ValueDefault= [Brace tightness] @@ -87,7 +80,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=1 ValueDefault=1 [Brace vertical tightness] @@ -98,7 +90,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Brace vertical tightness closing] @@ -109,7 +100,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Break after all operators] @@ -117,7 +107,6 @@ Description="

The -baao sets the default to be to break after all of the following operators:

\n    % + - * / x != == >= <= =~ !~ < > | & \n    = **= += *= &= <<= &&= -= /= |= >>= ||= //= .= %= ^= x=\n    . : ? && || and or err xor

and the -bbao flag sets the default to break before all of these operators. These can be used to define an initial break preference which can be fine-tuned with the -wba and -wbb flags. For example, to break before all operators except an = one could use --bbao -wba='=' rather than listing every single perl operator except = on a -wbb flag.

" EditorType=boolean TrueFalse=-baao| -Value=0 ValueDefault=0 [Break before all operators] @@ -125,7 +114,6 @@ Description="

The -baao sets the default to be to break after all of the following operators:

\n    % + - * / x != == >= <= =~ !~ < > | & \n    = **= += *= &= <<= &&= -= /= |= >>= ||= //= .= %= ^= x=\n    . : ? && || and or err xor

and the -bbao flag sets the default to break before all of these operators. These can be used to define an initial break preference which can be fine-tuned with the -wba and -wbb flags. For example, to break before all operators except an = one could use --bbao -wba='=' rather than listing every single perl operator except = on a -wbb flag.

" EditorType=boolean TrueFalse=-bbao| -Value=0 ValueDefault=0 [Check syntax] @@ -134,7 +122,6 @@ EditorType=boolean Enabled=false TrueFalse=--check-syntax| -Value=0 ValueDefault=0 [Closing Side Comment Else Flag] @@ -145,7 +132,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=0 ValueDefault=0 [Closing Side Comment Interval] @@ -156,7 +142,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=6 ValueDefault=6 [Closing Side Comment List] @@ -165,7 +150,6 @@ Description="

where string is a list of block types to be tagged with closing side comments. By default, all code block types preceded by a keyword or label (such as if, sub, and so on) will be tagged. The -cscl command changes the default list to be any selected block types; see Specifying Block Types. For example, the following command requests that only sub's, labels, BEGIN, and END blocks be affected by any -csc or -dcsc operation:

\n   -cscl="sub : BEGIN END"
" EditorType=string Enabled=false -Value= ValueDefault= [Closing Side Comment Maximum Text] @@ -176,7 +160,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=20 ValueDefault=20 [Closing Side Comment Prefix] @@ -185,7 +168,6 @@ Description="

where string is the prefix used before the name of the block type. The default prefix, shown above, is ## end. This string will be added to closing side comments, and it will also be used to recognize them in order to update, delete, and format them. Any comment identified as a closing side comment will be placed just a single space to the right of its closing brace.

" EditorType=string Enabled=false -Value=## end ValueDefault=## end [Closing Side Comment Warnings] @@ -193,7 +175,6 @@ Description="

This parameter is intended to help make the initial transition to the use of closing side comments. It causes two things to happen if a closing side comment replaces an existing, different closing side comment: first, an error message will be issued, and second, the original side comment will be placed alone on a new specially marked comment line for later attention.

The intent is to avoid clobbering existing hand-written side comments which happen to match the pattern of closing side comments. This flag should only be needed on the first run with -csc.

" EditorType=boolean TrueFalse=--closing-side-comment-warnings| -Value=0 ValueDefault=0 [Closing Side Comments] @@ -203,7 +184,6 @@ Description="

A closing side comment is a special comment which perltidy can automatically create and place after the closing brace of a code block. They can be useful for code maintenance and debugging. The command -csc (or --closing-side-comments) adds or updates closing side comments. For example, here is a small code snippet

\n        sub message {\n            if ( !defined( $_[0] ) ) {\n                print("Hello, World\n");\n            }\n            else {\n                print( $_[0], "\n" );\n            }\n        }

And here is the result of processing with perltidy -csc:

\n        sub message {\n            if ( !defined( $_[0] ) ) {\n                print("Hello, World\n");\n            }\n            else {\n                print( $_[0], "\n" );\n            }\n        } ## end sub message

A closing side comment was added for sub message in this case, but not for the if and else blocks, because they were below the 6 line cutoff limit for adding closing side comments. This limit may be changed with the -csci command, described below.

The command -dcsc (or --delete-closing-side-comments) reverses this process and removes these comments.

Several commands are available to modify the behavior of these two basic commands, -csc and -dcsc:

" EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [Closing token indentation] @@ -214,7 +194,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=0 ValueDefault=0 [Continuation indentation] @@ -225,7 +204,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=2 ValueDefault=2 [Cuddled else] @@ -233,7 +211,6 @@ Description="

Enable the ``cuddled else'' style, in which else and elsif are follow immediately after the curly brace closing the previous block. The default is not to use cuddled elses, and is indicated with the flag -nce or --nocuddled-else. Here is a comparison of the alternatives:

\n  if ($task) {\n      yyy();\n  } else {    # -ce\n      zzz();\n  }
\n  if ($task) {\n        yyy();\n  }\n  else {    # -nce  (default)\n        zzz();\n  }
" EditorType=boolean TrueFalse=-ce|-nce -Value=0 ValueDefault=0 [Delete old newlines] @@ -241,7 +218,6 @@ Description="

By default, perltidy first deletes all old line break locations, and then it looks for good break points to match the desired line length. Use -ndnl or --nodelete-old-newlines to force perltidy to retain all old line break points.

" EditorType=boolean TrueFalse=-dnl|-ndnl -Value=0 ValueDefault=0 [Delete old whitespace] @@ -249,7 +225,6 @@ Description="

Setting this option allows perltidy to remove some old whitespace between characters, if necessary. This is the default. If you do not want any old whitespace removed, use -ndws or --nodelete-old-whitespace.

" EditorType=boolean TrueFalse=--delete-old-whitespace| -Value=0 ValueDefault=0 [Delete semicolons] @@ -257,7 +232,6 @@ Description="

Setting -dsm allows perltidy to delete extra semicolons which are simply empty statements. This is the default, and may be deactivated with -ndsm or --nodelete-semicolons. (Such semicolons are not deleted, however, if they would promote a side comment to a block comment).

" EditorType=boolean TrueFalse=--delete-semicolons| -Value=0 ValueDefault=0 [Entab leading whitespace] @@ -268,7 +242,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=4 ValueDefault=4 [Feeze newlines] @@ -276,7 +249,6 @@ Description="

If you do not want any changes to the line breaks in your script, set -fnl, and they will remain fixed, and the rest of the commands in this section and sections Controlling List Formatting, Retaining or Ignoring Existing Line Breaks, and Blank Line Control will be ignored. You may want to use -noll with this.

" EditorType=boolean TrueFalse=-fnl| -Value=0 ValueDefault=0 [Fixed position side comment] @@ -287,7 +259,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=0 ValueDefault=0 [Format skipping] @@ -295,7 +266,6 @@ Description="

Selected lines of code may be passed verbatim to the output without any formatting. This feature is enabled by default but can be disabled with the --noformat-skipping or -nfs flag. It should be used sparingly to avoid littering code with markers, but it might be helpful for working around occasional problems. For example it might be useful for keeping the indentation of old commented code unchanged, keeping indentation of long blocks of aligned comments unchanged, keeping certain list formatting unchanged, or working around a glitch in perltidy.

-fs, --format-skipping

This flag, which is enabled by default, causes any code between special beginning and ending comment markers to be passed to the output without formatting. The default beginning marker is #<<< and the default ending marker is #>>> but they may be changed (see next items below). Additional text may appear on these special comment lines provided that it is separated from the marker by at least one space. For example

\n #<<<  do not let perltidy touch this\n    my @list = (1,\n                1, 1,\n                1, 2, 1,\n                1, 3, 3, 1,\n                1, 4, 6, 4, 1,);\n #>>>

The comment markers may be placed at any location that a block comment may appear. If they do not appear to be working, use the -log flag and examine the .LOG file. Use -nfs to disable this feature.

" EditorType=boolean TrueFalse=-fs|-nfs -Value=1 ValueDefault=1 [Format skipping begin] @@ -304,7 +274,6 @@ Description="

The -fsb=string parameter may be used to change the beginning marker for format skipping. The default is equivalent to -fsb='#<<<'. The string that you enter must begin with a # and should be in quotes as necessary to get past the command shell of your system. It is actually the leading text of a pattern that is constructed by appending a '', so you must also include backslashes for characters to be taken literally rather than as patterns.

Some examples show how example strings become patterns:

\n -fsb='#' becomes /^#/  which matches  #{{{ but not #{{{{\n -fsb='#'   becomes /^#/    which matches  #** but not #***\n -fsb='#{2,}' becomes /^#{2,}/  which matches  #** and #*****
" EditorType=string Enabled=false -Value=#<<< ValueDefault=#<<< [Format skipping end] @@ -313,7 +282,6 @@ Description="

The -fsb=string is the corresponding parameter used to change the ending marker for format skipping. The default is equivalent to -fse='#<<<'.

" EditorType=string Enabled=false -Value=#<<< ValueDefault=#<<< [Freeze whitespace] @@ -321,7 +289,6 @@ Description="This flag causes your original whitespace to remain unchanged, and causes the rest of the whitespace commands in this section, the Code Indentation section, and the Comment Control section to be ignored." EditorType=boolean TrueFalse=--freeze-whitespace| -Value=0 ValueDefault=0 [Gnu style] @@ -330,7 +297,6 @@ EditorType=boolean Enabled=false TrueFalse=--gnu-style| -Value=0 ValueDefault=0 [Hanging side comments] @@ -338,7 +304,6 @@ Description="

By default, perltidy tries to identify and align ``hanging side comments'', which are something like this:

\n        my $IGNORE = 0;    # This is a side comment\n                           # This is a hanging side comment\n                           # And so is this

A comment is considered to be a hanging side comment if (1) it immediately follows a line with a side comment, or another hanging side comment, and (2) there is some leading whitespace on the line. To deactivate this feature, use -nhsc or --nohanging-side-comments. If block comments are preceded by a blank line, or have no leading whitespace, they will not be mistaken as hanging side comments.

" EditorType=boolean TrueFalse=-hsc|-nhsc -Value=0 ValueDefault=0 [Indent block comments] @@ -346,7 +311,6 @@ Description="

Block comments normally look best when they are indented to the same level as the code which follows them. This is the default behavior, but you may use -nibc to keep block comments left-justified. Here is an example:

\n             # this comment is indented      (-ibc, default)\n             if ($task) { yyy(); }

The alternative is -nibc:

\n # this comment is not indented              (-nibc)\n             if ($task) { yyy(); }

See also the next item, -isbc, as well as -sbc, for other ways to have some indented and some outdented block comments.

" EditorType=boolean TrueFalse=-ibc|-nibc -Value=1 ValueDefault=1 [Indent closing brace] @@ -354,7 +318,6 @@ Description="The -icb option gives one extra level of indentation to a brace which terminates a code block . For example,

\n        if ($task) {\n            yyy();\n            }    # -icb\n        else {\n            zzz();\n            }

The default is not to do this, indicated by -nicb." EditorType=boolean TrueFalse=--indent-closing-brace| -Value=0 ValueDefault=0 [Indent closing paren] @@ -362,7 +325,6 @@ Description="The -icp flag is equivalent to-cti=2, described in the previous section. The -nicp flag is equivalent -cti=0. They are included for backwards compatability." EditorType=boolean TrueFalse=--indent-closing-paren| -Value=0 ValueDefault=0 [Indent columns] @@ -373,7 +335,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=4 ValueDefault=4 [Indent only] @@ -382,7 +343,6 @@ EditorType=boolean Enabled=false TrueFalse=--indent-only| -Value=0 ValueDefault=0 [Indent spaced block comments] @@ -390,7 +350,6 @@ Description="

If there is no leading space on the line, then the comment will not be indented, and otherwise it may be.

If both -ibc and -isbc are set, then -isbc takes priority.

" EditorType=boolean TrueFalse=-isbc| -Value=0 ValueDefault=0 [List indentation] @@ -398,7 +357,6 @@ Description="By default, perltidy indents lists with 4 spaces, or whatever value is specified with -i=n. Here is a small list formatted in this way:

\n    # perltidy (default)\n    @month_of_year = (\n        'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun',\n        'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'\n    );

Use the -lp flag to add extra indentation to cause the data to begin past the opening parentheses of a sub call or list, or opening square bracket of an anonymous array, or opening curly brace of an anonymous hash. With this option, the above list would become:

\n    # perltidy -lp\n    @month_of_year = (\n                       'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun',\n                       'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'\n    );

If the available line length (see -l=n ) does not permit this much space, perltidy will use less. For alternate placement of the closing paren, see the next section.

This option has no effect on code BLOCKS, such as if/then/else blocks, which always use whatever is specified with -i=n. Also, the existence of line breaks and/or block comments between the opening and closing parens may cause perltidy to temporarily revert to its default method.

Note: The -lp option may not be used together with the -t tabs option. It may, however, be used with the -et=n tab method.

In addition, any parameter which significantly restricts the ability of perltidy to choose newlines will conflict with -lp and will cause -lp to be deactivated. These include -io, -fnl, -nanl, and -ndnl. The reason is that the -lp indentation style can require the careful coordination of an arbitrary number of break points in hierarchical lists, and these flags may prevent that." EditorType=boolean TrueFalse=--line-up-parentheses| -Value=0 ValueDefault=0 [Maximum line length] @@ -409,7 +367,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=80 ValueDefault=80 [Minimum space to comment] @@ -420,7 +377,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=4 ValueDefault=4 [Nospace after keyword] @@ -429,7 +385,6 @@ Description="

When an opening paren follows a Perl keyword, no space is introduced after the keyword, unless it is (by default) one of these:

\n   my local our and or eq ne if else elsif until unless \n   while for foreach return switch case given when

These defaults can be modified with two commands:

-sak=s or --space-after-keyword=s adds keywords.

-nsak=s or --nospace-after-keyword=s removes keywords.

where s is a list of keywords (in quotes if necessary). For example,

\n  my ( $a, $b, $c ) = @_;    # default\n  my( $a, $b, $c ) = @_;     # -nsak="my local our"
" EditorType=string Enabled=false -Value= ValueDefault= [Nowant left space] @@ -438,7 +393,6 @@ Description="

For those who want more detailed control over the whitespace around tokens, there are four parameters which can directly modify the default whitespace rules built into perltidy for any token. They are:

-wls=s or --want-left-space=s,

-nwls=s or --nowant-left-space=s,

-wrs=s or --want-right-space=s,

-nwrs=s or --nowant-right-space=s.

These parameters are each followed by a quoted string, s, containing a list of token types. No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

To illustrate how these are used, suppose it is desired that there be no space on either side of the token types = + - / *. The following two parameters would specify this desire:

\n  -nwls="= + - / *"    -nwrs="= + - / *"

(Note that the token types are in quotes, and that they are separated by spaces). With these modified whitespace rules, the following line of math:

\n  $root = -$b + sqrt( $b * $b - 4. * $a * $c ) / ( 2. * $a );

becomes this:

\n  $root=-$b+sqrt( $b*$b-4.*$a*$c )/( 2.*$a );

These parameters should be considered to be hints to perltidy rather than fixed rules, because perltidy must try to resolve conflicts that arise between them and all of the other rules that it uses. One conflict that can arise is if, between two tokens, the left token wants a space and the right one doesn't. In this case, the token not wanting a space takes priority.

It is necessary to have a list of all token types in order to create this type of input. Such a list can be obtained by the command --dump-token-types. Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

" EditorType=string Enabled=false -Value= ValueDefault= [Nowant right space] @@ -447,7 +401,6 @@ Description="

For those who want more detailed control over the whitespace around tokens, there are four parameters which can directly modify the default whitespace rules built into perltidy for any token. They are:

-wls=s or --want-left-space=s,

-nwls=s or --nowant-left-space=s,

-wrs=s or --want-right-space=s,

-nwrs=s or --nowant-right-space=s.

These parameters are each followed by a quoted string, s, containing a list of token types. No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

To illustrate how these are used, suppose it is desired that there be no space on either side of the token types = + - / *. The following two parameters would specify this desire:

\n  -nwls="= + - / *"    -nwrs="= + - / *"

(Note that the token types are in quotes, and that they are separated by spaces). With these modified whitespace rules, the following line of math:

\n  $root = -$b + sqrt( $b * $b - 4. * $a * $c ) / ( 2. * $a );

becomes this:

\n  $root=-$b+sqrt( $b*$b-4.*$a*$c )/( 2.*$a );

These parameters should be considered to be hints to perltidy rather than fixed rules, because perltidy must try to resolve conflicts that arise between them and all of the other rules that it uses. One conflict that can arise is if, between two tokens, the left token wants a space and the right one doesn't. In this case, the token not wanting a space takes priority.

It is necessary to have a list of all token types in order to create this type of input. Such a list can be obtained by the command --dump-token-types. Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

" EditorType=string Enabled=false -Value= ValueDefault= [Opening brace always on right] @@ -455,7 +408,6 @@ Description="

The default style, -nbl places the opening code block brace on a new line if it does not fit on the same line as the opening keyword, like this:

\n        if ( $bigwasteofspace1 && $bigwasteofspace2\n          || $bigwasteofspace3 && $bigwasteofspace4 )\n        {\n            big_waste_of_time();\n        }

To force the opening brace to always be on the right, use the -bar flag. In this case, the above example becomes

\n        if ( $bigwasteofspace1 && $bigwasteofspace2\n          || $bigwasteofspace3 && $bigwasteofspace4 ) {\n            big_waste_of_time();\n        }

A conflict occurs if both -bl and -bar are specified.

" EditorType=boolean TrueFalse=-bar| -Value=0 ValueDefault=0 [Opening brace on new line] @@ -463,7 +415,6 @@ Description="

Use the flag -bl to place the opening brace on a new line:

\n  if ( $input_file eq '-' )    # -bl \n  {                          \n      important_function();\n  }

This flag applies to all structural blocks, including sub's (unless the -sbl flag is set -- see next item).

The default style, -nbl, places an opening brace on the same line as the keyword introducing it. For example,

\n  if ( $input_file eq '-' ) {   # -nbl (default)
" EditorType=boolean TrueFalse=-bl|-nbl -Value=0 ValueDefault=0 [Opening hash brace right] @@ -471,7 +422,6 @@ Description="

The -otr flag is a hint that perltidy should not place a break between a comma and an opening token. For example:

\n    # default formatting\n    push @{ $self->{$module}{$key} },\n      {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };
\n    # perltidy -otr\n    push @{ $self->{$module}{$key} }, {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };

The flag -otr is actually a synonym for three other flags which can be used to control parens, hash braces, and square brackets separately if desired:

\n  -opr  or --opening-paren-right\n  -ohbr or --opening-hash-brace-right\n  -osbr or --opening-square-bracket-right
" EditorType=boolean TrueFalse=-ohbr| -Value=0 ValueDefault=0 [Opening paren right] @@ -479,7 +429,6 @@ Description="

The -otr flag is a hint that perltidy should not place a break between a comma and an opening token. For example:

\n    # default formatting\n    push @{ $self->{$module}{$key} },\n      {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };
\n    # perltidy -otr\n    push @{ $self->{$module}{$key} }, {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };

The flag -otr is actually a synonym for three other flags which can be used to control parens, hash braces, and square brackets separately if desired:

\n  -opr  or --opening-paren-right\n  -ohbr or --opening-hash-brace-right\n  -osbr or --opening-square-bracket-right
" EditorType=boolean TrueFalse=-opr| -Value=0 ValueDefault=0 [Opening square bracket right] @@ -487,7 +436,6 @@ Description="

The -otr flag is a hint that perltidy should not place a break between a comma and an opening token. For example:

\n    # default formatting\n    push @{ $self->{$module}{$key} },\n      {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };
\n    # perltidy -otr\n    push @{ $self->{$module}{$key} }, {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };

The flag -otr is actually a synonym for three other flags which can be used to control parens, hash braces, and square brackets separately if desired:

\n  -opr  or --opening-paren-right\n  -ohbr or --opening-hash-brace-right\n  -osbr or --opening-square-bracket-right
" EditorType=boolean TrueFalse=-osbr| -Value=0 ValueDefault=0 [Opening sub brace on new line] @@ -495,7 +443,6 @@ Description="

The flag -sbl can be used to override the value of -bl for opening sub braces. For example,

\n perltidy -sbl

produces this result:

\n sub message\n {\n    if (!defined($_[0])) {\n        print("Hello, World\n");\n    }\n    else {\n        print($_[0], "\n");\n    }\n }

This flag is negated with -nsbl. If -sbl is not specified, the value of -bl is used.

" EditorType=boolean TrueFalse=-sbl|-nsbl -Value=0 ValueDefault=0 [Opening token right] @@ -503,7 +450,6 @@ Description="

The -otr flag is a hint that perltidy should not place a break between a comma and an opening token. For example:

\n    # default formatting\n    push @{ $self->{$module}{$key} },\n      {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };
\n    # perltidy -otr\n    push @{ $self->{$module}{$key} }, {\n        accno       => $ref->{accno},\n        description => $ref->{description}\n      };

The flag -otr is actually a synonym for three other flags which can be used to control parens, hash braces, and square brackets separately if desired:

\n  -opr  or --opening-paren-right\n  -ohbr or --opening-hash-brace-right\n  -osbr or --opening-square-bracket-right
" EditorType=boolean TrueFalse=-otr| -Value=0 ValueDefault=0 [Outdent keyword list] @@ -512,7 +458,6 @@ Description="This command can be used to change the keywords which are outdented with the -okw command. The parameter string is a required list of perl keywords, which should be placed in quotes if there are more than one. By itself, it does not cause any outdenting to occur, so the -okw command is still required.

For example, the commands -okwl="next last redo goto" -okw will cause those four keywords to be outdented. It is probably simplest to place any -okwl command in a .perltidyrc file." EditorType=string Enabled=false -Value= ValueDefault= [Outdent long comments] @@ -520,7 +465,6 @@ Description="

When -olc is set, lines which are full-line (block) comments longer than the value maximum-line-length will have their indentation removed. This is the default; use -nolc to prevent outdenting.

" EditorType=boolean TrueFalse=-olc|-nolc -Value=1 ValueDefault=1 [Outdent long lines] @@ -528,7 +472,6 @@ Description="This command is equivalent to --outdent-long-quotes and --outdent-long-comments, and it is included for compatibility with previous versions of perltidy. The negation of this also works, -noll or --nooutdent-long-lines, and is equivalent to setting -nolq and -nolc." EditorType=boolean TrueFalse=--outdent-long-lines| -Value=0 ValueDefault=0 [Outdent long quotes] @@ -536,7 +479,6 @@ Description="When -olq is set, lines which is a quoted string longer than the value maximum-line-length will have their indentation removed to make them more readable. This is the default. To prevent such out-denting, use -nolq or --nooutdent-long-lines." EditorType=boolean TrueFalse=--outdent-long-quotes| -Value=0 ValueDefault=0 [Outdenting Keywords] @@ -544,7 +486,6 @@ Description="The command -okw will will cause certain leading control keywords to be outdented by 2 spaces (or whatever -ci has been set to), if possible. By default, these keywords are redo, next, last, goto, and return. The intention is to make these control keywords easier to see. To change this list of keywords being outdented, see the next section.

For example, using perltidy -okw on the previous example gives:

\n        my $i;\n      LOOP: while ( $i = <FOTOS> ) {\n            chomp($i);\n          next unless $i;\n            fixit($i);\n        }

The default is not to do this." EditorType=boolean TrueFalse=--outdent-keywords| -Value=0 ValueDefault=0 [Outdenting Labels] @@ -552,7 +493,6 @@ Description="This command will cause labels to be outdented by 2 spaces (or whatever -ci has been set to), if possible. This is the default. For example:

\n        my $i;\n      LOOP: while ( $i = <FOTOS> ) {\n            chomp($i);\n            next unless $i;\n            fixit($i);\n        }

Use -nola to not outdent labels." EditorType=boolean TrueFalse=--outdent-labels| -Value=0 ValueDefault=0 [Output line ending] @@ -562,7 +502,6 @@ Description="where s=win, dos, unix, or mac. This flag tells perltidy to output line endings for a specific system. Normally, perltidy writes files with the line separator character of the host system. The win and dos flags have an identical result." EditorType=multiple Enabled=false -Value=1 ValueDefault=1 [Paren tightness] @@ -573,7 +512,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=1 ValueDefault=1 [Paren vertical tightness] @@ -584,7 +522,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Paren vertical tightness closing] @@ -595,7 +532,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Perl best practices] @@ -604,7 +540,6 @@ EditorType=boolean Enabled=false TrueFalse=--perl-best-practices --nostandard-output| -Value=0 ValueDefault=0 [Perl syntax check flags] @@ -613,7 +548,6 @@ Description="When perl is invoked to check syntax, the normal flags are -c -T. In addition, if the -x flag is given to perltidy, then perl will also be passed a -x flag. It should not normally be necessary to change these flags, but it can be done with the -pscf=s flag. For example, if the taint flag, -T, is not wanted, the flag could be set to be just -pscf=-c.

Perltidy will pass your string to perl with the exception that it willadd a -c and -x if appropriate. The .LOG file will show exactly what flags were passed to perl." EditorType=string Enabled=false -Value= ValueDefault= [Preserve line endings] @@ -622,7 +556,6 @@ EditorType=boolean Enabled=false TrueFalse=--preserve-line-endings| -Value=0 ValueDefault=0 [Space after keyword] @@ -631,7 +564,6 @@ Description="

When an opening paren follows a Perl keyword, no space is introduced after the keyword, unless it is (by default) one of these:

\n   my local our and or eq ne if else elsif until unless \n   while for foreach return switch case given when

These defaults can be modified with two commands:

-sak=s or --space-after-keyword=s adds keywords.

-nsak=s or --nospace-after-keyword=s removes keywords.

where s is a list of keywords (in quotes if necessary). For example,

\n  my ( $a, $b, $c ) = @_;    # default\n  my( $a, $b, $c ) = @_;     # -nsak="my local our"
" EditorType=string Enabled=false -Value= ValueDefault= [Space for semicolon] @@ -639,7 +571,6 @@ Description="

Semicolons within for loops may sometimes be hard to see, particularly when commas are also present. This option places spaces on both sides of these special semicolons, and is the default. Use -nsfs or --nospace-for-semicolon to deactivate it.

\n for ( @a = @$ap, $u = shift @a ; @a ; $u = $v ) {  # -sfs (default)\n for ( @a = @$ap, $u = shift @a; @a; $u = $v ) {    # -nsfs
" EditorType=boolean TrueFalse=--space-for-semicolon| -Value=0 ValueDefault=0 [Space function paren] @@ -647,7 +578,6 @@ Description="

When an opening paren follows a function the default is not to introduce a space. To cause a space to be introduced use:

-sfp or --space-function-paren

\n  myfunc( $a, $b, $c );    # default \n  myfunc ( $a, $b, $c );   # -sfp

You will probably also want to use the flag -skp (previous item) too.

" EditorType=boolean TrueFalse=--space-function-paren| -Value=0 ValueDefault=0 [Space keyword paren] @@ -655,7 +585,6 @@ Description="

When an opening paren follows a function or keyword, no space is introduced after the keyword except for the keywords noted in the previous item. To always put a space between a function or keyword and its opening paren, use the command:

-skp or --space-keyword-paren

You will probably also want to use the flag -sfp (next item) too.

" EditorType=boolean TrueFalse=--space-keyword-paren| -Value=0 ValueDefault=0 [Space terminal semicolon] @@ -663,7 +592,6 @@ Description="

Some programmers prefer a space before all terminal semicolons. The default is for no such space, and is indicated with -nsts or --nospace-terminal-semicolon.

\n        $i = 1 ;     #  -sts\n        $i = 1;      #  -nsts   (default)
" EditorType=boolean TrueFalse=--space-terminal-semicolon| -Value=0 ValueDefault=0 [Square bracket tightness] @@ -674,7 +602,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=1 ValueDefault=1 [Square bracket vertical tightness] @@ -685,7 +612,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Square bracket vertical tightness closing] @@ -696,7 +622,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Stack closing hash brace] @@ -704,7 +629,6 @@ Description="

The -sct flag tells perltidy to ``stack'' closing tokens when possible to avoid lines with isolated closing tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sct\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        } );

The -sct flag is somewhat similar to the -vtc flags, and in some cases it can give a similar result. The difference is that the -vtc flags try to avoid lines with leading opening tokens by ``hiding'' them at the end of a previous line, whereas the -sct flag merely tries to reduce the number of lines with isolated closing tokens by stacking them but does not try to hide them. For example:

\n    # -vtc=2\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1, } );

The flag -sct is a synonym for -scp -schb -scsb.

" EditorType=boolean TrueFalse=-schb| -Value=0 ValueDefault=0 [Stack closing paren] @@ -712,7 +636,6 @@ Description="

The -sct flag tells perltidy to ``stack'' closing tokens when possible to avoid lines with isolated closing tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sct\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        } );

The -sct flag is somewhat similar to the -vtc flags, and in some cases it can give a similar result. The difference is that the -vtc flags try to avoid lines with leading opening tokens by ``hiding'' them at the end of a previous line, whereas the -sct flag merely tries to reduce the number of lines with isolated closing tokens by stacking them but does not try to hide them. For example:

\n    # -vtc=2\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1, } );

The flag -sct is a synonym for -scp -schb -scsb.

" EditorType=boolean TrueFalse=-scp| -Value=0 ValueDefault=0 [Stack closing square bracket] @@ -720,7 +643,6 @@ Description="

The -sct flag tells perltidy to ``stack'' closing tokens when possible to avoid lines with isolated closing tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sct\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        } );

The -sct flag is somewhat similar to the -vtc flags, and in some cases it can give a similar result. The difference is that the -vtc flags try to avoid lines with leading opening tokens by ``hiding'' them at the end of a previous line, whereas the -sct flag merely tries to reduce the number of lines with isolated closing tokens by stacking them but does not try to hide them. For example:

\n    # -vtc=2\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1, } );

The flag -sct is a synonym for -scp -schb -scsb.

" EditorType=boolean TrueFalse=-scsb| -Value=0 ValueDefault=0 [Stack closing tokens] @@ -728,7 +650,6 @@ Description="

The -sct flag tells perltidy to ``stack'' closing tokens when possible to avoid lines with isolated closing tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sct\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        } );

The -sct flag is somewhat similar to the -vtc flags, and in some cases it can give a similar result. The difference is that the -vtc flags try to avoid lines with leading opening tokens by ``hiding'' them at the end of a previous line, whereas the -sct flag merely tries to reduce the number of lines with isolated closing tokens by stacking them but does not try to hide them. For example:

\n    # -vtc=2\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1, } );

For detailed control of the stacking of individual closing tokens the following controls can be used:

\n  -scp  or --stack-closing-paren\n  -schb or --stack-closing-hash-brace\n  -scsb or --stack-closing-square-bracket

The flag -sct is a synonym for -scp -schb -scsb.

" EditorType=boolean TrueFalse=-sct| -Value=0 ValueDefault=0 [Stack opening hash brace] @@ -736,7 +657,6 @@ Description="

The -sot flag tells perltidy to ``stack'' opening tokens when possible to avoid lines with isolated opening tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sot\n    $opt_c = Text::CSV_XS->new( {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );

For detailed control of individual closing tokens the following controls can be used:

\n  -sop  or --stack-opening-paren\n  -sohb or --stack-opening-hash-brace\n  -sosb or --stack-opening-square-bracket

The flag -sot is a synonym for -sop -sohb -sosb.

" EditorType=boolean TrueFalse=-sohb| -Value=0 ValueDefault=0 [Stack opening paren] @@ -744,7 +664,6 @@ Description="

The -sot flag tells perltidy to ``stack'' opening tokens when possible to avoid lines with isolated opening tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sot\n    $opt_c = Text::CSV_XS->new( {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );

The flag -sot is a synonym for -sop -sohb -sosb.

" EditorType=boolean TrueFalse=-sop| -Value=0 ValueDefault=0 [Stack opening square bracket] @@ -752,7 +671,6 @@ Description="

The -sot flag tells perltidy to ``stack'' opening tokens when possible to avoid lines with isolated opening tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sot\n    $opt_c = Text::CSV_XS->new( {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );

For detailed control of individual closing tokens the following controls can be used:

\n  -sop  or --stack-opening-paren\n  -sohb or --stack-opening-hash-brace\n  -sosb or --stack-opening-square-bracket

The flag -sot is a synonym for -sop -sohb -sosb.

" EditorType=boolean TrueFalse=-sosb| -Value=0 ValueDefault=0 [Stack opening tokens] @@ -760,7 +678,6 @@ Description="

The -sot flag tells perltidy to ``stack'' opening tokens when possible to avoid lines with isolated opening tokens.

For example:

\n    # default\n    $opt_c = Text::CSV_XS->new(\n        {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );
\n    # -sot\n    $opt_c = Text::CSV_XS->new( {\n            binary       => 1,\n            sep_char     => $opt_c,\n            always_quote => 1,\n        }\n    );

For detailed control of individual closing tokens the following controls can be used:

\n  -sop  or --stack-opening-paren\n  -sohb or --stack-opening-hash-brace\n  -sosb or --stack-opening-square-bracket

The flag -sot is a synonym for -sop -sohb -sosb.

" EditorType=boolean TrueFalse=-sot| -Value=0 ValueDefault=0 [Starting indentation level] @@ -771,7 +688,6 @@ Enabled=false MaxVal=1000 MinVal=0 -Value=0 ValueDefault=0 [Static Block Comment Outdent] @@ -779,7 +695,6 @@ Description="

The command -osbc will will cause static block comments to be outdented by 2 spaces (or whatever -ci=n has been set to), if possible.

" EditorType=boolean TrueFalse=-osbc| -Value=0 ValueDefault=0 [Static Block Comment Prefix] @@ -788,7 +703,6 @@ Description="

This parameter defines the prefix used to identify static block comments when the -sbc parameter is set. The default prefix is ##, corresponding to -sbcp=##. The prefix is actually part of a perl pattern used to match lines and it must either begin with # or ^#. In the first case a prefix ^* will be added to match any leading whitespace, while in the second case the pattern will match only comments with no leading whitespace. For example, to identify all comments as static block comments, one would use -sbcp=#. To identify all left-adjusted comments as static block comments, use -sbcp='^#'.

Please note that -sbcp merely defines the pattern used to identify static block comments; it will not be used unless the switch -sbc is set. Also, please be aware that since this string is used in a perl regular expression which identifies these comments, it must enable a valid regular expression to be formed.

A pattern which can be useful is:

\n    -sbcp=^#{2,}[^#]

This pattern requires a static block comment to have at least one character which is neither a # nor a space. It allows a line containing only '#' characters to be rejected as a static block comment. Such lines are often used at the start and end of header information in subroutines and should not be separated from the intervening comments, which typically begin with just a single '#'.

" EditorType=string Enabled=false -Value=## ValueDefault=## [Static Block Comments] @@ -796,7 +710,6 @@ Description="

Static block comments are block comments with a special leading pattern, ## by default, which will be treated slightly differently from other block comments. They effectively behave as if they had glue along their left and top edges, because they stick to the left edge and previous line when there is no blank spaces in those places. This option is particularly useful for controlling how commented code is displayed.

-sbc, --static-block-comments

When -sbc is used, a block comment with a special leading pattern, ## by default, will be treated specially.

Comments so identified are treated as follows:

  • If there is no leading space on the line, then the comment will not be indented, and otherwise it may be,

  • no new blank line will be inserted before such a comment, and

  • such a comment will never become a hanging side comment.

For example, assuming @month_of_year is left-adjusted:

\n    @month_of_year = (    # -sbc (default)\n        'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct',\n    ##  'Dec', 'Nov'\n        'Nov', 'Dec');

Without this convention, the above code would become

\n    @month_of_year = (   # -nsbc\n        'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct',\n  \n        ##  'Dec', 'Nov'\n        'Nov', 'Dec'\n    );

which is not as clear. The default is to use -sbc. This may be deactivated with -nsbc.

" EditorType=boolean TrueFalse=-sbc|-nsbc -Value=1 ValueDefault=1 [Static Side Comment Prefix] @@ -805,7 +718,6 @@ Description="

This parameter defines the prefix used to identify static side comments when the -ssc parameter is set. The default prefix is ##, corresponding to -sscp=##.

Please note that -sscp merely defines the pattern used to identify static side comments; it will not be used unless the switch -ssc is set. Also, note that this string is used in a perl regular expression which identifies these comments, so it must enable a valid regular expression to be formed.

" EditorType=string Enabled=false -Value=## ValueDefault=## [Static Side Comments] @@ -813,7 +725,6 @@ Description="

Static side comments are side comments with a special leading pattern. This option can be useful for controlling how commented code is displayed when it is a side comment.

-ssc, --static-side-comments

When -ssc is used, a side comment with a static leading pattern, which is ## by default, will be be spaced only a single space from previous character, and it will not be vertically aligned with other side comments.

The default is -nssc.

" EditorType=boolean TrueFalse=-ssc|-nssc -Value=0 ValueDefault=0 [Tabs] @@ -821,7 +732,6 @@ Description="This flag causes one leading tab character to be inserted for each level of indentation. Certain other features are incompatible with this option, and if these options are also given, then a warning message will be issued and this flag will be unset. One example is the -lp option." EditorType=boolean TrueFalse=--tabs| -Value=0 ValueDefault=0 [Trimming whitespace around qw quotes] @@ -831,7 +741,6 @@ Description="

-tqw or --trim-qw provide the default behavior of trimming spaces around multi-line qw quotes and indenting them appropriately.

-ntqw or --notrim-qw cause leading and trailing whitespace around multi-line qw quotes to be left unchanged. This option will not normally be necessary, but was added for testing purposes, because in some versions of perl, trimming qw quotes changes the syntax tree.

" EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [Vertical tightness] @@ -842,7 +751,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Vertical tightness closing] @@ -853,7 +761,6 @@ Enabled=false MaxVal=2 MinVal=0 -Value=0 ValueDefault=0 [Want break after] @@ -862,7 +769,6 @@ Description="

These parameters are each followed by a quoted string, s, containing a list of token types (separated only by spaces). No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

By default, perltidy breaks after these token types: % + - * / x != == >= <= =~ !~ < > | & = **= += *= &= <<= &&= -= /= |= >>= ||= //= .= %= ^= x=

And perltidy breaks before these token types by default: . << >> -> && || //

To illustrate, to cause a break after a concatenation operator, '.', rather than before it, the command line would be

\n  -wba="."

As another example, the following command would cause a break before math operators '+', '-', '/', and '*':

\n  -wbb="+ - / *"

These commands should work well for most of the token types that perltidy uses (use --dump-token-types for a list). Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization. However, for a few token types there may be conflicts with hardwired logic which cause unexpected results. One example is curly braces, which should be controlled with the parameter bl provided for that purpose.

" EditorType=string Enabled=false -Value= ValueDefault= [Want break before] @@ -871,7 +777,6 @@ Description="

These parameters are each followed by a quoted string, s, containing a list of token types (separated only by spaces). No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

By default, perltidy breaks after these token types: % + - * / x != == >= <= =~ !~ < > | & = **= += *= &= <<= &&= -= /= |= >>= ||= //= .= %= ^= x=

And perltidy breaks before these token types by default: . << >> -> && || //

To illustrate, to cause a break after a concatenation operator, '.', rather than before it, the command line would be

\n  -wba="."

As another example, the following command would cause a break before math operators '+', '-', '/', and '*':

\n  -wbb="+ - / *"

These commands should work well for most of the token types that perltidy uses (use --dump-token-types for a list). Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization. However, for a few token types there may be conflicts with hardwired logic which cause unexpected results. One example is curly braces, which should be controlled with the parameter bl provided for that purpose.

" EditorType=string Enabled=false -Value= ValueDefault= [Want left space] @@ -880,7 +785,6 @@ Description="

For those who want more detailed control over the whitespace around tokens, there are four parameters which can directly modify the default whitespace rules built into perltidy for any token. They are:

-wls=s or --want-left-space=s,

-nwls=s or --nowant-left-space=s,

-wrs=s or --want-right-space=s,

-nwrs=s or --nowant-right-space=s.

These parameters are each followed by a quoted string, s, containing a list of token types. No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

To illustrate how these are used, suppose it is desired that there be no space on either side of the token types = + - / *. The following two parameters would specify this desire:

\n  -nwls="= + - / *"    -nwrs="= + - / *"

(Note that the token types are in quotes, and that they are separated by spaces). With these modified whitespace rules, the following line of math:

\n  $root = -$b + sqrt( $b * $b - 4. * $a * $c ) / ( 2. * $a );

becomes this:

\n  $root=-$b+sqrt( $b*$b-4.*$a*$c )/( 2.*$a );

These parameters should be considered to be hints to perltidy rather than fixed rules, because perltidy must try to resolve conflicts that arise between them and all of the other rules that it uses. One conflict that can arise is if, between two tokens, the left token wants a space and the right one doesn't. In this case, the token not wanting a space takes priority.

It is necessary to have a list of all token types in order to create this type of input. Such a list can be obtained by the command --dump-token-types. Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

" EditorType=string Enabled=false -Value= ValueDefault= [Want right space] @@ -889,7 +793,6 @@ Description="

For those who want more detailed control over the whitespace around tokens, there are four parameters which can directly modify the default whitespace rules built into perltidy for any token. They are:

-wls=s or --want-left-space=s,

-nwls=s or --nowant-left-space=s,

-wrs=s or --want-right-space=s,

-nwrs=s or --nowant-right-space=s.

These parameters are each followed by a quoted string, s, containing a list of token types. No more than one of each of these parameters should be specified, because repeating a command-line parameter always overwrites the previous one before perltidy ever sees it.

To illustrate how these are used, suppose it is desired that there be no space on either side of the token types = + - / *. The following two parameters would specify this desire:

\n  -nwls="= + - / *"    -nwrs="= + - / *"

(Note that the token types are in quotes, and that they are separated by spaces). With these modified whitespace rules, the following line of math:

\n  $root = -$b + sqrt( $b * $b - 4. * $a * $c ) / ( 2. * $a );

becomes this:

\n  $root=-$b+sqrt( $b*$b-4.*$a*$c )/( 2.*$a );

These parameters should be considered to be hints to perltidy rather than fixed rules, because perltidy must try to resolve conflicts that arise between them and all of the other rules that it uses. One conflict that can arise is if, between two tokens, the left token wants a space and the right one doesn't. In this case, the token not wanting a space takes priority.

It is necessary to have a list of all token types in order to create this type of input. Such a list can be obtained by the command --dump-token-types. Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization.

WARNING Be sure to put these tokens in quotes to avoid having them misinterpreted by your command shell.

" EditorType=string Enabled=false -Value= ValueDefault= [Break at old comma breakpoints] @@ -897,7 +800,6 @@ Description="

This flag tells perltidy to try to break at all old commas. This is not the default. Normally, perltidy makes a best guess at list formatting, and seldom uses old comma breakpoints. Usually this works well, but consider:

\n    my @list = (1,\n                1, 1,\n                1, 2, 1,\n                1, 3, 3, 1,\n                1, 4, 6, 4, 1,);

The default formatting will flatten this down to one line:

\n    # perltidy (default)\n    my @list = ( 1, 1, 1, 1, 2, 1, 1, 3, 3, 1, 1, 4, 6, 4, 1, );

which hides the structure. Using -boc, plus additional flags to retain the original style, yields

\n    # perltidy -boc -lp -pt=2 -vt=1 -vtc=1\n    my @list = (1,\n                1, 1,\n                1, 2, 1,\n                1, 3, 3, 1,\n                1, 4, 6, 4, 1,);

A disadvantage of this flag is that all tables in the file must already be nicely formatted. For another possibility see the -fs flag in Skipping Selected Sections of Code.

" EditorType=boolean TrueFalse=--break-at-old-comma-breakpoints| -Value=0 ValueDefault=0 [Maximum fields per table] @@ -908,7 +810,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=40 ValueDefault=40 [Comma arrow breakpoints] @@ -919,7 +820,6 @@ Enabled=false MaxVal=3 MinVal=0 -Value=3 ValueDefault=3 [Break at old logical breakpoints] @@ -927,7 +827,6 @@ Description="

By default, if a logical expression is broken at a &&, ||, and, or or, then the container will remain broken. Also, breaks at internal keywords if and unless will normally be retained. To prevent this, and thus form longer lines, use -nbol.

" EditorType=boolean TrueFalse=--break-at-old-logical-breakpoints| -Value=0 ValueDefault=0 [Break at old keyword breakpoints] @@ -935,7 +834,6 @@ Description="

By default, perltidy will retain a breakpoint before keywords which may return lists, such as sort and <map>. This allows chains of these operators to be displayed one per line. Use -nbok to prevent retaining these breakpoints.

" EditorType=boolean TrueFalse=--break-at-old-keyword-breakpoints| -Value=0 ValueDefault=0 [Break at old ternary breakpoints] @@ -943,7 +841,6 @@ Description="

By default, if a conditional (ternary) operator is broken at a :, then it will remain broken. To prevent this, and thereby form longer lines, use -nbot.

" EditorType=boolean TrueFalse=--break-at-old-ternary-breakpoints| -Value=0 ValueDefault=0 [Ignore old breakpoints] @@ -951,7 +848,6 @@ Description="

Use this flag to tell perltidy to ignore existing line breaks to the maximum extent possible. This will tend to produce the longest possible containers, regardless of type, which do not exceed the line length limit.

" EditorType=boolean TrueFalse=--ignore-old-breakpoints| -Value=0 ValueDefault=0 [Keep interior semicolons] @@ -959,7 +855,6 @@ Description="

Use the -kis flag to prevent breaking at a semicolon if there was no break there in the input file. Normally perltidy places a newline after each semicolon which terminates a statement unless several statements are contained within a one-line brace block. To illustrate, consider the following input lines:

\n    dbmclose(%verb_delim); undef %verb_delim;\n    dbmclose(%expanded); undef %expanded;

The default is to break after each statement, giving

\n    dbmclose(%verb_delim);\n    undef %verb_delim;\n    dbmclose(%expanded);\n    undef %expanded;

With perltidy -kis the multiple statements are retained:

\n    dbmclose(%verb_delim); undef %verb_delim;\n    dbmclose(%expanded);   undef %expanded;

The statements are still subject to the specified value of maximum-line-length and will be broken if this maximum is exceeed.

" EditorType=boolean TrueFalse=--keep-interior-semicolons| -Value=0 ValueDefault=0 [Blanks before comments] @@ -967,7 +862,6 @@ Description="

A blank line will be introduced before a full-line comment. This is the default. Use -nbbc or --noblanks-before-comments to prevent such blank lines from being introduced.

" EditorType=boolean TrueFalse=--blanks-before-comments| -Value=0 ValueDefault=0 [Blanks before subs] @@ -975,7 +869,6 @@ Description="

A blank line will be introduced before a sub definition, unless it is a one-liner or preceded by a comment. A blank line will also be introduced before a package statement and a BEGIN and END block. This is the default. The intention is to help display the structure of a program by setting off certain key sections of code. This is negated with -nbbs or --noblanks-before-subs.

" EditorType=boolean TrueFalse=--blanks-before-subs| -Value=0 ValueDefault=0 [Blanks before blocks] @@ -983,7 +876,6 @@ Description="

A blank line will be introduced before blocks of coding delimited by for, foreach, while, until, and if, unless, in the following circumstances:

  • The block is not preceded by a comment.

  • The block is not a one-line block.

  • The number of consecutive non-blank lines at the current indentation depth is at least -lbl (see next section).

This is the default. The intention of this option is to introduce some space within dense coding. This is negated with -nbbb or --noblanks-before-blocks.

" EditorType=boolean TrueFalse=--blanks-before-blocks| -Value=0 ValueDefault=0 [Long block line count] @@ -994,7 +886,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=8 ValueDefault=8 [Maximum consecutive blank lines] @@ -1005,7 +896,6 @@ Enabled=false MaxVal=9999 MinVal=0 -Value=1 ValueDefault=1 [Swallow optional blank lines] @@ -1013,7 +903,6 @@ Description="

All blank lines not required by the above flags, -bbb, -bbs, and -bbc, will be deleted. (But essential blank lines above pod documents will be retained). This is NOT the default.

" EditorType=boolean TrueFalse=--swallow-optional-blank-lines| -Value=0 ValueDefault=0 [Noswallow optional blank lines] @@ -1021,7 +910,6 @@ Description="

Retain blank lines, including those which do not corresponding to flags -bbb, -bbs, and -bbc. This is the default. The number of blanks retained is subject to the limit imposed by --maximum-consecutive-blank-lines, however.

" EditorType=boolean TrueFalse=--noswallow-optional-blank-lines| -Value=0 ValueDefault=0 [Delete all comments] @@ -1029,7 +917,6 @@ Description="

Perltidy can selectively delete comments and/or pod documentation. The command -dac or --delete-all-comments will delete all comments and all pod documentation, leaving just code and any leading system control lines.

" EditorType=boolean TrueFalse=--delete-all-comments| -Value=0 ValueDefault=0 [Delete pod] @@ -1037,7 +924,6 @@ Description="

The command -dp or --delete-pod will remove all pod documentation (but not comments).

" EditorType=boolean TrueFalse=--delete-pod| -Value=0 ValueDefault=0 [Delete block comments] @@ -1045,7 +931,6 @@ Description="

Two commands which remove comments (but not pod) are: -dbc or --delete-block-comments and -dsc or --delete-side-comments. (Hanging side comments will be deleted with block comments here.)

" EditorType=boolean TrueFalse=--delete-block-comments| -Value=0 ValueDefault=0 [Delete side comments] @@ -1053,7 +938,6 @@ Description="

Two commands which remove comments (but not pod) are: -dbc or --delete-block-comments and -dsc or --delete-side-comments. (Hanging side comments will be deleted with block comments here.)

" EditorType=boolean TrueFalse=--delete-side-comments| -Value=0 ValueDefault=0 [Tee all comments] @@ -1061,7 +945,6 @@ Description="

When perltidy writes a formatted text file, it has the ability to also send selected text to a file with a .TEE extension. This text can include comments and pod documentation.

The command -tac or --tee-all-comments will write all comments and all pod documentation.

" EditorType=boolean TrueFalse=--tee-all-comments| -Value=0 ValueDefault=0 [Tee pod] @@ -1069,7 +952,6 @@ Description="

When perltidy writes a formatted text file, it has the ability to also send selected text to a file with a .TEE extension. This text can include comments and pod documentation.

The command -tp or --tee-pod will write all pod documentation (but not comments).

" EditorType=boolean TrueFalse=--tee-pod| -Value=0 ValueDefault=0 [Tee block comments] @@ -1077,7 +959,6 @@ Description="

When perltidy writes a formatted text file, it has the ability to also send selected text to a file with a .TEE extension. This text can include comments and pod documentation.

The commands which write comments (but not pod) are: -tbc or --tee-block-comments and -tsc or --tee-side-comments. (Hanging side comments will be written with block comments here.)

" EditorType=boolean TrueFalse=--tee-block-comments| -Value=0 ValueDefault=0 [Tee side comments] @@ -1085,7 +966,6 @@ Description="

When perltidy writes a formatted text file, it has the ability to also send selected text to a file with a .TEE extension. This text can include comments and pod documentation.

The commands which write comments (but not pod) are: -tbc or --tee-block-comments and -tsc or --tee-side-comments. (Hanging side comments will be written with block comments here.)

" EditorType=boolean TrueFalse=--tee-side-comments| -Value=0 ValueDefault=0 [Look for hash bang] @@ -1093,7 +973,6 @@ Description="

If your script has leading lines of system commands or other text which are not valid perl code, and which are separated from the start of the perl code by a ``hash-bang'' line, ( a line of the form #!...perl ), you must use the -x flag to tell perltidy not to parse and format any lines before the ``hash-bang'' line. This option also invokes perl with a -x flag when checking the syntax. This option was originally added to allow perltidy to parse interactive VMS scripts, but it should be used for any script which is normally invoked with perl -x.

" EditorType=boolean TrueFalse=--look-for-hash-bang| -Value=0 ValueDefault=0 [Making a file unreadable] @@ -1103,7 +982,6 @@ Description="

The goal of perltidy is to improve the readability of files, but there are two commands which have the opposite effect, --mangle and --extrude. They are actually merely aliases for combinations of other parameters. Both of these strip all possible whitespace, but leave comments and pod documents, so that they are essentially reversible. The difference between these is that --mangle puts the fewest possible line breaks in a script while --extrude puts the maximum possible. Note that these options do not provided any meaningful obfuscation, because perltidy can be used to reformat the files. They were originally developed to help test the tokenization logic of perltidy, but they have other uses. One use for --mangle is the following:

\n  perltidy --mangle myfile.pl -st | perltidy -o myfile.pl.new

This will form the maximum possible number of one-line blocks (see next section), and can sometimes help clean up a badly formatted script.

A similar technique can be used with --extrude instead of --mangle to make the minimum number of one-line blocks.

Another use for --mangle is to combine it with -dac to reduce the file size of a perl script.

" EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [MakeMaker] @@ -1111,7 +989,6 @@ Description="

The first $VERSION line of a file which might be eval'd by MakeMaker is passed through unchanged except for indentation. Use --nopass-version-line, or -npvl, to deactivate this feature.

" EditorType=boolean TrueFalse=--nopass-version-line| -Value=0 ValueDefault=0 [AutoLoader] @@ -1119,7 +996,6 @@ Description="

If the AutoLoader module is used, perltidy will continue formatting code after seeing an __END__ line. Use --nolook-for-autoloader, or -nlal, to deactivate this feature.

" EditorType=boolean TrueFalse=--nolook-for-autoloader| -Value=0 ValueDefault=0 [SelfLoader] @@ -1127,5 +1003,4 @@ Description="

Likewise, if the SelfLoader module is used, perltidy will continue formatting code after seeing a __DATA__ line. Use --nolook-for-selfloader, or -nlsl, to deactivate this feature.

" EditorType=boolean TrueFalse=--nolook-for-selfloader| -Value=0 ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_phpCB.ini --- a/indenters/uigui_phpCB.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_phpCB.ini Thu Jun 12 09:15:02 2008 +0000 @@ -21,7 +21,6 @@ Description=Align all assignement statements EditorType=boolean TrueFalse=--align-equal-statements| -Value=1 ValueDefault=1 [Align all assignement statements to a fixed position] @@ -32,7 +31,6 @@ Enabled=false MaxVal=60 MinVal=4 -Value=30 ValueDefault=30 [Allow to insert a space after '('] @@ -40,7 +38,6 @@ Description=Allow to insert a space after start bracket '(' EditorType=boolean TrueFalse=--space-after-start-bracket| -Value=0 ValueDefault=0 [Allow to insert a space after 'if'] @@ -48,7 +45,6 @@ Description=Allow to insert a space after 'if' keyword EditorType=boolean TrueFalse=--space-after-if| -Value=1 ValueDefault=1 [Allow to insert a space after 'switch'] @@ -56,7 +52,6 @@ Description=Allow to insert a space after 'switch' keyword EditorType=boolean TrueFalse=--space-after-switch| -Value=1 ValueDefault=1 [Allow to insert a space after 'while'] @@ -64,7 +59,6 @@ Description=Allow to insert a space after 'while' keyword EditorType=boolean TrueFalse=--space-after-while| -Value=1 ValueDefault=1 [Allow to insert a space after '}'] @@ -72,7 +66,6 @@ Description=Allow to insert a space after starting angle bracket '}' EditorType=boolean TrueFalse=--space-after-end-angle-bracket| -Value=1 ValueDefault=1 [Allow to insert a space before ')'] @@ -80,7 +73,6 @@ Description=Allow to insert a space before end bracket ')' EditorType=boolean TrueFalse=--space-before-end-bracket| -Value=0 ValueDefault=0 [Allow to insert a space before '{'] @@ -88,7 +80,6 @@ Description=Allow to insert a space before starting angle bracket '{' EditorType=boolean TrueFalse=--space-before-start-angle-bracket| -Value=1 ValueDefault=1 [Change comments] @@ -96,7 +87,6 @@ Description="Change '# ...' comments into '// ...' comments
SourceWith --change-shell-comment-to-double-slashes-commentWithout --change-shell-comment-to-double-slashes-comment
<?php

#comment content
//another comment
?>
<?php

// comment content
// another comment
?>
<?php

# comment content
// another comment
?>
" EditorType=boolean TrueFalse=--change-shell-comment-to-double-slashes-comment| -Value=1 ValueDefault=1 [Comment render style] @@ -106,7 +96,6 @@ Description="The following style of comment formating are available:
--comment-rendering-style PEAR--comment-rendering-style PHPDoc
<?php

/**
 * bla bla bla
 *
 * @access public
 */
?>
<?php

/**
* bla bla bla
*
* @access public
*/
?>
" EditorType=multiple Enabled=true -Value=0 ValueDefault=0 [Force large PHP code tag] @@ -114,7 +103,6 @@ Description="Change '<?' and '<%' tokens into '<?php' and '%>' into '?>'" EditorType=boolean TrueFalse=--force-large-php-code-tag| -Value=1 ValueDefault=1 [Glue "&&" to following item] @@ -122,7 +110,6 @@ Description="Glue '&' to following item

With --glue-amperscoreWithout --glue-amperscore
<?php
$value = &$objectInstance;
?>
<?php
$value = & $objectInstance;
?>
" EditorType=boolean TrueFalse=--glue-amperscore| -Value=1 ValueDefault=1 [Increase padding before case statements] @@ -130,7 +117,6 @@ Description="Increase padding before case statements:
With --extra-padding-for-case-statementWithout --extra-padding-for-case-statement
<?php

switch($condition){
    case 1:
        action1();
        break;
    case 2:
        action2();
        break;
    default:
        defaultaction();
        break;
}
?>
<?php

switch($condition){
case 1:
    action1();
    break;
case 2:
    action2();
    break;
default:
    defaultaction();
    break;
}
?>
" EditorType=boolean TrueFalse=--extra-padding-for-case-statement| -Value=0 ValueDefault=0 [Indent with TAB] @@ -138,7 +124,6 @@ Description="If selected, tabulation (ASCII #9) character is used to indent text, elsewhere space (ASCII #32) character is used" EditorType=boolean TrueFalse=--indent-with-tab| -Value=0 ValueDefault=0 [Lowercase for NULL, TRUE and FALSE constants] @@ -146,7 +131,6 @@ Description="Lowercase for NULL, TRUE and FALSE constants as encouraged in PEAR coding standards
With --force-true-false-null-contant-lowercaseWithout --force-true-false-null-contant-lowercase
<?php
if(true){
    if(false){
        $value = null;
    }
}
?>
<?php
if(TRUE){
    if(FALSE){
        $value = NULL;
    }
}
?>
" EditorType=boolean TrueFalse=--force-true-false-null-contant-lowercase| -Value=1 ValueDefault=1 [Padding char count] @@ -157,7 +141,6 @@ Enabled=false MaxVal=8 MinVal=0 -Value=4 ValueDefault=4 [Use "One true brace" formating for functions] @@ -165,5 +148,4 @@ Description="Use 'One true brace' formating for functions
With --one-true-brace-function-declarationWithout --one-true-brace-function-declaration
<?php

function aFunction($param)
{
    // function content
}
?>
<?php

function aFunction($param) {
    // function content
}
?>
" EditorType=boolean TrueFalse=--one-true-brace-function-declaration| -Value=1 ValueDefault=1 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_phpStylist.ini --- a/indenters/uigui_phpStylist.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_phpStylist.ini Thu Jun 12 09:15:02 2008 +0000 @@ -24,7 +24,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=4 ValueDefault=4 [Indent with tabs] @@ -32,7 +31,6 @@ Description="Indent with tabs instead of spaces" EditorType=boolean TrueFalse="--indent_with_tabs|" -Value=0 ValueDefault=0 [Keep redundant lines] @@ -40,7 +38,6 @@ Description="Keep redundant lines" EditorType=boolean TrueFalse="--keep_redundant_lines|" -Value=0 ValueDefault=0 [Space inside parentheses] @@ -48,7 +45,6 @@ Description="Space inside parentheses" EditorType=boolean TrueFalse="--space_inside_parentheses|" -Value=0 ValueDefault=0 [Space outside parentheses] @@ -56,7 +52,6 @@ Description="Space outside parentheses" EditorType=boolean TrueFalse="--space_outside_parentheses|" -Value=0 ValueDefault=0 [Space after comma] @@ -64,7 +59,6 @@ Description="Space after comma" EditorType=boolean TrueFalse="--space_after_comma|" -Value=0 ValueDefault=0 [Space around assignment] @@ -72,7 +66,6 @@ Description="Space around = .= += -= *= /= <<<" EditorType=boolean TrueFalse="--space_around_assignment|" -Value=0 ValueDefault=0 [Align block +3 assigned variables] @@ -80,7 +73,6 @@ Description="Align block +3 assigned variables" EditorType=boolean TrueFalse="--align_var_assignment|" -Value=0 ValueDefault=0 [Space around comparison] @@ -88,7 +80,6 @@ Description="Space around == === != !== > >= < <=" EditorType=boolean TrueFalse="--space_around_comparison|" -Value=0 ValueDefault=0 [Space around arithmetic] @@ -96,7 +87,6 @@ Description="Space around - + * / %" EditorType=boolean TrueFalse="--space_around_arithmetic|" -Value=0 ValueDefault=0 [Space around logical] @@ -104,7 +94,6 @@ Description="Space around && || AND OR XOR << >>" EditorType=boolean TrueFalse="--space_around_logical|" -Value=0 ValueDefault=0 [Space around colon and question] @@ -112,7 +101,6 @@ Description="Space around ? :" EditorType=boolean TrueFalse="--space_around_colon_question|" -Value=0 ValueDefault=0 [Blank line before keyword] @@ -120,7 +108,6 @@ Description="Blank line before keyword" EditorType=boolean TrueFalse="--line_before_function|" -Value=0 ValueDefault=0 [Opening bracket on next line] @@ -128,7 +115,6 @@ Description="Opening bracket on next line" EditorType=boolean TrueFalse="--line_before_curly_function|" -Value=0 ValueDefault=0 [Blank line below opening bracket] @@ -136,7 +122,6 @@ Description="Blank line below opening bracket" EditorType=boolean TrueFalse="--line_after_curly_function|" -Value=0 ValueDefault=0 [Space around ->] @@ -144,7 +129,6 @@ Description="Space around ->" EditorType=boolean TrueFalse="--space_around_obj_operator|" -Value=0 ValueDefault=0 [Space around ::] @@ -152,7 +136,6 @@ Description="Space around ::" EditorType=boolean TrueFalse="--space_around_double_colon|" -Value=0 ValueDefault=0 [Space before parentheses] @@ -160,7 +143,6 @@ Description="Space between keyword and opening parentheses" EditorType=boolean TrueFalse="--space_after_if|" -Value=0 ValueDefault=0 [Keep else/elseif along with bracket] @@ -168,7 +150,6 @@ Description="Keep else/elseif along with bracket" EditorType=boolean TrueFalse="--else_along_curly|" -Value=0 ValueDefault=0 [Opening bracket on next line] @@ -176,7 +157,6 @@ Description="Opening bracket on next line" EditorType=boolean TrueFalse="--line_before_curly|" -Value=0 ValueDefault=0 [Add missing brackets] @@ -184,7 +164,6 @@ Description="Add missing brackets to single line structs" EditorType=boolean TrueFalse="--add_missing_braces|" -Value=0 ValueDefault=0 [Blank line after case "break"] @@ -192,7 +171,6 @@ Description="Blank line after case 'break'" EditorType=boolean TrueFalse="--line_after_break|" -Value=0 ValueDefault=0 [Space between "for" elements] @@ -200,7 +178,6 @@ Description="Space between 'for' elements" EditorType=boolean TrueFalse="--space_inside_for|" -Value=0 ValueDefault=0 [Extra indent for "Case" and "Default"] @@ -208,7 +185,6 @@ Description="Extra indent for 'Case' and 'Default'" EditorType=boolean TrueFalse="--indent_case|" -Value=0 ValueDefault=0 [Opening array parentheses on next line] @@ -216,7 +192,6 @@ Description="Opening array parentheses on next line" EditorType=boolean TrueFalse="--line_before_array|" -Value=0 ValueDefault=0 [Non-empty arrays as vertical block] @@ -224,7 +199,6 @@ Description="Non-empty arrays as vertical block" EditorType=boolean TrueFalse="--vertical_array|" -Value=0 ValueDefault=0 [Align block +3 assigned array elements] @@ -232,7 +206,6 @@ Description="Align block +3 assigned array elements" EditorType=boolean TrueFalse="--align_array_assignment|" -Value=0 ValueDefault=0 [Space around double arrow] @@ -240,7 +213,6 @@ Description="Space around double arrow" EditorType=boolean TrueFalse="--space_around_double_arrow|" -Value=0 ValueDefault=0 [Concatenation as vertical block] @@ -248,7 +220,6 @@ Description="Concatenation as vertical block" EditorType=boolean TrueFalse="--vertical_concat|" -Value=0 ValueDefault=0 [Space around concat elements] @@ -256,7 +227,6 @@ Description="Space around concat elements" EditorType=boolean TrueFalse="--space_around_concat|" -Value=0 ValueDefault=0 [Blank line before multi-line comment] @@ -264,7 +234,6 @@ Description="Blank line before multi-line comment (/*)" EditorType=boolean TrueFalse="--line_before_comment_multi|" -Value=0 ValueDefault=0 [Blank line after multi-line comment] @@ -272,7 +241,6 @@ Description="Blank line after multi-line comment (/*)" EditorType=boolean TrueFalse="--line_after_comment_multi|" -Value=0 ValueDefault=0 [Blank line before single line comments] @@ -280,7 +248,6 @@ Description="Blank line before single line comments (//)" EditorType=boolean TrueFalse="--line_before_comment|" -Value=0 ValueDefault=0 [Blank line after single line comments] @@ -288,5 +255,4 @@ Description="Blank line after single line comments (//)" EditorType=boolean TrueFalse="--line_after_comment|" -Value=0 ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_php_Beautifier.ini --- a/indenters/uigui_php_Beautifier.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_php_Beautifier.ini Thu Jun 12 09:15:02 2008 +0000 @@ -24,7 +24,6 @@ Enabled=true MaxVal=99 MinVal=0 -Value=4 ValueDefault=4 [Indent With Tabs] @@ -35,7 +34,6 @@ Enabled=false MaxVal=99 MinVal=0 -Value=1 ValueDefault=1 [Add Header] @@ -45,75 +43,66 @@ Description="Adds header information to a file. These can be Php, BSD, Apache, LGPL or Pear license info." EditorType=multiple Enabled=true -Value=0 -ValueDefault=0 - -[Newline Class] -Category=0 -Description=Add a new line after class before opening brace. -EditorType=boolean -TrueFalse="-l \"Pear(newline_class=true)\"|-l \"Pear(newline_class=false)\"" -Value=1 -ValueDefault=1 - -[Newline Function] -Category=0 -Description=Add a new line after function before opening brace. -EditorType=boolean -TrueFalse="-l \"Pear(newline_function=true)\"|-l \"Pear(newline_function=false)\"" -Value=1 -ValueDefault=1 - -[New Lines Before] -CallName="-l \"NewLines(before=" -Category=0 -Description="Add new lines before specific keywords. Keywords are separated by a single colon. Example: if:switch:T_CLASS
The string MUST end with a closing brace and an escaped double quote." -EditorType=string -Enabled=false -Value= -ValueDefault="if:switch:T_CLASS)\"" - -[New Lines After] -CallName="-l \"NewLines(after=" -Category=0 -Description="Add new lines after specific keywords. Keywords are separated by a single colon. Example: T_COMMENT:function
The string MUST end with a closing brace and an escaped double quote." -EditorType=string -Enabled=false -Value= -ValueDefault="T_COMMENT:function)\"" - -[Arrays Nested] -Category=0 -Description= -EditorType=boolean -TrueFalse="-l \"ArrayNested()\"|" -Value=0 -ValueDefault=0 - -[Lowercase] -Category=0 -Description=Lowercases all control structures. -EditorType=boolean -TrueFalse="-l \"Lowercase()\"|" -Value=0 -ValueDefault=0 - -[List Class And Functions] +ValueDefault=0 + +[Newline Class] +Category=0 +Description=Add a new line after class before opening brace. +EditorType=boolean +TrueFalse="-l \"Pear(newline_class=true)\"|-l \"Pear(newline_class=false)\"" +ValueDefault=1 + +[Newline Function] +Category=0 +Description=Add a new line after function before opening brace. +EditorType=boolean +TrueFalse="-l \"Pear(newline_function=true)\"|-l \"Pear(newline_function=false)\"" +ValueDefault=1 + +[New Lines Before] +CallName="-l \"NewLines(before=" +Category=0 +Description="Add new lines before specific keywords. Keywords are separated by a single colon. Example: if:switch:T_CLASS
The string MUST end with a closing brace and an escaped double quote." +EditorType=string +Enabled=false +ValueDefault="if:switch:T_CLASS)\"" + +[New Lines After] +CallName="-l \"NewLines(after=" +Category=0 +Description="Add new lines after specific keywords. Keywords are separated by a single colon. Example: T_COMMENT:function
The string MUST end with a closing brace and an escaped double quote." +EditorType=string +Enabled=false +ValueDefault="T_COMMENT:function)\"" + +[Arrays Nested] +Category=0 +Description= +EditorType=boolean +TrueFalse="-l \"ArrayNested()\"|" +ValueDefault=0 + +[Lowercase] +Category=0 +Description=Lowercases all control structures. +EditorType=boolean +TrueFalse="-l \"Lowercase()\"|" +ValueDefault=0 + +[List Class And Functions] Category=0 Choices="-l \"ListClassFunction(list_classes=true)\"|-l \"ListClassFunction(list_functions=true)\"|-l \"ListClassFunction()\"" -ChoicesReadable="List Classes|List Functions|List Classes And Functions" -Description=Create a list of functions and classes in the script By default, this Filter puts the list at the beggining of the script. If you want it in another position, put a comment like that 
 // Class and Function List
The script lookup for the string 'Class and Function List' in a comment and replace the entire comment with the list. +ChoicesReadable="List Classes|List Functions|List Classes And Functions" +Description=Create a list of functions and classes in the script By default, this Filter puts the list at the beggining of the script. If you want it in another position, put a comment like that 
 // Class and Function List
The script lookup for the string 'Class and Function List' in a comment and replace the entire comment with the list. EditorType=multiple Enabled=false -Value=0 -ValueDefault=0 - -[Indent Styles] +ValueDefault=0 + +[Indent Styles] Category=0 Choices="-l \"IndentStyles(style=k&r)\"|-l \"IndentStyles(style=allman)\"|-l \"IndentStyles(style=whitesmiths)\"|-l \"IndentStyles(style=gnu)\"" -ChoicesReadable="K&R|Allman|Whitesmiths|GNU" -Description= +ChoicesReadable="K&R|Allman|Whitesmiths|GNU" +Description= EditorType=multiple Enabled=false -Value=0 -ValueDefault=0 +ValueDefault=0 diff -r d2b86d544678 -r 6dda59f4cc5a indenters/uigui_tidy.ini --- a/indenters/uigui_tidy.ini Thu Jun 12 06:57:31 2008 +0000 +++ b/indenters/uigui_tidy.ini Thu Jun 12 09:15:02 2008 +0000 @@ -22,7 +22,6 @@ EditorType=boolean Enabled=true TrueFalse=quiet:yes|quiet:no -Value=0 ValueDefault=1 [Uppercase tags] @@ -31,7 +30,6 @@ EditorType=boolean Enabled=false TrueFalse=uppercase-tags:yes|uppercase-tags:no -Value=1 ValueDefault=0 [accessibility-check] @@ -42,7 +40,6 @@ Enabled=true MaxVal=3 MinVal=0 -Value=0 ValueDefault=0 [add-xml-decl] @@ -51,7 +48,6 @@ EditorType=boolean Enabled=false TrueFalse=add-xml-decl:yes|add-xml-decl:no -Value=1 ValueDefault=0 [add-xml-space] @@ -60,7 +56,6 @@ EditorType=boolean Enabled=false TrueFalse=add-xml-space:yes|add-xml-space:no -Value=0 ValueDefault=0 [alt-text] @@ -69,7 +64,6 @@ Description="-This option specifies the default 'alt=' text Tidy uses for attributes. This feature is dangerous as it suppresses further accessibility warnings. You are responsible for making your documents accessible to people who can not see the images!" EditorType=string Enabled=false -Value= ValueDefault= [ascii-chars] @@ -78,7 +72,6 @@ EditorType=boolean Enabled=false TrueFalse=ascii-chars:yes|ascii-chars:no -Value=0 ValueDefault=0 [assume-xml-procins] @@ -87,7 +80,6 @@ EditorType=boolean Enabled=false TrueFalse=assume-xml-procins:yes|assume-xml-procins:no -Value=0 ValueDefault=0 [bare] @@ -96,7 +88,6 @@ EditorType=boolean Enabled=false TrueFalse=bare:yes|bare:no -Value=0 ValueDefault=0 [break-before-br] @@ -105,7 +96,6 @@ EditorType=boolean Enabled=false TrueFalse=break-before-br:yes|break-before-br:no -Value=0 ValueDefault=0 [char-encoding] @@ -114,7 +104,6 @@ Description="This option specifies the character encoding Tidy uses for both the input and output. For ascii, Tidy will accept Latin-1 (ISO-8859-1) character values, but will use entities for all characters whose value > 127. For raw, Tidy will output values above 127 without translating them into entities. For latin1, characters above 255 will be written as entities. For utf8, Tidy assumes that both input and output is encoded as UTF-8. You can use iso2022 for files encoded using the ISO-2022 family of encodings e.g. ISO-2022-JP. For mac and win1252, Tidy will accept vendor specific character values, but will use entities for all characters whose value > 127." EditorType=multiple Enabled=false -Value=1 ValueDefault=1 [clean] @@ -123,7 +112,6 @@ EditorType=boolean Enabled=false TrueFalse=clean:yes|clean:no -Value=0 ValueDefault=0 [css-prefix] @@ -132,7 +120,6 @@ Description="-This option specifies the prefix that Tidy uses for styles rules. By default, 'c' will be used." EditorType=string Enabled=false -Value= ValueDefault= [decorate-inferred-ul] @@ -141,7 +128,6 @@ EditorType=boolean Enabled=false TrueFalse=decorate-inferred-ul:yes|decorate-inferred-ul:no -Value=0 ValueDefault=0 [doctype] @@ -150,7 +136,6 @@ Description=This option specifies the DOCTYPE declaration generated by Tidy. If set to 'omit' the output won't contain a DOCTYPE declaration. If set to 'auto' (the default) Tidy will use an educated guess based upon the contents of the document. If set to 'strict', Tidy will set the DOCTYPE to the strict DTD. If set to 'loose', the DOCTYPE is set to the loose (transitional) DTD. Alternatively, you can supply a string for the formal public identifier (FPI). For example: doctype: '-//ACME//DTD HTML 3.14159//EN' If you specify the FPI for an XHTML document, Tidy will set the system identifier to an empty string. For an HTML document, Tidy adds a system identifier only if one was already present in order to preserve the processing mode of some browsers. Tidy leaves the DOCTYPE for generic XML documents unchanged. --doctype omit implies --numeric-entities yes. This option does not offer a validation of the document conformance. EditorType=multiple Enabled=false -Value=1 ValueDefault=1 [drop-empty-paras] @@ -159,7 +144,6 @@ EditorType=boolean Enabled=false TrueFalse=drop-empty-paras:yes|drop-empty-paras:no -Value=1 ValueDefault=1 [drop-font-tags] @@ -168,7 +152,6 @@ EditorType=boolean Enabled=false TrueFalse=drop-font-tags:yes|drop-font-tags:no -Value=0 ValueDefault=0 [drop-proprietary-attributes] @@ -177,7 +160,6 @@ EditorType=boolean Enabled=false TrueFalse=drop-proprietary-attributes:yes|drop-proprietary-attributes:no -Value=0 ValueDefault=0 [enclose-block-text] @@ -186,7 +168,6 @@ EditorType=boolean Enabled=false TrueFalse=enclose-block-text:yes|enclose-block-text:no -Value=0 ValueDefault=0 [enclose-text] @@ -195,7 +176,6 @@ EditorType=boolean Enabled=false TrueFalse=enclose-text:yes|enclose-text:no -Value=0 ValueDefault=0 [escape-cdata] @@ -204,7 +184,6 @@ EditorType=boolean Enabled=false TrueFalse=escape-cdata:yes|escape-cdata:no -Value=0 ValueDefault=0 [fix-backslash] @@ -213,7 +192,6 @@ EditorType=boolean Enabled=false TrueFalse=fix-backslash:yes|fix-backslash:no -Value=1 ValueDefault=1 [fix-bad-comments] @@ -222,7 +200,6 @@ EditorType=boolean Enabled=false TrueFalse=fix-bad-comments:yes|fix-bad-comments:no -Value=1 ValueDefault=1 [fix-uri] @@ -231,7 +208,6 @@ EditorType=boolean Enabled=false TrueFalse=fix-uri:yes|fix-uri:no -Value=1 ValueDefault=1 [hide-comments] @@ -240,7 +216,6 @@ EditorType=boolean Enabled=false TrueFalse=hide-comments:yes|hide-comments:no -Value=0 ValueDefault=0 [hide-endtags] @@ -249,7 +224,6 @@ EditorType=boolean Enabled=false TrueFalse=hide-endtags:yes|hide-endtags:no -Value=0 ValueDefault=0 [indent] @@ -258,7 +232,6 @@ EditorType=boolean Enabled=false TrueFalse=indent:yes|indent:no -Value=1 ValueDefault=0 [indent-attributes] @@ -267,7 +240,6 @@ EditorType=boolean Enabled=false TrueFalse=indent-attributes:yes|indent-attributes:no -Value=0 ValueDefault=0 [indent-cdata] @@ -276,7 +248,6 @@ EditorType=boolean Enabled=false TrueFalse=indent-cdata:yes|indent-cdata:no -Value=0 ValueDefault=0 [indent-spaces] @@ -287,7 +258,6 @@ Enabled=true MaxVal=5000 MinVal=0 -Value=2 ValueDefault=2 [input-encoding] @@ -296,7 +266,6 @@ Description=This option specifies the character encoding Tidy uses for the input. See char-encoding for more info. EditorType=multiple Enabled=false -Value=4 ValueDefault=4 [input-xml] @@ -305,7 +274,6 @@ EditorType=boolean Enabled=false TrueFalse=input-xml:yes|input-xml:no -Value=0 ValueDefault=0 [join-classes] @@ -314,7 +282,6 @@ EditorType=boolean Enabled=false TrueFalse=join-classes:yes|join-classes:no -Value=0 ValueDefault=0 [join-styles] @@ -323,7 +290,6 @@ EditorType=boolean Enabled=false TrueFalse=join-styles:yes|join-styles:no -Value=1 ValueDefault=1 [literal-attributes] @@ -332,7 +298,6 @@ EditorType=boolean Enabled=false TrueFalse=literal-attributes:yes|literal-attributes:no -Value=0 ValueDefault=0 [logical-emphasis] @@ -341,7 +306,6 @@ EditorType=boolean Enabled=false TrueFalse=logical-emphasis:yes|logical-emphasis:no -Value=0 ValueDefault=0 [lower-literals] @@ -350,7 +314,6 @@ EditorType=boolean Enabled=false TrueFalse=lower-literals:yes|lower-literals:no -Value=1 ValueDefault=1 [markup] @@ -359,7 +322,6 @@ EditorType=boolean Enabled=false TrueFalse=markup:yes|markup:no -Value=1 ValueDefault=1 [merge-divs] @@ -369,7 +331,6 @@ Description="Can be used to modify behavior of -c (--clean yes) option. This option specifies if Tidy should merge nested
such as '
...
'. If set to 'auto', the attributes of the inner
are moved to the outer one. As well, nested
with ID attributes are not merged. If set to 'yes', the attributes of the inner
are discarded with the exception of 'class' and 'style'." EditorType=multiple Enabled=false -Value=0 ValueDefault=0 [ncr] @@ -378,7 +339,6 @@ EditorType=boolean Enabled=false TrueFalse=ncr:yes|ncr:no -Value=1 ValueDefault=1 [new-blocklevel-tags] @@ -387,7 +347,6 @@ Description="This option specifies new block-level tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you can't change the content model for elements such as ,
    ,
      and
      . This option is ignored in XML mode." EditorType=string Enabled=false -Value= ValueDefault= [new-empty-tags] @@ -396,7 +355,6 @@ Description="This option specifies new empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Remember to also declare empty tags as either inline or blocklevel. This option is ignored in XML mode." EditorType=string Enabled=false -Value= ValueDefault= [new-inline-tags] @@ -405,7 +363,6 @@ Description="This option specifies new non-empty inline tags. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. This option is ignored in XML mode." EditorType=string Enabled=false -Value= ValueDefault= [new-pre-tags] @@ -414,7 +371,6 @@ Description="This option specifies new tags that are to be processed in exactly the same way as HTML's 
       element. This option takes a space or comma separated list of tag names. Unless you declare new tags, Tidy will refuse to generate a tidied file if the input includes previously unknown tags. Note you can not as yet add new CDATA elements (similar to