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

Fix incorrect naming of .viminspector.json

Browse source 
I got tripped up getting started because the documentation incorrectly uses `vimspector.json` and I was getting an error about no debug configurations found.
This commit is contained in:
Ethan Setnik 2020-05-15 11:32:09 -04:00 • committed by GitHub
commit 62c1fe79da
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -578,7 +578,7 @@ let g:vimspector_enable_mappings = 'HUMAN'
## Launch and attach by PID:
* Create `vimspector.json`. See [below](#supported-languages).
* Create `.vimspector.json`. See [below](#supported-languages).
* `:call vimspector#Launch()` and select a configuration.
![debug session](https://puremourning.github.io/vimspector-web/img/vimspector-overview.png)
@ -1183,7 +1183,7 @@ sign define vimspectorPC text=🔶 texthl=SpellBad
3. How do I stop it starting a new Terminal.app on macOS? See [this
comment](https://github.com/puremourning/vimspector/issues/90#issuecomment-577857322)
4. Can I specify answers to the annoying questions about exception breakpoints
in my `vimspector.json` ? Yes, see [here][vimspector-ref-exception].
in my `.vimspector.json` ? Yes, see [here][vimspector-ref-exception].
5. Do I have to specify the file to execute in `.vimspector.json`, or could it be the current vim file?
You don't need to. You can specify $file for the current active file. See [here][vimspector-ref-var] for complete list of replacements in the configuration file.