> Maxim Abalenkov \\
maxim.a...@gmail.com <mailto:
maxim.a...@gmail.com>
This assumes vim-latex-1.10 ...
The keymap's (buffer-local) language mapping for `.' is overruled by a
buffer-local Insert mode mapping.
To show the problem: in a LaTeX (ft=tex) buffer:
:imap <buffer> .
(or just)
:imap .
shows something like (depending on g:Tex_SmartKeyDot)
<C-R>=<SNR>20_SmartDots()<CR>
or <C-R>=<SNR>12_LookupCharacter(".")<CR>
You can remove the Insert mode mapping after it gets defined:
Create a file
after/ftplugin/tex.vim
containing the line
iunmap <buffer> .
for example the file ~/.vim/after/ftplugin/tex.vim where
~/.vim/after must occur in the 'runtimepath'.
--------------------------------------------------------------
You can ignore what follows.
An alternative is to
put in the vimrc:
:let g:Tex_SmartKeyDot = 0
and to put in the after/ftplugin/tex.vim file:
" :echo IMAP_list_all('.')
" tex: "`. => "`.
" tex: \`. => \`.
" tex: ``. => ``.
" tex: `. => \cdot
if exists('*IUNMAP') && maparg('.', 'i') =~# '<SNR>\d\+_LookupCharacter("\.")'
call IUNMAP('"`.', 'tex')
call IUNMAP('\`.', 'tex')
call IUNMAP('``.', 'tex')
call IUNMAP('`.', 'tex')
endif
Would have been cleaner if there was an IUNMAP_ALL('.', 'tex') function ...
And not sure about the exact consequences ... the mapping for `.' is
created per buffer, but IMAP() creates internal data structures per
filetype.
--
Andy