Vim delay when using Ctrl+C, but only in SQL files

gvimvim

I'm working on a side project with both JavaScript and SQL source files. When I'm editing the JavaScript, Vim behaves normally. However, when I'm editing the SQL files, there's about a one-second delay between when I press CtrlC and when Vim exits insert mode. When I use the Escape key, or ShiftEnter which I mapped in my ~/.vimrc as a test, it shows no delay.

I thought perhaps it was something to do with the syntax highlighting, but when I ran :syntax off to try and fix it, the delay still showed up. I also tried :setf text, which also did not work. I have only a couple of plugins installed (CtrlP, NerdTree, and highlighters for Jade, Less, and CoffeeScript) so I don't think that's what's interfering.

Does anyone know what could be going on?

Best Answer

You seem to have a filetype plugin that installs a buffer-local mapping for Ctrl-C. You can check with

:verbose imap <buffer> <C-c>

It's probably the default one, cp. :help ft_sql. The prefix key can be reconfigured via this (in your ~/.vimrc):

let g:ftplugin_sql_omni_key = '<C-j>'

Related Solutions

Why does Vim only activate the highlight configuration after I source the .vimrc manually

The issue is caused by the sensible plugin:line 93. :help t_Co

" Allow color schemes to do bright colors without forcing bold.
if &t_Co == 8 && $TERM !~# '^linux'
  set t_Co=16  " << --- Causes hickup
endif

If you run vim in verbose log mode (vim -V15load_log.vim) – and search for t_Co= and RedundantSpaces you'll see that sensible is actually parsed after your appearance.vim file.

Quick fix would be to either comment out that section of the code and add it to your .vimrc, but as you link to git repositories that is perhaps not what you want.

A different approach would be to move it out of the bundledirectory and add it as a separate source line in your vimrc, before your glob loop.

I.e.:

  source ~/.vim/hacks/vim-sensible/plugin/sensible.vim

  for f in split(glob ...

Another way would be to load custom highlight on BufLoad.

Etc. …

Suppress recovery files when editing sensitive files in vi, nvi, and vim

For vim you can move the location of the recovery file with the directory option.

set directory=/tmp/XXXXXXXX

This can be added to the command line for a single instance like this

mkdir -m700 /tmp/xyz
vim --cmd "set directory=/tmp/xyz" /path/to/secure.file

Best Answer

Related Solutions

Why does Vim only activate the highlight configuration after I source the .vimrc manually

Suppress recovery files when editing sensitive files in vi, nvi, and vim

Related Question