Yrurtj

The default vim filetype commands create new bindings beginning with [ and ]. Is there a way to prevent them from doing so or control which bindings are created?

I like using [ and ] to scroll up and down by half pages, by analogy with { and } for paragraph navigation.

nnoremap ] <c-d>

vnoremap ] <c-d>

xnoremap ] <c-d>



nnoremap [ <c-u>

vnoremap [ <c-u>

xnoremap [ <c-u>

It works well for the text filetype, but programming language filetypes typically have bindings beginning with [ and ], for instance for python files there are many structural navigation commands that I tend not to use:

...

n  [M          *@:call <SNR>25_Python_jump('n', 'vSn*(^(s*n*)*(class|def|async def)|^S)', 'Wb', 0, v:count1)<CR>

n  [m          *@:call <SNR>25_Python_jump('n', 'v^s*(class|def|async def)>', 'Wb', v:count1)<CR>

n            *@:call <SNR>25_Python_jump('n', 'vS.*n+(def|class)', 'Wb', 0, v:count1)<CR>

n  [[          *@:call <SNR>25_Python_jump('n', 'v^(class|def|async def)>', 'Wb', v:count1)<CR>

...

n  ]M          *@:call <SNR>25_Python_jump('n', 'vSn*(%$|^(s*n*)*(class|def|async def)|^S)', 'W', 0, v:count1)<CR>

n  ]m          *@:call <SNR>25_Python_jump('n', 'v%$|^s*(class|def|async def)>', 'W', v:count1)<CR>

n  ][          *@:call <SNR>25_Python_jump('n', 'v%$|S.*n+(def|class)', 'W', 0, v:count1)<CR>

n  ]]          *@:call <SNR>25_Python_jump('n', 'v%$|^(class|def|async def)>', 'W', v:count1)<CR>

The file that defines this is located at

/usr/share/vim/vim81/ftplugin/python.vim

and does not appear to check the value of a "configuration variable" to determine whether it should bind keys.

Is there a creative way to overrule it?

You can unmap these within a file called ~/.vim/after/ftplugin/python.vim or $HOME/vimfiles/after/ftplugin/python.vim on windows, etc. containing:

silent! nunmap <buffer> ]]

silent! nunmap <buffer> [[

silent! nunmap <buffer> ][

silent! nunmap <buffer> 

" and so on ...

vim executes scripts of the form after/ftplugin/{filetype}.vim after ftplugin/{filetype}.vim so you cna provide arbitrary overrides to the defaults.

Alternatively, you can use autocmds within your vimrc as follows:

function! PythonUnmaps()

    silent! nunmap <buffer> ]]

    silent! nunmap <buffer> [[

    silent! nunmap <buffer> ][

    silent! nunmap <buffer> 

    " and so on...

endfunction

augroup my_python_overrides

    au!

    autocmd FileType python call PythonUnmaps()

augroup END

Both of these approaches are general, you can replace python with whichever filetype you want to alter the settings for.