Move the thread handling into the stack frame handling
This shows stack traces as children of a thread, removing one of the UI splits. However, we still have the somewhat awkward concepts of "current" thread and "current" stack frame. These are messy and incredibly fiddly. And in any case, probably wrong _most_ of the time.
This commit is contained in:
parent
0a19048311
commit
5ed9a06ed5
3 changed files with 175 additions and 116 deletions
|
|
@ -72,7 +72,7 @@ function! vimspector#DeleteWatch() abort
|
|||
endfunction
|
||||
|
||||
function! vimspector#GoToFrame() abort
|
||||
py3 _vimspector_session.GoToFrame()
|
||||
py3 _vimspector_session.ExpandFrameOrThread()
|
||||
endfunction
|
||||
|
||||
function! vimspector#AddWatch( expr ) abort
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue