anchor.diff:  
   At startup, if `-n` is not specified, Kakoune will try to source the file
   `../share/kak/kakrc` relative to the kak binary. This kak file will then try
  -to source any files in `$XDG_CONFIG_HOME/kak/autoload` (with `$XDG_CONFIG_HOME`
  -defaulting to `$HOME/.config`), and finally `$XDG_CONFIG_HOME/kak/kakrc`.
  -
  -The common pattern is to add links to `$XDG_CONFIG_HOME/kak/autoload` to the
  -scripts in `$PREFIX/share/kak/rc` that the user wants sourced at kak launch.
  +to recursively source any files in `$XDG_CONFIG_HOME/kak/autoload` (with
  +`$XDG_CONFIG_HOME` defaulting to `$HOME/.config`, and falling back to
  +`../share/kak/autoload/` if that autoload directory does not exists),
  +and finally `$XDG_CONFIG_HOME/kak/kakrc`.
  +
  +That leads to the following behaviour: by default, with no user autoload
  +directory, the system wide autoload directory is used, once the user wants
  +control on autoloading, they can create an autoload directory and eventually
  +symlink individual scripts, or the whole system wide autoload directory. They
  +can as well add any new scripts not provided with Kakoune.
   
   Basic Interaction
   -----------------
  
positive.code: 
   * `<c-r>`: insert contents of the register given by next key
   * `<c-v>`: insert next keystroke directly into the buffer,
      without interpretting it.
  
   * `<c-u>`: commit changes up to now as a single undo group.
  
  
negative.code: ~~~~~~~~~~~
  
  When entering insert mode, keys are now directly inserted before each selections
  cursor. Some additional keys are recognised in insert mode:
  
   * `<esc>`: leave insert mode
   * `<backspace>`: delete characters before cursors
  