Just add ?w=1 to the Github URL to ignore whitespace.
That's not the problem. The problem is the person making the PR projecting their own style choices instead of following the project's. They explicitly changed other contributors' code in a negative (stylistic) way.
The space following the "#" is meant to signify that the preprocessor directive is nested one layer deep. You can see that this style is used in other files, like here: https://github.com/vim/vim/blob/master/src/gui.c#L40-L42
So no, I think this is Bram bringing one file's indentation style in line with the rest of the project.
That's not the problem. The problem is the person making the PR projecting their own style choices instead of following the project's. They explicitly changed other contributors' code in a negative (stylistic) way.
Bram is the creator and maintainer of vim and the author of that patch. https://groups.google.com/forum/#!topic/vim_dev/QCj8lIntzCk The space following the "#" is meant to signify that the preprocessor directive is nested one layer deep. You can see that this style is used in other files, like here: https://github.com/vim/vim/blob/master/src/gui.c#L40-L42 So no, I think this is Bram bringing one file's indentation st…
> The space following the "#" is meant to signify that the preprocessor directive is nested one layer deep.
Ohhh! I really like that idea. I may adopt that, though I tend to avoid most preprocessor usage so I have little opportunity to try it out.
Tsk tsk! Commit mixes gratuitous whitespace changes with semantics. Oh, why? You just don't do that. Come on, "git commit --patch", pick out the changes ...
Tsk tsk! Commit mixes gratuitous whitespace changes with semantics. Oh, why? You just don't do that. Come on, "git commit --patch", pick out the changes ...