title: Is this Clojure code indented properly?
body: <p><a href="http://pastebin.com/d2294a374" rel="nofollow noreferrer">http://pastebin.com/d2294a374</a></p>
  
  <p>I've posted code indented in 2 different way in there. I get confused here because I am not sure what to do when a function has multiple arguments. Should each argument be on a different line or the same? furthermore, when we have something like (def xyz (fn abc [a1 a2] ... does (fn abc ... go in a different line?</p>
  
  <p><strong>I am reading the following from <a href="http://mumble.net/~campbell/scheme/style.txt" rel="nofollow noreferrer">http://mumble.net/~campbell/scheme/style.txt</a>, but it does not seem to make much sense to me.</strong> </p>
  
  <p>** Indentation and Alignment</p>
  
  <p>The operator of any form, i.e. the first subform following the opening
  round bracket, determines the rules for indenting or aligning the
  remaining forms.  Many names in this position indicate special
  alignment or indentation rules; these are special operators, macros, or
  procedures that have certain parameter structures.</p>
  
  <p>If the first subform is a non-special name, however, then if the second
  subform is on the same line, align the starting column of all following
  subforms with that of the second subform.  If the second subform is on
  the following line, align its starting column with that of the first
  subform, and do the same for all remaining subforms.</p>
  
  <p>In general, Emacs will indent Lisp code correctly.  Run `C-M-q'
  (indent-sexp) on any code to ensure that it is indented correctly, and
  configure Emacs so that any non-standard forms are indented
  appropriately.</p>
  
  <p>Unacceptable:</p>
  
  <pre><code>(+ (sqrt -1)
    (* x y)
    (+ p q))
  
  (+
     (sqrt -1)
     (* x y)
     (+ p q))
  </code></pre>
  
  <p>Acceptable:</p>
  
  <pre><code>(+ (sqrt -1)
     (* x y)
     (+ p q))
  
  (+
   (sqrt -1)
   (* x y)
   (+ p q))
  </code></pre>
  
  <p>Rationale:  The columnar alignment allows the reader to follow the
    operands of any operation straightforwardly, simply by scanning
    downward or upward to match a common column.  Indentation dictates
    structure; confusing indentation is a burden on the reader who wishes
    to derive structure without matching parentheses manually.</p>