Matěj Cepl wrote:
> On 2017-09-09, 20:20 GMT, Bram Moolenaar wrote:
> > Patch 8.0.1085
> > Problem: The terminal debugger can't set breakpoints.
> > Solution: Add :Break and :Delete commands. Also commands for stepping
> > through code.
> > Files: runtime/pack/dist/opt/termdebug/plugin/termdebug.vim,
> > runtime/doc/terminal.txt
>
> Is there some way how to make termdebug working with other
> debugger (I would be interested in pdb, of course)?
> That would be really awesome! The only thing which makes me
> thing about VSCode or PyCharm is missing debugger in vim (and
> all plugins I found are more or less broken).
The plugin depends on the GDB/MI interface. If another debugger
supports that it should work, just set g:termdebugger to the executable
name. If it uses something else for remote control, it's going to be
more work. If there is no remote control it's going to be difficult.
Esp. to have the debugger tell Vim where it stopped in the source code.
--
Nobody will ever need more than 640 kB RAM.
-- Bill Gates, 1983
Windows 98 requires 16 MB RAM.
-- Bill Gates, 1999
Logical conclusion: Nobody will ever need Windows 98.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
