Ivan Yonchovski
Ivan Yonchovski
> By this you mean support for debugging spawned Node processes? @eeshugerman I am not that familiar with nodejs but I think that we kind of support now this usecase....
@eeshugerman good. I am looking for feedback for: * session management works fine(e. g. cleanup after child session exits is done) * UI makes sense - do we need to...
FWIW I added a method `dap-js-setup` and how you can install it using M-x dap-js-setup Here it is also sample configuration that I am using for testing: ``` json {...
It should be good after https://github.com/emacs-lsp/dap-mode/pull/700 We should migrate other packages as well (whenever possible).
There is this in attach template: https://github.com/scalameta/metals-vscode/blob/main/packages/metals-vscode/package.json#L944 And the crash happens here: https://github.com/scalameta/metals/blob/b1532e787797355855371a619302327a078da34b/metals/src/main/scala/scala/meta/internal/metals/debug/SourcePathAdapter.scala#L66 I don't know that that is in scala context, but maybe you know.
AFAICS it says in their docs/samples. ``` // name of the module that is being debugging ```
@mihaipop11 both a built on top of lsp
pushed a fix about the issue related to marksman
> @Xalares @yyoncho still an issue for me for whatever reason can you describe what you are seeing when doing M-x lsp-start-plain and installing the server...
There was a recent fix in lsp-credo. Can you test it out?