vim/vim-vebugger
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fixed a few typos, made one rewording recommendation.

Browse Source
This commit is contained in:
Jim Bridgewater 2019-01-13 11:26:12 -06:00
parent 4fac68fb95
commit 119b814671
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -7,7 +7,7 @@ wasn't happy with the other debugger plugins I found. Vebugger currently
supports:
* Tracking the currently executed command in the source code
* Debugger flow commands - step-in, set-over, set-out and continue
* Debugger flow commands - step-in, step-over, step-out and continue
* Breakpoints management
* Evaluating expressions in the current executed scope
* Messing with the program's state (changing values, calling functions)
@ -29,10 +29,10 @@ that add such implementations as long as they use Vim's |license|.
Vebugger is built under the following assumptions:
* While command line debuggers share enough in common to make the creation
of such a framework as Vebugger possible, the differences between them are
of a framework such as Vebugger possible, the differences between them are
too great to be expressed with regular expression. To support them all at
least some code has to be written.
* Unlike IDE users, Vim users tend to understand the tools the operate behind
* Unlike IDE users, Vim users tend to understand the tools that operate behind
the scenes. While Vebugger automates the common features, it allows you to
"open the hood" and interact with the debugger's shell directly so you could
utilize the full power of your debugger.