David E Jones wrote:
>
> There may be lots of other reasons bantered here and in other
> discussions, but for my money when working with a group there is one
> simple reason: to avoid commits with changes that are formatting only.
> Those can number in the dozens of lines for one line of actual
> functional change, making it nearly impossible to find in a larger patch.
It actually comes down to consistency. I am perfectly fine with
spaces *or* tabs, as long as *all* lines in a file are the same. I've
worked with several sources over the years, and I always emulate
whatever formatting is already there.
For OfBiz, we as a project have decided to follow the sun java
conventions: 4 space indents, no tabs, { on the same line, spaces
around operators, no space around (), space after cast, space after
comma, space after ; in for(;;;), no spaces/tabs at the end of
line(pet peeve).
It's just common courtesy.
ps: I have vim configured to highlight spacing issues with a red
background. If there are mixed space/tabs at the beginning of the
line, or trailing spaces on a line, it's very apparent.
pps: There's no reason to keep the *entire* previous email(s) in the
quote. That's what mail threading is for.
ppps: The computer is more efficient than any human. Configure the
system to do this for you automatically.
