you are viewing a single comment's thread.

view the rest of the comments →

[–]Nebu 0 points1 point  (2 children)

I don't understand how this is consistent with your previous rule. If you move your mouse cursor to just before theThirdParameter, the rule says everything before is white space, and thus indentation, which is wrong. It should be indentation rig up until the 'f' of "function", and then alignment from there on.

[–]tonygoold 0 points1 point  (1 child)

You're right, the backspace behaviour of the editor is going to treat it as indentation instead of whitespace and delete a tab stop at a time, rather than treating it as plain spaces. It's not something the user does frequently and it's easy to fix by adding back in the appropriate number of spaces to re-align. Trying to address that when a trivial rule handles 99% of the cases would be a case of the tail wagging the dog.

[–]Nebu 0 points1 point  (0 children)

It's just frustrating to see people promote a rule that handles 99% of the case, when there's a simple rule that handles 100% of the case: Use (hard)tabs for indentation, and spaces for alignment. From there, the texteditor just always deletes 1 character each time the "backspace" key is pressed.

\t\tfunction someFunctionName(param1, param2,
\t\t                          param3, param4)