> I cannot for the life of me understand why it keeps re-indexing my codebase in certain circumstances. Perhaps this is some on-again off-again bug, but it comes back to bite me constantly.
This is the thing that drives me insane. The most annoying part is that they haven't built a proper cross-idea way to diagnose this. How hard is it to just have a UI, or even some text log, that says "I'm reindexing because X, Y, Z have changed" or something?
I used JetBrains IDEs for years, and dropped it years ago because of this. It was maddening then and crazy to hear that after all this time it’s still a problem.
I wasn't going to pipe up because I wasn't sure that a Hackernews thread is a good substitute for an issue tracker... but it's related to new AI-driven workflows so I hope it chins the bar.
Now that I work on 3-8 concurrent projects, I want to have them most of them open so I can interact, sense-check, be engaged in the work. When I tear down one worktree, ALL projects open in RubyMine concurrently re-index. It kills my M3 Max and I have to force quit. Then when I restart RubyMine it does the same so I have to race to press the tiny pause button on just enough of the projects for it to not die. There's no way to tweak the re-indexing settings or determine when it will kick off. WHY it kicks off - i don't know.
This is the single thing that's led me to Zed/VSCode, or to not open more than 2 at a time.