Open rileyrg opened 4 years ago
Can you provide call stack? Are you sure this is not the issue you already reported in dap-mode?
I havent done a debugging session in this case: the other seemed to be related to the output window not being visible during an actual debugging session, I also reverted to melpa dap btw. this seems to be a recent thing. stack :-
Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
#<subr select-window>(nil norecord)
lsp-ui--hide-doc-frame-on-window-change(#<subr select-window> nil norecord)
apply(lsp-ui--hide-doc-frame-on-window-change #<subr select-window> (nil norecord))
select-window(nil norecord)
company-box--change-line()
company-box--next-line()
funcall-interactively(company-box--next-line)
call-interactively(company-box--next-line nil nil)
command-execute(company-box--next-line)
Bringing up company complete dialog:-
Try to cursor down and get:-
Note that
is nil and hasnt been on in this session,
lsp mode,lsp managed, lsp ui, dap, dap ui all on btw,