Doctr tests

.appveyor.yml

@@ -1,4 +1,4 @@
-version: 0.7.6.{build}
+version: 0.7.7.{build}
 os: Windows Server 2012 R2
 environment:
 

CHANGELOG.rst

@@ -4,6 +4,40 @@ Xonsh Change Log
 
 .. current developments
 
+v0.7.7
+====================
+
+**Added:**
+
+* A xontrib which adds support for autojump to xonsh
+* Added new env-var ``XONSH_HISTORY_MATCH_ANYWHERE``. If set to ``True`` then
+  up-arrow history matching will match existing history entries with the search
+  term located anywhere, not just at the beginning of the line. Default value is
+  ``False``
+
+
+**Changed:**
+
+* Improved iteration over virtual environments in ``Vox.__iter__``
+
+
+**Fixed:**
+
+* Fix for ``Enter`` not returning from Control-R search buffer
+* Fixed automatic wrapping of many subprocesses that spanned multiple lines via
+  line continuation characters with logical operators separating the commands.
+  For example, the following now works:
+
+  .. code-block:: sh
+
+        echo 'a' \
+        and echo 'b'
+* Environment swapping would not properly reraise errors due to weird
+  Python name binding issue.
+
+
+
+
 v0.7.6
 ====================
 
@@ -83,7 +117,7 @@ v0.7.4
 
 **Fixed:**
 
-- Fixed a bug with converting new PTK2 colors names to old names when using PTK1 or Jupyter 
+* Fixed a bug with converting new PTK2 colors names to old names when using PTK1 or Jupyter
     as the shell type.
 * ``CommandsCache.locate_binary()`` will now properly return None when
   ``ignore_alias=False`` and the command is only a functional alias,
@@ -103,11 +137,11 @@ v0.7.3
 
 * Add the ``PROMPT_TOOLKIT_COLOR_DEPTH`` environment to xonsh default environment.
   Possible values are ``DEPTH_1_BIT``/``MONOCHROME``,
-  ``DEPTH_4_BIT``/``ANSI_COLORS_ONLY``, ``DEPTH_8_BIT``/``DEFAULT``, or ``DEPTH_24_BIT``/``TRUE_COLOR``. 
+  ``DEPTH_4_BIT``/``ANSI_COLORS_ONLY``, ``DEPTH_8_BIT``/``DEFAULT``, or ``DEPTH_24_BIT``/``TRUE_COLOR``.
   Note: not all terminals support all color depths.
 * New way to fix unreadable default terminal colors on Windows 10. Windows 10
   now supports true color in the terminal, so if prompt toolkit 2 is
-  installed Xonsh will use a style with hard coded colors instead of the 
+  installed Xonsh will use a style with hard coded colors instead of the
   default terminal colors. This will give the same color experience as on linux an mac.
   The behaviour can be disabled with ``$INTENSIFY_COLORS_ON_WIN``
   environment variable.
@@ -116,9 +150,9 @@ v0.7.3
 
 **Changed:**
 
-* All ansicolor names used in styles have ben updated to the color names used by prompt_toolkit 2. 
-  The new names are are much easier to understand 
-  (e.g. ``ansicyan``/``ansibrightcyan`` vs. the old ``#ansiteal``/``#ansiturquoise``). The names are automatically 
+* All ansicolor names used in styles have ben updated to the color names used by prompt_toolkit 2.
+  The new names are are much easier to understand
+  (e.g. ``ansicyan``/``ansibrightcyan`` vs. the old ``#ansiteal``/``#ansiturquoise``). The names are automatically
   translated back when using prompt_toolkit 1.