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

process_buffer exits ctrl-x mode #305

Closed
taylor-peterson opened this issue Feb 10, 2016 · 5 comments
Closed

process_buffer exits ctrl-x mode #305

taylor-peterson opened this issue Feb 10, 2016 · 5 comments

Comments

@taylor-peterson
Copy link

The autocommand that calls gitgutter#process_buffer(bufnr(''), 1) when the CursorHoldI event is triggered exits the ctrl-x sub-mode. If updatetime is set to the recommended value, this makes it very difficult to use completion.

Repro-Steps:

  1. enable vim-gitgutter
  2. :set updatetime=1000 (to better see what's going on)
  3. :set showmode
  4. Enter insert mode -> status line displays that you are in insert mode
  5. Hit ctrl-x ->status line displays that you are in ctrl-x mode
  6. updatetime later, CursorHoldI is triggered, calling process_buffer and you are dropped out of ctrl-x mode back into insert mode

Desired Behavior:
You remain in ctrl-x mode after the process_buffer call.

@airblade
Copy link
Owner

I have never noticed this before. I don't know how to detect the i_CTRL-X submode so I have asked on vim_use.

@TKr
Copy link

TKr commented Feb 10, 2016

Same issue

@airblade
Copy link
Owner

No reply on vim_use so I have asked on vim_dev.

@airblade
Copy link
Owner

airblade commented Apr 20, 2016

This is a vim problem: I can reproduce it without vim-gitgutter.

  1. Start vim with:

    vim -u NONE -N --cmd 'set updatetime=1000' --cmd 'set showmode' --cmd 'autocmd CursorHoldI * 1'

  2. Type i to enter insert mode.

  3. Type CTRL-x to enter the insertion completion submode.

  4. Expected: vim stays in insertion completion submode. Actual: after 1 second the mode changes back to insert mode.

I'll leave this issue open for now and wait to see what happens on vim_dev.

@airblade
Copy link
Owner

This is fixed in Vim 7.4.1758.

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

3 participants