mercurial/helptext/extensions.txt

util: implement `writelines()` on atomictempfile

With typehints on the vfs objects, pytype will flag this:

    FAILED: /mnt/c/Users/Matt/hg/.pytype/pyi/mercurial/patch.pyi
    /usr/bin/python3.8 -m pytype.single
        --imports_info /mnt/c/Users/Matt/hg/.pytype/imports/mercurial.patch.imports
        --module-name mercurial.patch -V 3.7
        -o /mnt/c/Users/Matt/hg/.pytype/pyi/mercurial/patch.pyi
        --analyze-annotated --nofail --quick
        /mnt/c/Users/Matt/hg/mercurial/patch.py
    File "/mnt/c/Users/Matt/hg/mercurial/patch.py", line 535, in writerej:
        No attribute 'writelines' on mercurial.util.atomictempfile [attribute-error]
      In Union[
          mercurial.util.atomictempfile,
          mercurial.vfs.checkambigatclosing,
          mercurial.vfs.delayclosedfile,
          mercurial.windows.fdproxy,
          mercurial.windows.mixedfilemodewrapper
      ]

It's not a real problem there (atomictempfile is only created by passing
different args), but it's reasonable for this to implement the function and
behave like a normal file.  There are other functions missing that can be added
if/when needed.

Mercurial has the ability to add new features through the use of
extensions. Extensions may add new commands, add options to
existing commands, change the default behavior of commands, or
implement hooks.

To enable the "foo" extension, either shipped with Mercurial or in the
Python search path, create an entry for it in your configuration file,
like this::

  [extensions]
  foo =

You may also specify the full path to an extension::

  [extensions]
  myfeature = ~/.hgext/myfeature.py

See :hg:`help config` for more information on configuration files.

Extensions are not loaded by default for a variety of reasons:
they can increase startup overhead; they may be meant for advanced
usage only; they may provide potentially dangerous abilities (such
as letting you destroy or modify history); they might not be ready
for prime time; or they may alter some usual behaviors of stock
Mercurial. It is thus up to the user to activate extensions as
needed.

To explicitly disable an extension enabled in a configuration file of
broader scope, prepend its path with !::

  [extensions]
  # disabling extension bar residing in /path/to/extension/bar.py
  bar = !/path/to/extension/bar.py
  # ditto, but no path was supplied for extension baz
  baz = !