anchor.diff:  = FAQ
   
  -== How to pronounce the name of the project and what does it mean ?
  +== The project
  +
  +=== How to pronounce the name of the project and what does it mean ?
   
   The name of the project is pronounced "Kak-oon", and is a word taken from a
   New Caledonian dialect based on French. It means a hard blow, usually a punch,
   but generally refers to a blow into which all of one's strength went.
   
  -== Is there going to be a Windows port of Kakoune ?
  +=== Is there going to be a Windows port of Kakoune ?
   
   As many features provided by UNIX systems would be missing, or if anything
   much less efficient on a Windows system, the incentive to porting the
  
positive.code: 
  In most distributions, `/bin/sh` will end up being used.
  
  == Can I disable auto-indentation completely ?
  
  All the indentation hooks are conventionally named `<lang>-indent`, which
  allows us to use the `disabled_hooks` variable to disable indentation
  globally with the following command: `set global disabled_hooks '.+-indent'`
  
  == How to enable syntax highlighting ?
  
  The mimetype of the files opened in new buffers is detected using the
  `file` command, and syntax highlighting enabled automatically when
  possible.
  
  == My file seems to be highlighted with the wrong colors, I thought syntax highlighting was detected automatically ?
  
  The `file` utility has several shortcomings, such as detecting the
  wrong mimetype for a file containing data with different syntax, e.g.
  a Python script containing hardcoded HTML templates detected as an HTML
  file.
  
  Kakoune does its best at detecting file types (using known extensions
  for a given format for instance), but not much can be done about those
  ambiguous cases. You might consider writing a custom `$HOME/.magic` file
  if needed.
  
  == Can I disable syntax highlighting completely ?
  
  Similarly to the indentation hooks, the name format followed by the
  highlighting hooks is `<lang>-highlight`. You can thus disable syntax
  highlighting using the following command: `set global disabled_hooks
  '.+-highlight'`
  
  == 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
  
negative.code: use the `[^\n]+` pattern, which is arguably a good compromise when
  balanced against the ability to select data over several lines.
  
  === Why does `a` extend the current selection, but `i` leaves it untouched ?
  
  Selections are ranges of characters whose delimiters are an "anchor" and
  a "cursor", and inserting characters is always done before the cursor in
  