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

tmux-complete conflicts with neocomplete #29

Closed
mayersj1 opened this issue Apr 12, 2014 · 1 comment · Fixed by #30
Closed

tmux-complete conflicts with neocomplete #29

mayersj1 opened this issue Apr 12, 2014 · 1 comment · Fixed by #30

Comments

@mayersj1
Copy link

As both neocomplete and tmux complete use completefunc, a conflict arises.

Changing plugin/tmuxcomplete.vim to use omnifunc allows me to at least use tmux-complete in those filetypes that don't set a specific omnifunc value.

@wellle
Copy link
Owner

wellle commented Apr 13, 2014

I looked into it and created a neocomplete source in #30. So you should see the tmux completions in your normal completions now. I also added a #trigger option to disable the conflict:

let g:tmuxcomplete#trigger = 'completefunc' " <C-X><C-U> (default)
let g:tmuxcomplete#trigger = 'omnifunc'     " <C-X><C-O>
let g:tmuxcomplete#trigger = ''             " no trigger

Slightly longer version

Thank you! 👍

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

Successfully merging a pull request may close this issue.

2 participants