> That is OK. As long as it is used as a diagnose tool and not being mandatory
> I am all for it.
Done. It can be a good diagnostic tool at this stage. The recommended usage is
uncrustify -c development/coding/uncrustify.cfg file
diff file file.uncrustify
Later on, if all the diffs produced by
On Monday 05 November 2007 21:53:31 Bo Peng wrote:
> > > There are 138 options and I have not gone through them one by one.
> > > Most, if not all, your preferences can be achieved by changing
> > > uncrustify.cfg.
> >
> > Possibly, but _I_ won't do that ;-)
>
> Jose,
>
> Do you agree to put this f
> > There are 138 options and I have not gone through them one by one.
> > Most, if not all, your preferences can be achieved by changing
> > uncrustify.cfg.
>
> Possibly, but _I_ won't do that ;-)
Jose,
Do you agree to put this file (uncrustify.cfg) under
development/coding? With some adjustment
On Mon, Nov 05, 2007 at 03:20:51PM -0600, Bo Peng wrote:
> > ASpell::ASpell(BufferParams const &, string const & lang)
> >
> > by
> >
> > ASpell::ASpell(BufferParams const & , string const & lang)
> >
> >
> > I think I prefer the original version.
> > So, as I said: Checking patches with it is ni
> ASpell::ASpell(BufferParams const &, string const & lang)
>
> by
>
> ASpell::ASpell(BufferParams const & , string const & lang)
>
>
> I think I prefer the original version.
> So, as I said: Checking patches with it is nice, but as it stands I
> would not like to see it ruling our style.
There
On Mon, Nov 05, 2007 at 02:09:20PM +1800, Bo Peng wrote:
> Dear all,
>
> It is not always easy to write code that conforms to lyx' coding rules
> so I have been searching for an open-source code beautifier. I have
> tried bcpp, greatcode, astyle, indent etc, but none of them is
> powerful enough.
> And you call that a good beautifier?! ;)
If can help us locate and fix most of the space problems, and I think
this is very helpful.
Attached please find an update configuration file generated by
'uncrustify -c configfile --update-config-with-doc'.
Bo
uncrustify.cfg
Description: Binary data
Bo Peng wrote:
Personally, I don't like code beautifiers that much. There are just too
many times when I like to do things which I doubt a code beautifier
would preserve (and I want to do it that way nonetheless). E.g: look for
"if (// not for ArabTeX" in output_latex.cpp.
Uncrustify seem
> Personally, I don't like code beautifiers that much. There are just too
> many times when I like to do things which I doubt a code beautifier
> would preserve (and I want to do it that way nonetheless). E.g: look for
> "if (// not for ArabTeX" in output_latex.cpp.
Uncrustify seems to preserv
Bo Peng wrote:
Dear all,
It is not always easy to write code that conforms to lyx' coding rules
so I have been searching for an open-source code beautifier. I have
tried bcpp, greatcode, astyle, indent etc, but none of them is
powerful enough. I tried again yesterday and found that uncrustify
(h
Bo Peng wrote:
> Dear all,
>
> It is not always easy to write code that conforms to lyx' coding rules
> so I have been searching for an open-source code beautifier. I have
> tried bcpp, greatcode, astyle, indent etc, but none of them is
> powerful enough. I tried again yesterday and found that un
Dear all,
It is not always easy to write code that conforms to lyx' coding rules
so I have been searching for an open-source code beautifier. I have
tried bcpp, greatcode, astyle, indent etc, but none of them is
powerful enough. I tried again yesterday and found that uncrustify
(http://uncrustify.
12 matches
Mail list logo
