5 ms·
So you have a rule, "every file gets formatted in <style> before it gets checked in - edit in any style you please, but reformat it after".
by JulianMorrison 17y ago
So you have a rule, "every file gets formatted in <style> before it gets checked in - edit in any style you please, but reformat it after".
- jrockway 17y agoExactly. This is almost common sense; I have never specifically told anyone "to commit to my repository, make sure you indent in such-and-such way". I have also never been told this rule; if I notice that every indentation level is two spaces more than the last level, I assume I should do the same. (If it's a whole project, I just add the changed settings to my .eproject file, and never think about it again. Very simple.) I have found, in general, that it's the very new or very bad programmers that want to quibble over style. Everyone I've worked with is fine with anything. In the long run, it just doesn't matter at all.
- __david__ 17y agoThe rules is somewhat common sense. But I have had to tell people the rule (mostly to very new programmers). Interestingly I haven't found that they wanted to quibble about style, they just didn't notice they were doing things differently. Putting the correct thing in their .emacs usually clears things up (show-trailing-whitespace throws your loose whitespace habits right in your face).
- ubernostrum 17y agoYeah, and most projects do -- it's called a style guide.