On Thu, Sep 2, 2010 at 5:30 AM, Marc Weber wrote:
> Y usually copy the results of the quickfix window into a new buffer and
> then use :g or :v or or the like to keep the lines I'm interested in (I
> mapped this "filter lines") so its very fast for me.
>
> For huge projects I don't use grep - I us
On Wed, Sep 1, 2010 at 11:39 PM, Gary Johnson wrote:
> On 2010-08-31, Britton Kerin wrote:
>> Hello,
>>
>> I only fairly recently found out about :copen :lopen etc. Some snippets
>> using
>> them are popular on vim_use:
>>
>>
>> http://groups.google.com/group/vim_use/browse_thread/thread/21
Y usually copy the results of the quickfix window into a new buffer and
then use :g or :v or or the like to keep the lines I'm interested in (I
mapped this "filter lines") so its very fast for me.
For huge projects I don't use grep - I use gnu id utils for speed
reasons.
Writing additional filter
On Aug 31, 3:00 pm, Britton Kerin wrote:
>
> * Its not easy to filter the grep results. When a user needs to grep it
> usually means:
>
The command VxOccur from the vimuiex plugin (vimscript#2606) tries
to solve this problem. The vimgrep results are displayed in a popup
window and can be fur
On 2010-08-31, Britton Kerin wrote:
> Hello,
>
> I only fairly recently found out about :copen :lopen etc. Some snippets using
> them are popular on vim_use:
>
>
> http://groups.google.com/group/vim_use/browse_thread/thread/211ed834076e7526/9f756b498db39636?lnk=gst&q=Run+lgrep+then+immediat
Hello,
I only fairly recently found out about :copen :lopen etc. Some snippets using
them are popular on vim_use:
http://groups.google.com/group/vim_use/browse_thread/thread/211ed834076e7526/9f756b498db39636?lnk=gst&q=Run+lgrep+then+immediately+#9f756b498db39636
At minimum, I think these c
