jyapayne/vimspector
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #272 from ayberkydn/patch-1

Browse source 
Update README.md
This commit is contained in:
mergify[bot] 2020-10-01 21:30:12 +00:00 • committed by GitHub
commit f6726de058
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -1274,7 +1274,7 @@ It allows you to debug scripts running inside chrome from within Vim.
## Java ## Java
Vimsepctor works well with the [java debug server][java-debug-server], which Vimspector works well with the [java debug server][java-debug-server], which
runs as a jdt.ls (Java Language Server) plugin, rather than a standalone runs as a jdt.ls (Java Language Server) plugin, rather than a standalone
debug adapter. debug adapter.
@ -1669,7 +1669,7 @@ hi link jsonComment Comment
7. What is the difference between a `gadget` and an `adapter`? A gadget is 7. What is the difference between a `gadget` and an `adapter`? A gadget is
somethin you install with `:VimspectorInstall` or `install_gadget.py`, an somethin you install with `:VimspectorInstall` or `install_gadget.py`, an
`adapter` is something that Vimspector talks to (actually it's the Vimsepctor `adapter` is something that Vimspector talks to (actually it's the Vimspector
config describing that thing). These are _usually_ one-to-one, config describing that thing). These are _usually_ one-to-one,
but in theory a single gadget can supply multiple `adapter` configs. but in theory a single gadget can supply multiple `adapter` configs.
Typically this happens when a `gadget` supplies different `adapter` config Typically this happens when a `gadget` supplies different `adapter` config
@ -1701,7 +1701,7 @@ A message from the author about the motivation for this plugin:
> into the debugger, it would be faster and more enjoyable that just cerebral > into the debugger, it would be faster and more enjoyable that just cerebral
> code comprehension. > code comprehension.
> >
> I created Vimsepctor because I find changing tools frustrating. `gdb` for c++, > I created Vimspector because I find changing tools frustrating. `gdb` for c++,
> `pdb` for python, etc. Each has its own syntax. Each its own lexicon. Each its > `pdb` for python, etc. Each has its own syntax. Each its own lexicon. Each its
> own foibles. > own foibles.
> >