-
Notifications
You must be signed in to change notification settings - Fork 203
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
neocomplete screenshots #10
Comments
Thanks. I will add them later.
Yes. I think gif is better choice. |
Thanks. I wii add them. |
neco-look is supported neocomplete.vim source. |
https://github.com/Shougo/vim-neco-calc I added neocomplete source in neco-alc and sent pull request. |
yes, neco-look supports, it is a mistake |
thank you. I merged pull request. |
Thanks. I deleted forked repository. |
I think fuzzy complement will display a lot of candidate word , it is inconvenient to choose expect word |
Yes,it makes sense |
What's the behavior? I don't understand it. |
OK. I implemented it. |
What about adding some in README.md and others in wiki page? |
Not in plan. |
change to neocomplete ,and delete YCM 💃 |
@Shougo Most people dont read the man but it never stop developers to make them. Thankfully. A good alternative would be to put the doc where the doc should be (on GitHub, it is the wiki) and add a link to the most important page in the README.md. |
I want to replace the screenshots in README.
If you have good screenshots for neocomplete README, can you add it in this issue?
The text was updated successfully, but these errors were encountered: