Tag urself on lisp indentation style:

;; I'm afraid of passing 80 characters
(proc1
arg1 arg2
(proc2
arg1 arg2
(cond
[(foo)
(bar 'baz 'quux)]
[else
(beep boop 'bop)])))

;; Everyone has wide monitors these days anyway right?????
(proc1 arg1 arg2
(proc2 arg1 arg2 (cond [(foo) (bar 'baz 'quux)]
[else (beep boop 'bop)])))

@cwebber 80 chars is best when you want to have 2 or 3 files open at once.

@phoe I agree, which is why I tend to be very "conservative" about width

@cwebber @phoe It seems odd that we still worry about line widths when we're editing structured data like code. Why should the formatting even make it into the file?

@freakazoid @phoe @cwebber jup.
I don't get why we even commit the formatting.

Just let everyone run their own go-like formatter.

Whatever the build server doesn't need does not belong into the repo

@saxnot @freakazoid @cwebber Indentation tends to convey meaning sometimes. Also, it's trivial to treat source as text and not as binary data. You can't trivially edit binary data with vim or emacs.

@phoe @freakazoid @cwebber no i was thinking more of a commit hook that removed all intendation and maybe newlines too.
The editor shall be responsible for displaying it how the user wants (whatever the editor is. This can be done trivially in vim and emacs - the hard part is deciding what format you want your code in)