Re: [Libphidget-devel] More on indent

[Jack S. <js...@ja...>]

On Tue, 2002-09-10 at 12:21, Vadim Tkachenko wrote:
> Hello,
> 
> Indeed, indent is fragile.
> 
> Some options break the code altogether (--dont-break-procedure-type). Some
> options cause the results to be different on each run
> (--braces-on-struct-decl-line). Some options, though, yield a repeatable
> result. After some fiddling, I've found the set that I can live with:
> 
> --no-blank-lines-after-declarations                                                           
> --blank-lines-after-procedures                                                                
> --no-blank-lines-after-commas
> --break-before-boolean-operator    
> --braces-on-if-line
> --brace-indent4
> --braces-after-struct-decl-line
> --no-comment-delimiters-on-blank-lines
> --cuddle-else 
> --else-endif-column1
> --space-after-cast
> --declaration-indentation4
> -ndj                     
> --dont-format-first-column-comments
> --dont-format-comments             
> --honour-newlines     
> --indent-level4  
> --parameter-indentation5
> --continue-at-parentheses
> --no-space-after-function-call-names
> --no-space-after-parentheses
> --procnames-start-lines
> --dont-star-comments   
> --leave-optional-blank-lines
> --line-length128
> 
> Cut'n'paste it into ./indent.rules in INDENT branch and see if it is OK with
> you, and if so, let's stop right there - enough time wasted. It's all my
> fault ;/

k I finally got home,

I just updated to the INDENT revision.

[jstrohm@oishi libphidget]$ make indent
indent: unknown option "-blank-lines-after-block-comments"
.
.
.
.

and then woops! all the source code files were empty   :-(

no problem, but need to add a something so that if indent dies it
doesn't kill the original file.


started over again, and set up the configuration like you said above,
now if this is the style it's checked in as, and we can run indent-local
to get our own preferences it's fine with me, but I personally don't
care for it.