-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue when running it at the 1st time #6
Comments
Thanks. Hm... I guess this issue is related with |
yes, you are right. the fact is as what you said. Removing the |
Thanks for the confirmation. Hmm.... I don't know why but something conflict with lazy loading mappings. I guess we should report it to neobundle as well. But, anyway, I recommend you not to use lazy loading with incsearch.vim (and vim-asterisk as well) because incsearch.vim doesn't execute heavy scripts at startup at all. There are just some definition of mappings and commands. |
Oh, and I guess this is incsearch.vim's problem, not vim-asterisk's one. |
Previously, incsearch.vim just works fine. However, this issue occurs after adding the vim-asterisk. Thus I file report it to asterisk. I think if there is anther issue report (in incsearch.vim or neobundle) to keep track of this, you could feel free to close it. I accept that remove the lazy suffix, it is not a big deal. Now things are done and thanks. |
Hm, how about vim-anzu? |
Oh, the I have a question, should I still add
I test it also, |
Thanks! Hmm... vim-asterisk use
Oh, I guess that's my bad. My explanation in the document is confusing. |
I have installed
haya14busa/incsearch.vim
,haya14busa/vim-asterisk
,osyo-manga/vim-anzu
andthinca/vim-visualstar
vianeobundle
. And here are the settings for these plugins:Open a file via
vim
, move cursor to a word and press*
. It doesn't search the word under the cursor. Clear the unexpected result, move cursor the a word and press*
again. It just works fine. This issue only happens when we do the search for the 1st time.The text was updated successfully, but these errors were encountered: