helm-swoop VS projectile

I am thinking myself of whether swiper/swoop functionality can entirely replace isearch, or whether it is better kept separate. You never use isearch at all?

Helm-swoop https://github.com/emacsorphanage/helm-swoop

The easiest way of doing this is using M-x occur which might be bound to M-s o by default. This will involve typing out the search string. I like using helm-swoop which I've bound to M-i, which searches for the thing at point, which is faster. Both of these tools generate the sparse buffer and let you jump around the file. The advantage of using occur is that you can invoke edit and then modify one or more occurences directly in the occur buffer.

Could you explain more about this setup? I'm not familiar with "projectile". Is this https://github.com/bbatsov/projectile the same thing you're referring to?

Sounds interesting. What I've done recently is open my vim in the folder that contains all the organization's repos (the ones I've cloned) and just run ripgrep inside vim to find examples or references to whatever I've seeking. Seems performant enough even without doing anything except letting ripgrep ignore git-ignored stuff (default behavior of ripgrep).

Sure. It sounds like it's working well enough. Here's a Github issue that may be of interest to you. Apparently you can get this behavior if there's a project marker file at a higher level.

With projectile you can define custom "run", "compile", "test" commands per project. Also there are pre-defined commands for many known project types.

Thanks for your detailed explanation, but no that is no that is not the question. This is projectile: https://github.com/bbatsov/projectile

I am currently trying with perspective rather than persp-mode, as it segregates the buffer list as I like (#1 above). I've got projectile with persp-projectile, and that seems to give me what I need for project navigation (#2 probably, still not 100%). I get some help in my mode line for project focus (#3, partially).