Thanks for the efforts for describing this workflow, but please note my point above about being "effortless" ;) To be a bit more specific: I need to see the st

Thanks for the efforts for describing this workflow, but please note my point above about being "effortless" ;) To be a bit more specific: I need to see the structure of what I'm searching in, so at minimum, that means neotree/nerdtree. I don't have photographic memory, or alphabetic memory, I always forget the names of folders, files, everything. I just couldn't care less. "../.." means nothing to me. What is that directory? Show me, and I will point to what I want. Also, I don't want to search in a project. I want to search in a project OR in multiple projects OR in a subdirectory within a project, ad hoc. OR just select some files and search in them. And in my opinion, for this specific use-case there is nothing wrong with using the mouse. When I'm searching for something in the way I described above I am usually browsing the code, reading it, trying to understand what is going on. This is different to when I'm actually coding something, then vi/emacs suddenly gets much more attractive, depending on the language used :)