-
-
Notifications
You must be signed in to change notification settings - Fork 293
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
deoplete screenshots #96
Comments
I recorded a gif of deoplete + echodoc: https://github.com/archSeer/nvim-elixir/blob/master/autocomplete.gif |
Thank you! |
let me show you some dark color pic |
@Shougo Using PaperColor theme? |
@pickfire Yep, that's PaperColor. |
Thanks. updated. |
@SageEx what font are you using in those screenshots? |
@myhonor16 It's Fantasque Sans Mono. On Wed, Mar 2, 2016 at 12:17 AM, Samuel notifications@github.com wrote:
|
@SageEx Thanks! |
Does it support c++? I don't see any screenshots of a c++ project. |
@bjadamson https://github.com/zchee/deoplete-clang All you need to do for any language is find/create the sources. Deoplete can support anything |
Thanks. I will update it later. |
Thanks. I have updated it. |
@nhooyr what colorscheme do you use? |
@nhooyr thanks. Do you have this colorscheme set up for you terminal as well? |
@yevhen-m yes, I use it in iTerm2. |
@nhooyr How can I set it up in iterm too? |
@yevhen-m It isn't really intended for other people to use, at least yet. If you still want to use it, you can just clone the repo and import |
@archseer Hate to be that guy but, do you remember the name of the colorscheme used in the GIF? https://github.com/archSeer/nvim-elixir/blob/master/autocomplete.gif |
looks like a colorscheme just for elixir language 😄 |
Updated. |
Updated. |
It would be nice to have the deoplete configuration for every screenshot showed... |
I'd be happy to post mine, @Shougo would you want to add a section with footnotes containing the config for each screenshot? |
I think the link is better than paste the configuration. |
Thank you @Shougo and @afnanenayet! That would be great for newbies to have simple snippets as configuration starting point. |
Here's a gist with my deoplete settings: |
@afnanenayet Sorry for off topic, but I see that you use python-language-source. How's your experience with it? Is it better than deoplete-jedi + jedi in terms of completion, goto definition, etc? |
The language server uses Jedi for source code analysis, so using the server just gives me the bonus of having a readily available linter, etc. |
I have added the link. |
Hello, sorry for the possibly tedious answer... I was looking at @richox gif using neco-vim and exploring g:deplete variables and I've realized that, although I am able to see all functions after typing
is it possible that some other external sources are messing up with neco-vim? thank you! and sorry to bother! I'm quite new to neovim (just made the big step from vim a few days ago) and I still have to get used to @Shougo awesome (but tricky! ;P) plugins! |
It is feature. |
@Shougo thank you for your prompt reply! I see, but If I call Thank you again! |
You don't have to set all options. Please read the documentation...
Possible. Please use imap <expr><C-Space> deoplete#manual_complete() |
thank you @Shougo, I feel bad for this off topic, but what I was aiming for is to be able to press |
It is bug of neovim. |
I have fixed the manual completion error. |
this is exactly the behavior I expected! thanks! The process remains there hanging even after i close neovim. It happens only if I call manual completion after a whitespace, not after or within a word. Also, the problem seems to arise only on a [New Buffer] type of buffer (i.e. no filetype specified or unsaved?). I am not able to reproduce this consistently though. It might depend on I don't think it is your bug, but advise users to be careful about "unexpected behavior" when using this feature in some circumstances, as it is likely that literally all available candidates from all sources will try to populate the list! Thank you again Shougo |
I don't work for the problem. |
I think it seems tmux-complete.vim problem. |
You have said |
The input check should be added. |
スクリーンショット。 |
OK. I have updated it. |
This site is not Q/A site. And you should read deoplete documentation.
|
Thanks. |
I want to add the screenshots in README.
If you have good screenshots for deoplete README, can you add it in this issue?
The text was updated successfully, but these errors were encountered: