anchor.diff:  clj -X:my-fn
   ----
   
  -You can supply additional keys, or override values stored in the deps.edn file by passing  pairs of key-path and value. The key-path should either be a single key or a vector of keys to refer to a nested key (as with `assoc-in`). Each key-path will be used to `assoc-in` to the original `:args` map, overriding the value there.
  +You can supply additional keys, or override values stored in the deps.edn file by passing pairs of key-path and value. The key-path should either be a single key or a vector of keys to refer to a nested key (as with `assoc-in`). Each key-path will be used to `assoc-in` to the original `:args` map, overriding the value there.
  +
  +[source]
  +----
  +# Top key override
  +clj -X:my-fn :config 789
  +
  +# Nested key override
  +clj -X:my-fn '[:my :data]' 789
  +----
   
   Key/value pairs are read as edn strings, please see the tips about quoting below.
   
  
positive.code: 
  === Aliases
  
  Aliases give a name to a data structure that can be used either by the Clojure tool itself or other consumers of deps.edn. They are defined in the `:aliases` section of the config file. These Clojure tool flags use the following well-known alias keys:
  
  * -R - uses these keys when expanding deps during `resolve-deps`:
  ** `:extra-deps` - a deps map from lib to coordinate of deps to add to the deps
  ** `:override-deps` - a deps map from lib to coordinate of override versions to use
  ** `:default-deps` - a deps map from lib to coordinate of versions to use if none is found
  ** If multiple alias maps with these keys are activated, all of them are merge-with merged
  * -C - uses these keys when creating the classpath during `make-classpath`:
  ** `:extra-paths` - a collection of string paths to add to `:paths`
  ** `:classpath-overrides` - a map of lib to string path to replace the location of the lib
  ** If multiple maps with these keys are activated, `:extra-paths` concatenate and `:classpath-overrides` merge-with merge
  * -O - uses these keys when constructing the final command JVM options:
  ** `:jvm-opts` - a collection of string JVM options
  ** If multiple maps with these keys are activated, `:jvm-opts` concatenate
  ** If -J JVM options are also specified on the command line, they are concatenated after the alias options
  * -M - uses these keys when constructing the final command clojure.main arguments:
  ** `:main-opts` - a collection of clojure.main options
  ** If multiple maps with these keys are activated, only the last one will be used
  ** If command line clojure.main arguments are supplied on the command line, they are concatenated after the last main alias map
  * -A - activates all of the keys above, also these keys are only supported with -A:
  ** `:deps` - a deps map from lib to coordinate of deps to REPLACE the project `:deps`
  ** `:paths` a collection of string paths to REPLACE project `:paths`
  
  So given a deps.edn like:
  
  
negative.code: 
  After installation, deps.edn configuration files can be found in (up to) three locations:
  
  - root installation directory - created only at install time
  - user config directory (often ~/.clojure) - modify to change cross-project (or no-project) defaults
  - local project directory - per-project settings
  
  The `deps.edn` files in each of these locations (if they exist) are merged to form one combined dependency configuration. The merge is done in the order above root/user/project, last one wins. The operation is essentially `merge-with merge`, except for the `:paths` key, where only the last one found is used (they are not combined).
  
  You can use the  `-Sverbose` option to see all of the actual directory locations.
  
  