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

Document interactions between lexima and neocomplete #66

Open
gotgenes opened this issue Nov 6, 2016 · 0 comments
Open

Document interactions between lexima and neocomplete #66

gotgenes opened this issue Nov 6, 2016 · 0 comments

Comments

@gotgenes
Copy link

gotgenes commented Nov 6, 2016

In issue #65, @cohama said

In the past, I introduced some codes to hide popup menu forcely because some auto completion plugins (e.g. neocomplete) conflict with lexima.vim.

and

If you use any auto completion plugin, conflicts lexima's one.
It requires more time to solve both 2 problems simultaneously.

I recently started using neocomplete. I would like to know more about the interactions between lexima and neocomplete. I can see from this search there has been discussion of the two, but I don't find any documentation in lexima's Vim documentation. I'm especially interested in how users can minimize the negative interactions between these plugins.

For example, does the order of loading the plugins matter (e.g., do I need to load lexima before I load neocomplete, or vice versa)?

If I want to define <CR> behavior in the insert mode popup completion, as described in this comment,

imap <expr> <CR> pumvisible() ? "\<C-y>" : "\<CR>"

does this need to be defined after setting some configurations for lexima e.g.,

let g:lexima_no_default_rules = 1
call lexima#set_default_rules()

or can it be defined before those lexima configurations? (It seems like it must happen after lexima configuration.)

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

No branches or pull requests

1 participant