It’s so critical to use text editors for software development and extract all other functionality to separate shell tools.
If a mix of very simple vim or Emacs + grep / git grep / silver searcher + CLI tools for automatic linting, test cases, etc., isn’t efficient for you, and motivates you to bring all these things into one consolidated IDE, I urge you to consider that this is a type of bad code smell and bad workflow smell, the all-in-one IDE is not actually helping productivity but hurting it in the long run, and you should invest right away in the learning curve & barriers you perceive are blocking you from a purely shell command-line workflow that separates code management & search into isolated utilities in separate interfaces.
I do grant there are a very small number of use cases where the IDE approach is useful: helping students who are literally just starting out, helping developers with atypical accessibility constraints that can be assisted with the IDE, probably a few more.
But general code search, linter/test integration, and embedded features like autocomplete, pop-up signatures or docs, etc., are disastrously bad things hands down for regular development.
It’s such a shame that a whole generation of programmers are tricked into believing those things are good for them.
It reminds me of people tricked into becoming reliant on MATLAB or Jupyter notebooks, and then retroactively trying to defend those tools as productivity-enhancing when they are, from first principles, productivity destroyers.