Purpose of this package?

[lloiser]

I'm currently developing the go-debug atom package which is a debugger interface for go (using delve).

Is this going to be a general purpose package to create such debuggers (standard interface and api, like in visual code)? If so what's the purpose of the "old" package atom-community/debugger then?

And is there any way one could help building such a package?

[thomasjo]

I'm not 100% sure, but I believe this is meant to co-exist with captain-hook.

/cc @joefitzgerald

[joefitzgerald]

@lloiser firstly, thank you for working on that package - this is awesome and precisely why I split out the logic for go-config from go-plus into a standalone package!!! When you feel like go-debug is mature, I would like to bundle it into go-plus, if you're open (go-plus is basically a package installer now).

Second, as @thomasjo describes, yes, debug is intended to work in conjunction with captain-hook. It will allow for a provider-based system to work in a similar way to nuclide's debugging packages. In essence, the language-specific providers should not need to worry about UI, or determination of which package should be used to debug what file or folder.

You should join us on Slack:

[lloiser]

Great to hear this 😁 It seems to work fine although I'm pretty sure that there is still room for improvement here and there or bugs which I didn't found until now. Test it yourself and if it looks fine to you feel free to add it to go-plus.

So this will replace my ui implementation sooner or later - great, less code to maintain then 😄

[joefitzgerald]

You should create an animated gif and add it to the readme. Once we have that we should post it to reddit.

[fbender]

Any roadmap for this package? Seems like nothing happened in the last months 😕

[lloiser]

I'm currently reworking my go-debug package to separate the view and the actual debugger into separate projects/packages. Are you interested in moving my code over to here?

[joefitzgerald]

@lloiser, yes!

[ghost]

Can there at least be some expanded README description until the illustration is ready? I've just stumbled across this, and I still can't tell what it is supposed to be (debugger for a certain language? universal debugger for many languages? base plugin to be used by developers of languages to implement their actual debugger?...) so having a better description than the current super vague one-liner would be hugely appreciated.

[paddotk]

From what I understand, this package simply allows you to install other debug packages, with which you can debug inside Atom itself.
However, what isn't clear to me is how to use this. There are no settings for this package, there is no debug pane nor can I find a terminal pane where you can input the install command for debug packages. In that respect, I second the notion of adding some explanation to the readme.