Ok I really really really can't deal with 80, I have tried it for a while now and it forces to make new lines on the most simple lines (Initialisations) that cannot be simplified any further and where reducing the indent by refactoring the inside (e.g. of an if conditional) into an extra-function also makes no sense. Breaking them into two lines makes such lines utterly annoying to read and it happens regularly. This clearly is not supporting readability, I'd say.
Winner can decide about the limit or can be challenged by another team member.
Shall we make it 100 then?
Well, that's why I see the 80/X limit as a guidelines rather than 100% enforced thing. Sometimes it makes sense and it's fine to cross the limit.
Code in general should be no more than 80 characters long per line. Long lines are more difficult to read and may lead to general bad programming practice. However there are cases when lines longer than 80 characters are appropriate, and in such cases it's allowed. However, no code line, ever, should be longer than 120 characters. Comments in code should be split to lines at 120-character boundary.
You add a guide at 80 and one at 120.
I want cuhlurrrss. Otherwise this is exactly what I want though.
What do Paul and Martin think of the soft limit at 80 and the hard one at 120?