Re: [Libphidget-devel] More on indent

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

On Tue, 2002-09-10 at 21:24, Vadim Tkachenko wrote:
> According to Jack Strohm:
> 
> > > 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                     
> 
> The -ndj option is undocumented in my manual, but I've looked it up on
> Internet, it can be omitted 'cause it's the default
> 
> > > --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"

I cut and paste the error, not sure where the single - came from.

> 
> Are you sure *that* was the message? There's no such option in the text
> above... And all the long options start with double dash.
> 
> > 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.
> 
> Will fix that.

please, be bad to loose all changes before you check in cause you called
"make indent"


>  
> > 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.
> 
> So, would it be OK if I just commit it as it is with the above options and
> merge it back to main branch?

Yeah, as long as we are sure it won't flip/flop on us like the last
style :-)