The problem with a native vim window is that it doesn't give you much affordance in terms of UI, you can't collapse files that have a lot of matches, hard to remember options and syntax for regex/case sensitivity, etc.
The collapsing sounds like a valid complaint. The rest falls on deaf ears for this vim user.
I would expect most vim users to feel the same since those complaints are either considered features or the common barrier to entry that vim has anyway. Am I wrong?
You can consider it a matter of preference, I suppose. I prefer having a GUI file browser over NERDTree for similar reasons as I outlined before. VimAck has the same line of thinking behind it.
Comments
The problem with a native vim window is that it doesn't give you much affordance in terms of UI, you can't collapse files that have a lot of matches, hard to remember options and syntax for regex/case sensitivity, etc.
The collapsing sounds like a valid complaint. The rest falls on deaf ears for this vim user.
I would expect most vim users to feel the same since those complaints are either considered features or the common barrier to entry that vim has anyway. Am I wrong?
You can consider it a matter of preference, I suppose. I prefer having a GUI file browser over NERDTree for similar reasons as I outlined before. VimAck has the same line of thinking behind it.
Yeah, I totally get that. I'm just assuming that the average vim user is going to prefer things to work vim-native over anything else.
It puts the results in a quickfix window, which has a well-defined set of keybindings for navigation and refinement.