Or just use an IDE. It's 2022 people! We don't have to code like it's 1985.
Use whatever headless buildscripts you fancy (make?!) to build your project.
Problem solved.
If you wanted code-completion, you'd better use LSP anyways, and you'll get all that fancy compiler diagnostics and whatever in your editor.
I don’t think I’ve ever seen the build and code repo tooling ever work on any professional codebase I’ve worked on, save one.
Use grep or ag
>debugger
What's so painful about it?
No one serious would assert that inspecting complex data structure, managing breakpoints, stepping through code, or debugging remotely via text mode gdb like it’s 1986, is as easy or efficient as simply using a GUI in 2022, or even 1992.
Yeah I agree though in my experience it is because professional teams are usually infected by at least a few "everyone just uses Vim and a terminal right?" people who then go about turning the build system into some horrible script based system that IDEs can't work with.
For navigation I've used something like this since eternity: https://cloudef.pw/armpit/vim-bemenu-curses.mp4
For search, grep or ag will do. As for refactoring, personally I've never had the need for a tooling for that.
>Use whatever headless buildscripts you fancy (make?!) to build your project.
These are just fancy text editors at this point. IDE is like visual studio, or xcode. Sure some of those fancy editors still share the same problems, especially all the java ones (eclipse, android studio, jetbrains ...)