CODEWITHSUNDEEP
clojureindentation
Vagif Verdi
Vagif Verdi

Reputation: 4906

Clojure indentation problems in team with different IDEs

I am using emacs + slime for clojure development. Recently we got a new team member and he does not like emacs, so he installed intellij with la clojure plugin.

Both emacs and intellij allow to automatically re-indent big blocks of code, entire functions and even modules.

This leads to a very annoying problem. If he makes a small change (few lines) and then reindents entire file, then obviously recording it into dvcs (we use darcs) will produce big patch with hundreds rows changed. That makes code review impossible. How do i know which 3 out of hundreds committed lines really changed ?

So now we have collaboration problem. I wonder if there are other clojure teams who use different IDEs. How do you reconcile these problems ?

The options i see are:

  1. Enforce the use of one IDE (emacs). This will solve the problem, but i do not like such an authoritative approach.

  2. Somehow setup both environments to indent identically (not sure if its possible)

  3. Agree to always indent in one IDE. This is cumbersome and prone to errors.

Upvotes: 3

Views: 307

Answers (4)

Rachel K. Westmacott
Rachel K. Westmacott

Reputation: 2301

If you can generate a diff from the patch that ignores whitespace changes then your specific problem would go away. +1 for a consistent coding style within the team though.

Upvotes: 0

Nathan
Nathan

Reputation: 115

If someone chooses to use a different IDE, it's their responsibility to configure it to be a good member of the team. If they don't know how to do so, they probably don't have much of a reason to use it over any other IDE.

However, the configuration options for indentation are located in: Preferences > Code Style

Upvotes: 3

BillRobertson42
BillRobertson42

Reputation: 12883

You could try asking him to respect the rest of the team and not automatically reformat everybody's code.

You might also write an external program to do the indenting, and then hook that into your source code system as a pre-commit step. That way it wouldn't matter what editor was used, it would become consistent. I suppose this is a variation on option #2.

Good luck.

Upvotes: 9

Yuriy Zubarev
Yuriy Zubarev

Reputation: 2871

Number 2): One team, one coding standard.

Upvotes: 2

Related Questions