E227 warning when using both yankring and improvedft

[alick]

Hi, I have installed YankRing before. After installing improvedft I met E227 warning at vim startup:

Error detected while processing function ftimproved#Activate..37_Map:
line 3:
E227: mapping already exists for f
E227: mapping already exists for F
E227: mapping already exists for t
E227: mapping already exists for T
E227: mapping already exists for ;
E227: mapping already exists for ,

Can these warnings be eliminated?

[chrisbra]

Hi Alick!

On So, 05 Aug 2012, Alick Zhao wrote:

Hi, I have installed YankRing before. After installing improvedft I met E227 warning at vim startup:

Error detected while processing function ftimproved#Activate..37_Map:
line 3:
E227: mapping already exists for f
E227: mapping already exists for F
E227: mapping already exists for t
E227: mapping already exists for T
E227: mapping already exists for ;
E227: mapping already exists for ,

Can these warnings be eliminated?

Yeah, I know, that Yankring already maps those keys to its own function
and that prevents using the ft_improved plugin.

I see, if I can find a way to make both plugins work.

regards,

Christian

Die Klasse, welche die herrschende materielle macht der Gesellschaft
ist, ist zugleich ihre herrschende geistige Macht.
-- Karl Marx

[chrisbra]

I wonder, why the yankring plugin is loaded before the improved_ft plugin. That shouldn't happen. Can you show me your :scriptnames output?

[alick]

Perhaps it is because the letter case: I use YankRing as the directory name instead of yankring.

The :scriptnames output (without improvedft plugin since I haven't enabled it again):

1: /etc/vimrc
2: /usr/share/vim/vim73/syntax/syntax.vim
3: /usr/share/vim/vim73/syntax/synload.vim
4: /usr/share/vim/vim73/syntax/syncolor.vim
5: /usr/share/vim/vim73/filetype.vim
6: ~/.vim/ftdetect/csv.vim
7: /usr/share/vim/vim73/ftplugin.vim
8: ~/.vimrc
9: /usr/share/vim/vim73/syntax/nosyntax.vim
10: ~/.vim/autoload/pathogen.vim
11: /usr/share/vim/vim73/ftoff.vim
12: ~/.vim/bundle/vim-pandoc/ftdetect/pandoc.vim
13: /usr/share/vim/vim73/indent.vim
14: /usr/share/vim/vim73/ftplugin/man.vim
15: ~/.vim/plugin/AnsiEscPlugin.vim
16: ~/.vim/plugin/ShowFuncKeys.vim
17: ~/.vim/plugin/SyntaxFolds.vim
18: ~/.vim/plugin/abolish.vim
19: ~/.vim/plugin/cecutil.vim
20: ~/.vim/plugin/filebrowser.vim
21: ~/.vim/plugin/genutils.vim
22: ~/.vim/plugin/hanoi.vim
23: ~/.vim/plugin/imaps.vim
24: ~/.vim/plugin/libList.vim
25: ~/.vim/plugin/matchit.vim
26: ~/.vim/plugin/punc-trans.vim
27: ~/.vim/plugin/remoteOpen.vim
28: ~/.vim/plugin/tetris.vim
29: ~/.vim/plugin/vimcdoc.vim
30: ~/.vim/plugin/vimim.vim
31: ~/.vim/plugin/vsearch.vim
32: ~/.vim/bundle/LargeFile/plugin/LargeFile.vim
33: ~/.vim/bundle/Recover.vim/plugin/recover.vim
34: ~/.vim/bundle/Recover.vim/autoload/recover.vim
35: ~/.vim/bundle/YankRing/plugin/yankring.vim
36: ~/.vim/bundle/nerdcommenter/plugin/NERD_commenter.vim
37: ~/.vim/bundle/snipmate/plugin/snipMate.vim
38: ~/.vim/bundle/vim-addon-mw-utils/autoload/funcref.vim
39: ~/.vim/bundle/snipmate/plugin/snipMateInterface.vim
40: ~/.vim/bundle/tlib_vim/plugin/02tlib.vim
41: ~/.vim/bundle/vcscommand/plugin/vcsbzr.vim
42: ~/.vim/bundle/vcscommand/plugin/vcscommand.vim
43: ~/.vim/bundle/vcscommand/plugin/vcscvs.vim
44: ~/.vim/bundle/vcscommand/plugin/vcsgit.vim
45: ~/.vim/bundle/vcscommand/plugin/vcshg.vim
46: ~/.vim/bundle/vcscommand/plugin/vcssvk.vim
47: ~/.vim/bundle/vcscommand/plugin/vcssvn.vim
48: ~/.vim/bundle/vim-pandoc/plugin/pandoc.vim
49: /usr/share/vim/vimfiles/plugin/cctree.vim
50: /usr/share/vim/vim73/plugin/getscriptPlugin.vim
51: /usr/share/vim/vim73/plugin/gzip.vim
52: /usr/share/vim/vim73/plugin/matchparen.vim
53: /usr/share/vim/vim73/plugin/netrwPlugin.vim
54: /usr/share/vim/vim73/plugin/rrhelper.vim
55: /usr/share/vim/vim73/plugin/spellfile.vim
56: /usr/share/vim/vim73/plugin/tarPlugin.vim
57: /usr/share/vim/vim73/plugin/tohtml.vim
58: /usr/share/vim/vim73/plugin/vimballPlugin.vim
59: /usr/share/vim/vim73/plugin/zipPlugin.vim
60: ~/.vim/bundle/snipmate/after/plugin/snipMate.vim
61: /usr/share/vim/vim73/scripts.vim
62: /usr/share/vim/vim73/ftplugin/help.vim
63: /usr/share/vim/vim73/syntax/help.vim
64: ~/.vim/syntax/help_cn.vim

[chrisbra]

Oh well, in this case, the output of :scriptnames is not really useful...

Please try current head and in your .vimrc put the following:

let g:yankring_zap_keys = '/ ?'

regards,
Christian

[alick]

I tried the current head and warning messages appear less. But there are still warnings saying mapping already exists for ; and , . Can these warnings be avoided too?

[chrisbra]

Hi Alick!

On Mi, 15 Aug 2012, Alick Zhao wrote:

I tried the current head and warning messages appear less. But there are still warnings saying mapping already exists for ; and , . Can these warnings be avoided too?

Ah, I see. Thanks for the feedback. Please try current head. It should
work now.

regards,

Christian

Mit leerem Kopf nickt sich's leichter.

[alick]

On Wed, 15 Aug 2012 11:41:58 -0700, chrisbra wrote:

On Mi, 15 Aug 2012, Alick Zhao wrote:

Ah, I see. Thanks for the feedback. Please try current head. It should
work now.

But it doesn't work for me. The error message shown on vim startup is:

 YR: The YankRing is now disabled
 YR: The YankRing is now enabled
 Error detected while processing function 

ftimproved#Activate..37_Map:
line 3:
E227: mapping already exists for ;
E227: mapping already exists for ,

Alick

[chrisbra]

Hi Alick!

On Do, 16 Aug 2012, Alick Zhao wrote:

On Wed, 15 Aug 2012 11:41:58 -0700, chrisbra wrote:

On Mi, 15 Aug 2012, Alick Zhao wrote:

Ah, I see. Thanks for the feedback. Please try current head. It should
work now.

But it doesn't work for me. The error message shown on vim startup is:

 YR: The YankRing is now disabled
 YR: The YankRing is now enabled
 Error detected while processing function 

ftimproved#Activate..37_Map:
line 3:
E227: mapping already exists for ;
E227: mapping already exists for ,

Okay, please try with current head. This works here.

regards,

Christian

Halt den Mund, wenn ich dich unterbreche!

[alick]

Thanks for your efforts! It works well now :)