opened
pjrobertson
username_0
So, based on Etienne's recent PR on tabs/spaces, and after watching [this](http://www.bbc.co.uk/academy/technology/article/art20150206154333467) video where a GitHub guy was saying they're now using CI for much more than just tests (CSS validation etc. - watch the video!) I thought it would be interesting if we did the same.

I've butchered Etienne's gist ruby script (and probably written very bad ruby code) and have attempted to write a script that will check all newly added lines in .m/.h files and check to make sure they start with tabs and not spaces
Add a new CI test to make sure we use tabs and not spaces
issue
created
pjrobertson
username_0
P.S. I know @username_2 was [against](https://github.com/quicksilver/Quicksilver/pull/2021#issuecomment-72402365) using 'custom' scripts originally, but maybe I can persuade him here... ;-)

There's definitely scope for us to expand this out in the future - adding in more scripts and stuff, and it's not exactly 'difficult' to remember (although maybe we should have a directory for travis stuff kept separate).
Perhaps some day we could even have some kind of 'real' CI that meant when plugin PRs are merged they are automatically built and pushed to the plugin repo :-)
comment
created
tiennou
username_1
God, I feel like the pesky guy ;-). I'm not too fond of dot-hiding the script, could it be moved under `/Scripts` (or wherever we have those, I don't remember the name offhand) ?
comment
created
pjrobertson
username_0
...probably a good idea :-)
I've given it its own folder now, and have removed my test commits. It works as expected (fails when there are lines with spaces) so that's all good :-)
comment
created
skurfer
username_2
Man, you guys are really going ahead with this tab stuff, eh?

* Why is the Map stuff in here? It should already be on `master`.
* I was against using a custom script to do something Travis should handle natively. This doesn’t bother me too much.
* My first thought was “What a bullshit reason to fail tests!” but if you were forcing spaces instead of tabs, I’d think “Oh, yeah. We need that!” so… my argument is probably not objective. 😀
* I see the new Ruby script is indented using spaces, which is hilarious. At least it shows we’re not *complete* animals. 🐗
* Do you want to say that this “fixes” #2050?
comment
created
pjrobertson
username_0
Hahaha, well that's just hilarious! Maybe we need to decide what 'coding style' we have for ruby though... what if we want to use spaces? ;-)
comment
created
skurfer
username_2
Better. Were the tests not getting called via `xctool` before? I thought they were running somehow.
comment
created
pjrobertson
username_0
I basically copied the exact same command that [Travis was calling](https://travis-ci.org/quicksilver/Quicksilver/builds/78277014#L122) before I made these changes.
If you look at the logs for [tests on this branch](https://travis-ci.org/quicksilver/Quicksilver/builds/81773128), you'll see exactly the same thing is run/log output is generated.
comment
created
pjrobertson
username_0
...I've also switched check_indent to use tabs...!
comment
created
pjrobertson
username_0
Can this be merged? Every day that passes, we run the risk of ruining our code with spaces.. ;-)
comment