On Thursday, March 21, 2013 1:24:12 PM UTC-4, Gary Johnson wrote:
> On 2013-03-20, FlashBurn wrote:
> 
> > On Tuesday, March 19, 2013 5:54:23 PM UTC-4, Christian Brabandt wrote:
> 
> 
> 
> > > You need 2 commands:
> 
> > > 
> 
> > > :copen
> 
> > > 
> 
> > > :norm! "\<Cr>"
> 
> > > 
> 
> > 
> 
> > I tried the following:
> 
> > function! CscopeFind(action, word)
> 
> >   try
> 
> >     exe ':cs f '.a:action.' '.a:word
> 
> >     copen
> 
> >     normal "\<cr>"
> 
> >   catch
> 
> >     echohl WarningMsg | echo 'Can not find '.a:word.' with querytype as 
> > '.a:action.'.' | echohl None
> 
> >   endtry
> 
> > endfunction
> 
> > 
> 
> > And it didn't work. I also tried normal "<cr>", normal! "\<cr>",
> 
> > and normal! "<cr>". None of them worked. Does anybody have any
> 
> > other ideas?
> 
> 
> 
> I think that should have worked.
> 
> 
> 
> I grep'd for a pattern, executed ":copen" and tried various
> 
> ":normal" commands with "\<CR>", "\<LF>" and "\<Enter>" and none
> 
> worked.  I think this may be a bug.
> 
> 
> 
> However, I also skimmed quickfix.txt and found that the command
> 
> ".cc" should also work, and it worked for me, so try
> 
> 
> 
>     .cc
> 
> 
> 
> where you now have
> 
> 
> 
>     normal "\<cr>"
> 
> 
> 
> HTH,
> 
> Gary

Gary it worked. But I didn't use normal ".cc", I simply used cc instead. 
Here is how it looks

function! CscopeFind(action, word)
  try
    exe ':cs f '.a:action.' '.a:word
    copen
    cc
  catch
    echohl WarningMsg | echo 'Can not find '.a:word.' with querytype as 
'.a:action.'.' | echohl None

I'm also wondering if the dot (.) in front of a cc in your response is a type, 
or Vim has special meaning for it

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to