anchor.diff: -Counterclockwise User Guide
  -===========================
  += Counterclockwise User Guide
   Laurent Petit <laurent.petit@gmail.com>
  -:toc:
  -:toclevels: 0
  +:toc: left
  +:toc-title: User Guide
  +:toclevels: 2
   :sectlinks:
   :sectanchors:
   :highlight: highlightjs
   :experimental:
   :icons: font
   
  -Counterclockwise User Documentation
  -
  -= What is Counterclockwise ?
  +== What is Counterclockwise ?
   
   Counterclockwise is best described as an Integrated Development Environment for the http://www.clojure.org[Clojure] language. +
  -It is an extension of the popular http://www.eclipse.org[Eclipse IDE].
  +It is an extension of the popular http://www.eclipse.org/ide[Eclipse IDE].
   
   Goals of Counterclockwise:
   
   - be as easy as possible for Clojure beginners
  -- integrate nicely into the Eclipse IDE
  +- integrate nicely into the http://www.eclipse.org/ide[Eclipse IDE]
   
   Counterclockwise bundles everything for hacking Clojure Code:
   
  
positive.code: NOTE: It is possible to configure which files should be automatically loaded on project java process startup.
  
  
  == Namespace Browser View
  
  The `Namespace Browser View` displays all symbols of all namespaces of the active REPL.footnote:[active-repl,The active REPL is the last REPL you interacted with]. +
  It allows you to jump to the definition of symbols in the relevant files (including inside jars): just double-click on the symbol name in the `Namespace Browser View`.
  
negative.code: ====
  
  // TODO: see in what respect the following section still holds. Should we remove the section from the doc? Plan to re-add the feature in a future release?
  ==== Errors reporting
  
  _to be confirmed_
  
  In conjunction with auto-compile functionality, compilation problems are reported as problem markers : you see a summary of the problems in the problems view, you see the files that have problems in the package explorer, you see the problems at the correct line in the corresponding editor, you can jump to the editor at the correct line by double clicking on the problem in the problems view.
  
  ==== Keyboard Shortcuts
  
  The Editor is really keyboard commands friendly. 
  See the list of Keyboard Bindings: link:keyboard-shortcuts.html[List of Keyboard Shortcuts]
  
  ==== Interaction with a launched REPL
  
  You'll find the commands for interacting with a REPL from an Editor in the link:keyboard-shortcuts.html[Keyboard Shortcuts] page
  
  == Auto-build feature
  
  // TODO the sentence is badly written
  Once you have started a REPL for your project, and when the menu:Project[Build automatically] menu entry is selected, Eclipse will use a background connection to this REPL to automatically compile and evaluate the files you edit.
  
  == Package your work
  
  // TODO consider packaging Fat Jar with the Standalone Package
  // TODO change to explain how to do this with Leiningen
  
  === Distribute as a jar
  
  // TODO find the right menu labels
  - Use the Eclipse menu:File[Export as Jar] Wizard
  
  === Create a "fat" executable jar with all dependencies packaged into
  
  There's a community contributed Eclipse Plugin for this task, called `Fat Jar`.
  
  