[ANN] pyclewn release 2.1

Pyclewn 2.1 has been released at http://pyclewn.sourceforge.net/
Pyclewn is a Vim front-end to the gdb and pdb debuggers.

Version 2.1 brings full gdb completion and a better handling of Vim windows.
See below for the full details.

Xavier


===============
New features
^^^^^^^^^^^^

* Full gdb completion is now available on Vim command line. See
``:help gdb-completion``.

* The console and the Pyclewn buffers are loaded in windows of a dedicated tab
page when the ``--window`` option is set to ``usetab``. See
``help pyclewn-usetab``.

* The new command ``Cexitclewn`` closes the debugging session and removes the
Pyclewn buffers and their windows (issue #20).

* Two new key mappings are available in the breakpoints window. Use ``+`` to
toggle the breakpoint state between enable/disable, and use ``<C-K>`` to
delete the breakpoint.

* The new vim.ping() function may be used to check whether an existing Python
process may be attached to.

Changes
^^^^^^^

* Many improvements to the handling of the Pyclewn windows (issue #17).

* No windows are created when the ``--window`` option is set to ``none``.

Bug fixes
^^^^^^^^^

* Issue #6: Fix the crash in Pyclewn versions 2.0 and 2.0.1 when trying to
attach to a remote gdb.

* Issue #12: Prevent Pyclewn from running with an obsolete version of its Vim
run time files.

* Issue #13: Fix the error messages after ``:Pyclewn pdb`` failure.

* Issue #14: tmux can be used now with the ``terminal`` option, e.g.
``--terminal=tmux,split-window``.

* Issue #15: The clewn buffers are now emptied after the ``Cquit`` command.

* Issue #18: Create the windows layout upon starting Pyclewn. The windows
layout is still created upon the first command instead, when Pyclewn is
started with ``python -m clewn --window=usetab``.

* Issue #19: Vim signs are placed now in the window of a buffer loaded before
the debugging session instead of using the current window.

* Issue #22: Autoscroll the console when the ``--window`` option is set to
``none``.

* Issue #21: A gdb error message is printed now when the ``Cdbgvar`` command
fails.
===============

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.