Skip to content
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

Open
Shougo opened this issue Jun 7, 2013 · 19 comments
Open

neocomplete screenshots #10

Shougo opened this issue Jun 7, 2013 · 19 comments

Comments

@Shougo
Copy link
Owner

Shougo commented Jun 7, 2013

I want to replace the screenshots in README.

If you have good screenshots for neocomplete README, can you add it in this issue?

@Shougo
Copy link
Owner Author

Shougo commented Jun 7, 2013

file
omni
vim
vimshell

@osyo-manga
Copy link
Collaborator

file_include
vim_func

also required gif file?

@Shougo
Copy link
Owner Author

Shougo commented Jun 7, 2013

Thanks. I will add them later.

also required gif file?

Yes. I think gif is better choice.

@UncleBill
Copy link

I want to append these two plugin
Imgur
but neither of them don't work with neocomplete.vim

neco-calc: misses source for `neocomplete.

@osyo-manga
Copy link
Collaborator

vim_func

@Shougo
Copy link
Owner Author

Shougo commented Jun 8, 2013

Thanks. I wii add them.

@Shougo
Copy link
Owner Author

Shougo commented Jun 8, 2013

but neither of them don't work with neocomplete.vim
neco-calc: misses source for `neocomplete.

neco-look is supported neocomplete.vim source.
What's the problem?
Yes. neco-calc is not supported neocomplete.vim.
I will add it.

@Shougo
Copy link
Owner Author

Shougo commented Jun 8, 2013

https://github.com/Shougo/vim-neco-calc
hrsh7th/vim-neco-calc#1

I added neocomplete source in neco-alc and sent pull request.

@UncleBill
Copy link

neco-look is supported neocomplete.vim source.
What's the problem?

yes, neco-look supports, it is a mistake

@hrsh7th
Copy link

hrsh7th commented Jun 8, 2013

thank you. I merged pull request.

@Shougo
Copy link
Owner Author

Shougo commented Jun 8, 2013

Thanks. I deleted forked repository.

@kdurant
Copy link

kdurant commented Jun 9, 2013

I think fuzzy complement will display a lot of candidate word , it is inconvenient to choose expect word
So the first letter must be entered correctly, the latter's fuzzy complete, like sublime

@lookforit
Copy link

I think fuzzy complement will display a lot of candidate word , it is inconvenient to choose expect word
So the first letter must be entered correctly, the latter's fuzzy complete, like sublime

Yes,it makes sense

@Shougo
Copy link
Owner Author

Shougo commented Jun 10, 2013

I think fuzzy complement will display a lot of candidate word , it is inconvenient to choose expect word
So the first letter must be entered correctly, the latter's fuzzy complete, like sublime

What's the behavior? I don't understand it.

@Shougo
Copy link
Owner Author

Shougo commented Jun 10, 2013

I think fuzzy complement will display a lot of candidate word , it is inconvenient to choose expect word
So the first letter must be entered correctly, the latter's fuzzy complete, like sublime

OK. I implemented it.

@pickfire
Copy link

What about adding some in README.md and others in wiki page?

@Shougo
Copy link
Owner Author

Shougo commented Apr 30, 2015

Not in plan.
I think in README.md is better.
Because, people watch README.md in first.
Most people don't read project wiki.

@wsdjeg
Copy link

wsdjeg commented Dec 3, 2015

change to neocomplete ,and delete YCM 💃

@aloisdg
Copy link

aloisdg commented Feb 7, 2016

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants