Idea: Compilation Buffer / Build Output Panel with Jump-to-Error Navigation

[rcdware]

I really love Helix's minimalism, and the whole philosophy of do a set of things really well, and don't enlarge the scope too much.

I do think that one feature merits implementation and furthering Helix's capabilities, and that is a compilation buffer. One killer feature I like in Emacs is the ability to compile a project and view the output in a buffer that lets me jump to errors and warnings really quickly.
I find that system so elegant (in the mire of bloat that is Emacs) because you just compile using a key press, then go to an error, then back to the code on the exact line you need, then compile again ...
compile -> error -> edit -> compile
This really encapsulates the most fundamental workflow in programming I feel. And I think that working with the compiler is more important than the LSP, because the LSP is a very good parser, but it doesn't always catch the actual run time errors or understand the build.

I believe that most people who talk about terminal integration, are probably looking for this kind of workflow, because a separate terminal seems a bit cluncky.

It would be great to have the possibility to just build and run with the single press of a key (just choosing to link a key to a command like gcc main.c -o main && .main or make or smth) , then directly have the output in a buffer containing the parsed text of the compilation output with navigation line to line and being able to return to the correct line.

For most text editors the current workflow is quit the editor (or change terminals), then run the commands, read the output, memorize the line, go back in, find the line, edit, repeat. It just feels clunky and kind of gets in the way of thinking about the coding problem if you know what I mean.

Is this feature doable you think? It's basically a regex parser with this form file:line:col: error message
from what I understand. I'm a bit new to open source, so I'm happy to take criticism :)

Thank you for taking the time to read

[CalebLarsen]

See this issue: #2934