You are not logged in.
Hi all,
In my /etc/gvimrc I have:
map <A-1> :tabnext 1 <cr>
map <A-2> :tabnext 2 <cr>
etc..
which works most of the time.
However, whenever I load (or create) a file with a .cl extension (common lisp), these keybindings stop working.
All my other keybinds remain functional.
Anyone else have this issue?
EDIT: I should also note that typing the command :tabnext <whatever> works fine.
Last edited by Fragasaurus (2011-01-26 18:12:02)
Offline
Maybe you have a plugin for .cl filetype? If so, try to disable it.
Offline
You may create a session file from a cl session (with :mksession) and then check this file, say "Session.vim", for mappings.
grep map Session.vim
This should reveal whether there were those mappings redefined. If so check for .cl related plugins as karol suggested.
To know or not to know ...
... the questions remain forever.
Offline
Just do a
:verbose map <A-1>
and vim should show you where it was mapped last.
Offline
Just do a
:verbose map <A-1>
and vim should show you where it was mapped last.
Before opening (or writing) a .cl or .lisp file it says the expected..
Last set from /etc/gvimrc
but after it just says "no mapping found".
Also, I tried temporarily deleting all the plugins in vim73 and all the syntax files for cl and lisp, but that didn't make a difference either.
I should note that I have no plugins installed aside from whatever comes by default.
Offline
Very strange... It seems some plugin loaded by the lisp filetype disables the
mapping. Could you run diff on the output of :scriptnames before and after
editing a lisp file? Maybe we can narrow the bad guy like this.
Also, (if I may do a little advertisement) the guys on freenode's #vim channel
are very helpful, so if you don't fear diving into the waves of IRC, you might
get your answer there.
Offline
Very strange... It seems some plugin loaded by the lisp filetype disables the
mapping. Could you run diff on the output of :scriptnames before and after
editing a lisp file? Maybe we can narrow the bad guy like this.Also, (if I may do a little advertisement) the guys on freenode's #vim channel
are very helpful, so if you don't fear diving into the waves of IRC, you might
get your answer there.
Thanks! Somewhere along the line a file called /usr/share/vim/vimfiles/after/syntax/lisp.vim was created. Removing this file solved the problem. I'm not sure where it came from, though.
EDIT: It seems this file is installed with the clisp package. It was clisp's problem, not vim's.
Last edited by Fragasaurus (2011-01-28 14:39:37)
Offline
Thanks! Somewhere along the line a file called /usr/share/vim/vimfiles/after/syntax/lisp.vim was created. Removing this file solved the problem. I'm not sure where it came from, though.
EDIT: It seems this file is installed with the clisp package. It was clisp's problem, not vim's.
Glad you got it working.
As to the file ownership: Next time, go with a
pacman -Qo file
to see what package file belongs to.
Offline