Newcomer help wanted in the Haskell Debugger
Hi all,
In preparation for ZuriHac, I’d love to have some help on a few haskell-debugger issues.
These issues are especially relevant here because they will help more people use the debugger, and I do hope to onboard more people to using it in Zurich!
(Hopefully, some of you will even want to hack on these or other Haskell debugger features/bugs there).
If you want to work on any of these, do reply in the issue thread, to make sure two people don’t end up doing overlapping work:
Emacs Support: we’ve got instructions and tested the debugger with VSCode, nvim-dap, and vimspector; however, we need an Emacs user to take the lead in setting up
haskell-debuggerwith a DAP plugin, testing it, and writing down how to do it for other users (@simonpj is on Emacs, and I have yet to get him to try the debugger).Installing with stack fails: Stack users! Please help make the debugger installable using stack. I don’t know what the required details are, so do come help.
Ship via GHCup: GHCup now supports 3rd party tools, and @hasufell suggested we start distributing
haskell-debuggerthrough GHCup in this way. Installation is currently a bit subtle (because of the flags we must pass tocabal-install), so providing ready to use binaries in GHCup would be excellent.New Debugger Logo: We would love to have a cool logo for the debugger VSCode extension! It should ideally be recognizable when seen at a “small” scale on the VSCode marketplace.
Discussion in the ATmosphere