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 breaks wrapping behaviour in insert mode #345

Closed
jonhoo opened this Issue Jan 15, 2015 · 13 comments

Comments

Projects
None yet
3 participants
@jonhoo

jonhoo commented Jan 15, 2015

Minimal .vimrc:

set runtimepath=~/.vim/bundle/neocomplete
set nocompatible

let g:acp_enableAtStartup = 0
let g:neocomplete#enable_at_startup = 1
set tw=5

Open vim, go to insert mode, type:

abcde<ENTER>
abcde fghij

fghij should be automatically wrapped to the next line as can be seen by running vim -u NONE, setting tw=5 explicitly, and doing the same. If the second line starts with something that does not have a completion, wrapping works correctly.

Using git bisect, I've found that this issue was introduced in 1f7da02.

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo

Shougo Jan 19, 2015

Owner

#336

  • neocomplete uses complete() instead of completefunc
  • complete() uses line completion to implement it (I don't know why)
  • line completion does not break lines(Yes, it is true)
  • Wow, neocomplete does not break lines!
Owner

Shougo commented Jan 19, 2015

#336

  • neocomplete uses complete() instead of completefunc
  • complete() uses line completion to implement it (I don't know why)
  • line completion does not break lines(Yes, it is true)
  • Wow, neocomplete does not break lines!

@Shougo Shougo closed this Jan 19, 2015

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Jan 20, 2015

Contributor

@Shougo there is no way to fix this? It is a really annoying. Please, if possible, try to find a workaround. Thanks!

Contributor

petobens commented Jan 20, 2015

@Shougo there is no way to fix this? It is a really annoying. Please, if possible, try to find a workaround. Thanks!

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo

Shougo Jan 21, 2015

Owner

Nothing. You can use prevous version of neocomplete.

Owner

Shougo commented Jan 21, 2015

Nothing. You can use prevous version of neocomplete.

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Jan 21, 2015

Contributor

Mmm I see, what a pity. Why do you use complete() instead of completefunc?

Contributor

petobens commented Jan 21, 2015

Mmm I see, what a pity. Why do you use complete() instead of completefunc?

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo
Owner

Shougo commented Jan 21, 2015

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Jan 22, 2015

Contributor

I see. Thanks. I hope some day this will work again.

Contributor

petobens commented Jan 22, 2015

I see. Thanks. I hope some day this will work again.

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo

Shougo Jan 25, 2015

Owner

I will report the problem in vim_dev later.

Owner

Shougo commented Jan 25, 2015

I will report the problem in vim_dev later.

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Jan 25, 2015

Contributor

Thank you

Contributor

petobens commented Jan 25, 2015

Thank you

@Shougo Shougo added the wontfix label Jan 27, 2015

@jonhoo

This comment has been minimized.

Show comment
Hide comment
@jonhoo

jonhoo Feb 12, 2015

@Shougo: Did you report this upstream in vim_dev in the end? Any chance you could post a link to track progress?

jonhoo commented Feb 12, 2015

@Shougo: Did you report this upstream in vim_dev in the end? Any chance you could post a link to track progress?

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo
Owner

Shougo commented Feb 16, 2015

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Feb 16, 2015

Contributor

@Shougo thank you. I've upvoted the patch

Contributor

petobens commented Feb 16, 2015

@Shougo thank you. I've upvoted the patch

yangle added a commit to yangle/dotfiles that referenced this issue Mar 1, 2015

@petobens

This comment has been minimized.

Show comment
Hide comment
@petobens

petobens Mar 6, 2015

Contributor

@jonhoo , @Shougo using vim with patch 653 the problem seems fixed.

Contributor

petobens commented Mar 6, 2015

@jonhoo , @Shougo using vim with patch 653 the problem seems fixed.

@Shougo

This comment has been minimized.

Show comment
Hide comment
@Shougo

Shougo Mar 7, 2015

Owner

Yes. Thanks.

Owner

Shougo commented Mar 7, 2015

Yes. Thanks.

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