vimspector/support/test
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Ben Jackson 2710ee2bfa When the start parameter is missing, the behabiour is arbitary
It seems that the behaviour of the start parameter being missing is
server (or perhaps a specific client) dependent. The specification
clearely says that it should be inserted at the column of the original
request, but the servers clearly expect either for that column to be the
beginning of an identifier or for the client to ignore the spec and
request from that position anyway.

Reading the VSCode code, we see that the 'word' before the cursor is
guessed, and if only if BOTH 'start' AND 'length' are supplied, then
they are used to determine where insertion starts, otherwise the current
'word' is used. Unclear what 'word' means in the specific contexts, but
we're relying on iskeyword.
2020-09-04 00:29:39 +01:00
..
chrome Upgrade chrome debugger to 4.12.10 2020-09-03 22:11:57 +01:00
cpp/simple_c_program Windows support for cpptools 2020-06-27 17:28:05 +01:00
csharp Add and document why mono debugger doesn't work 2019-06-23 21:39:27 +01:00
example Add 'example' allowing simple command-line attachment 2020-01-31 16:11:36 +00:00
go/hello_world set GO111MODULE to off and the debug wont fail in go 1.11+ 2020-06-04 16:39:36 +10:00
java/test_project Use the original java test code 2020-07-16 08:04:03 +01:00
node/simple When the start parameter is missing, the behabiour is arbitary 2020-09-04 00:29:39 +01:00
python Add a way to force a str in case #json is really required in a key 2020-08-05 22:24:35 +01:00
rust/vimspector_test Add installer support for CodeLLDB 2020-07-06 11:24:54 +01:00
tcl Update tclpro; add a test 2020-07-08 13:19:14 +01:00
run_test_vim Improve tests 2019-05-16 21:08:18 +01:00