Build and Debug support

[WeetHet]

Check for existing issues

• Completed

Describe the feature

In most of today's code editors there is support for building tasks and debugging/launch support. This gives better reliability on the editor and reduces terminal usage. This is also just so much more comfortable. I think that first LLDB and Python debuggers should be introduced alongside with shell build tasks

If applicable, add mockups / screenshots to help present your vision of the feature

See: VSCode Build/Debug, JetBrains IDE's debug support

[JosephTLyons]

Going to group this together with the code runner issue:

• Code runner #5141

[Kethku]

I looked into vscode's task.json file format and I think we should build support for it. Its general purpose, used frequently today, and handles a lot of corner cases pretty well.

https://code.visualstudio.com/docs/editor/tasks

[WeetHet]

Speaking of that, shouldn't you also implement debug support? It will help a lot

[luolong]

I second this feature request.

An ability to run builds either manually or automatically based on some editor events, execute tests (with feedback on test failures) and run arbitrary shell scripts (or code snippets as mentioned in related "Code runner" issue), would be immensly helpful.

[WeetHet]

I just don't seem to understand why this, essential thing is not even considered by masses (well, we still don't have replace feature, so maybe that says something)

[natsuboy]

I think build, run, and debug are all core features.

[sonereker]

Debugging support for especially Go 👍🏼

[WeetHet]

Maybe we should try to popularise this issue among other people so we would have more support?

[aexvir]

I'll mention my own issue for this, as it's the oldest one and it already has a bunch of 👍🏻
#5307
it was covering mainly debugging through the support of dap servers, so no mention to building, but everyone who's interested on debugging should probably consolidate its reactions to that one

[sheikalthaf]

@JosephTLyons this one is very important feature which is required by default. Please Include this also as part of top ranking issues. So that i get attention from other developers also

[hovsater]

@JosephTLyons this one is very important feature which is required by default. Please Include this also as part of top ranking issues. So that i get attention from other developers also

Top ranking issues are based on number of thumbs up. Currently it’s the top 20 per core-label. This issue will automatically get there when the interest is high enough.

[WeetHet]

@JosephTLyons this one is very important feature which is required by default. Please Include this also as part of top ranking issues. So that i get attention from other developers also

Top ranking issues are based on number of thumbs up. Currently it’s the top 20 per core-label. This issue will automatically get there when the interest is high enough.

I just don't understand how this is considered just an "enhancement" and not a core feature?

[hovsater]

The label "enhancement" is used both for enhancements/features, so don't read too much into it. 🙂 The best way for the community to signal the importance of a given feature right now is by add your 👍 to the issue.

[WeetHet]

The label "enhancement" is used both for enhancements/features, so don't read too much into it. 🙂 The best way for the community to signal the importance of a given feature right now is by add your 👍 to the issue.

You can look at the problem this way, but that means that PHP support is more valuable than custom LSP support, which is obviously wrong, because latter is the superset of the former

[jansol]

Some of us just want a fast & sleek code editor with some navigation helpers, not a fully integrated Developer ®️ Experience ™️

Debugger integration might be a key feature for you but for like half of my current projects it's either not useful to begin with or not feasible to set up in any IDE.

[iamnbutler]

Labels are 100% an organizing mechanic and not a statement of importance or sequencing. Don't read into them too much.

Build & Debug hasn't been built because the team doesn't really use them – When the right combination of people want it, and it makes sense for us to build sequencing-wise compared to other things, it will get built.

@JosephTLyons we might want to consider merging this with #5307 or group them?

[gcdsss]

I'm looking forward to having debug, launch, and task features. Having both VS Code and PyCharm open with multiple projects consumes too much resources and it really slow. 👍

[0xtimsb]

Where can we track progress for this?

[MilanVilov]

This would be quite an important feature for everyone working on larger codebases with good specs coverage.
On the current Rails project we have around ~7500 specs, and we use debugger with RubyMine on daily basis, either to actually find the bug or for better understanding of the domain process.
It is one of the most selling points of RubyMine for Ruby/Rails development and probably the main reason I am paying the licence every year, it speeds up the development.

This was also a core functionality of the VisualStudio while I did .Net development and it still is.
For me the main difference between lightweight code editors and the IDE I use for everyday work is high quality debugger.

It would be awesome if a great tool like Zed would have couple of these grade 1 IDE features integrated as part of the core functionality.

[MilanVilov]

I'm looking forward to having debug, launch, and task features. Having both VS Code and PyCharm open with multiple projects consumes too much resources and it really slow. 👍

I am found myself using Zed + RubyMine couple of times, as I really wanted to migrate to Zed, but lack of debugger is just too big of an issues, so I went back to RubyMine until this is implemented.

[0xtimsb]

Only build task runner is stopping me from switching to Zed.

[majd-asab]

Only build task runner is stopping me from switching to Zed.

same, but I'd also love a debugger

[emil14]

This is the reason why I won't switch from VSCode :-(

[jansol]

Since there's a huge influx of new people: issue popularity is being tracked programmatically based on the 👍 reactions to the OP of each issue. (this would probably deserve a pinned notice at the top of the issue tracker)

"me too" comments do not contribute to the popularity count, they only send out unnecessary notifications to a lot of people.

[Varagos]

A debugger is currently the only thing holding me from using Zed more actively too.

[davidbuzz]

PHP / xdebug / dbgp protocol needs to also be a part of this as its the most-popular language by-far for running websites, and it fully supports being debugged.

[ximidas]

I'm using Zed for Rust development, and interestingly, I find myself rarely needing a debugger for Rust. However, when I'm working with languages like Python, Ruby, JavaScript, and PHP, a debugger becomes indispensable.

[davidbuzz]

If Zed implemented Debug Adapter Protocol aka "DAP" to match what VSCode has ( as requested on this issue and #5307 ) , then it should be possible to debug in Zed just about anything that can already be debugged in VSCode, including C,C++,php,c#,node, python, javascript, perl, haskel, ie all-the-things listed here:
https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/

here's a rust implemention of DAP as well...: https://github.com/sztomi/dap-rs

[jansol]

why rust rarely needing a debugger for Rust?

Serious answer because this gets asked surprisingly often:

Rust's language-level guarantees and generally very insightful compiler error messages mean that it is rare to have to debug something at runtime. When you do, it is often something that is quickly solved by printing the offending statement with dbg!(<problematic statement here>). Also, panics in rust code give you a nice backtrace by default so you don't need a debugger for figuring out where that problematic statement is.

[jansol]

You can build & run your code via tasks now. Certain setups also have the ability to detect test functions in the code and run them with a button in the gutter. No debugging yet.

[panakour]

There is a draft implementation for debugger here #13433