I would agree that consistency is key. You can't rely on IDE pretty-printing to save the day, because some of your developers may not like using an IDE, and because when you're trawling through a code base of thousands of source files, it's simply not feasible to pretty print all the files when you start working on them, and perform a roll-back afterwards so your VCS doesn't try to commit back all the changes (clogging the repository with needless updates that burden everyone).
I would suggest standardizing at least the following (in decreasing order of importance):
- Whitespace (it's easiest if you choose a style that conforms to the automatic pretty-printing of some shared tool)
- Naming (files and folders, classes, functions, variables, ...)
- Commenting (using a format that allows automatic documentation generation)
