anchor.diff:  
   In most distributions, `/bin/sh` will end up being used.
   
  -=== Why does a dot `.` in a regex select newline characters ?
  +=== Why does a dot `.` in a regex select newline characters?
   
   Data in buffers is a stream of characters, and newlines do not receive special
   treatment compared to other characters, with regards to regex matching. In
  
positive.code: file you selected to the current Kakoune session (e.g. `echo "eval -client
  $kak_client edit /path/to/file" | kak -p $kak_session`).
  
  === How do I automatically indent code, as Vim does with `=` ?
  
  As `Kakoune` doesn't parse the contents of the buffers, there is no builtin
  equivalent for this Vim feature. Use a formatter/prettifier dedicated to
  
negative.code: The resulting binary should produce a stacktrace that you can, afterwards,
  post in an issue in unmangled form (c.f. `c++filt`).
  
  === How can I explore the filesystem the way Vim's NerdTree does?
  
  The builtin file completion engine used when opening a file for editing
  (using the `:edit` command and letting the suggestions popup in the menu
  