Blaž Hrastnik

There's nothing wrong with it, but it adds extra code that we have to maintain forever or until deprecation. If you're using `export GO111MODULE=off` you likely want to apply it...

Is this something VSCode supports? To me it still seems like you'd want DEFMT_LOG set automatically via dotenv when you enter the directory.

Themes: It's going to be a pain to maintain the list and the previews. You can already just tab through the list of themes and see the theme previewed live...

Yes, given that LSP is built in, DAP will be built in too. Note that both GDB and LLDB don't support DAP and implement a custom protocol, though LLDB seems...

We should be able to reuse most of the LSP low-level code, it's the same protocol. Just the high level requests are different.

Interesting, so DAP doesn't run over stdin/stdout? I think the way forward will be to define a transport and all the request/response protocol types in `helix-dap`, then construct a session...

Looks like it can be both ways. Either it's an executable we're responsible with starting and then communicating via stdio, or it's a server (that can also be externally running,...

From what I understand the implementation in neovim is inherently different than the tree sitter rust crate or other helix so even if we have compatible scopes it's not guaranteed...

See https://github.com/helix-editor/helix/pull/1843 and https://github.com/vorner/signal-hook/issues/132 we were hoping to fix this in signal-hook instead

Maybe you could just upstream the fix? @pickfire closed the issue since he couldn't track it down.