view docs/known-doc-issues.rst @ 4332:9980df8eda98 stable

tests: fix PYTHONPATH manipulation on Windows

Without the semicolon separator and quotes, the variables ends up like this:

    c:\Users\Matt\projects\hg-evolve:c:\Users\Matt\projects\hg-evolve:
    c:\Users\Matt\projects\hg;c:\Users\Matt\projects\hg-evolve\tests;
    c:\Users\Matt\projects\hg\tests

That in turn makes the local evolve code unreachable, and the system installed
code is tested instead.

I'm testing against `uname` instead of a trivial python script printing os.name
because maybe one day tests will run on WSL.

.. Copyright © 2017 Pierre-Yves David <[e-mail]>

==============================================
Known limitations of the current documentation
==============================================

Features not covered by tutorials
=================================

Some of the *newer* features of evolution might not be reflected in the
documentation yet. You can directly check the inline documentation of the
extension itself for fresher details using `hg help -e evolve`.

Known undocumented features are:

 * `hg prev`,
 * `hg next`,
 * `hg next --evolve`,
 * `hg evolve --rev`,
 * `hg evolve --list`,
 * `hg obslog`,
 * `hg split`,
 * `hg metaedit`,
 * `hg touch`,
 * `hg amend --extract`,
 * `hg pdiff`,
 * `hg pstatus`,
 * `hg amend -i`,
 * various topic related elements (in particular `hg stack`),

Unreferenced Documents
======================

There are documents with content not linked in the flow of the main
documentation. Some might be outdated and some are too fresh to be integrated in
the main flow yet.

.. toctree::
   :maxdepth: 1

   evolve-faq
   evolve-good-practice
   obs-terms
   tutorials/topic-tutorial
   tutorials/tutorial