anchor.diff:  
   === Is there going to be a Windows port of Kakoune ?
   
  -As many features provided by UNIX systems would be missing, or albeit much
  -less efficient, on a Windows system, the incentive to porting the project
  -to this operating system is low.
  +As many features provided by UNIX systems are missing or less efficient on
  +a Windows system, the incentive to porting the project to this operating
  +system is low.
   
   Moreover, you can achieve pretty decent performance by using Kakoune on
   Cygwin (which is officially supported).
  
positive.code: As a fairly compliant follower of the UNIX philosophy, Kakoune does not
  try to implement features that are best handled by separate, dedicated
  tools. Window splitting in terminals is a prime example of that
  concept, whereby the editor provides commands to interact with several
  terminal multiplexers (e.g. `tmux`), as opposed to emulating their
  functionalities.
  
  
negative.code: The `:exec` and `:eval` commands can apply changes to a comma-separated
  list of buffers, passed as argument to the `-buffer` flag.
  
  In order to let the editor figure out which buffers are open, the special
  value `*` is accepted as a wildcard. For example, in order to reload all
  open buffers:
  
  ----
  :eval -buffer * e!
  