Closed GoogleCodeExporter closed 9 years ago
I do not follow any github versions of vimwiki.
So, have you tried version from this repository?
Original comment by habamax
on 18 May 2012 at 8:28
I tried this repo, but I found have some weird problem, so I use the github
mirror repo still.
Original comment by numbch...@gmail.com
on 18 May 2012 at 8:38
I use this github mirror rep for a long time. this "Enter" issue occurs
recently.
Original comment by numbch...@gmail.com
on 18 May 2012 at 8:39
And sometimes google code will be banned. so I think github is more safe.
Original comment by numbch...@gmail.com
on 18 May 2012 at 8:39
You don't use vimwiki from this site (and vim plugin site) do you?
I wonder how I can help you then?
Original comment by habamax
on 18 May 2012 at 8:44
Let me rephrase myself.
Are you *sure* the problem you report exists in the current state of vimwiki?
Original comment by habamax
on 18 May 2012 at 8:48
weird. I use this google code version, then get similar problem <SNR>251_CR().
Original comment by numbch...@gmail.com
on 18 May 2012 at 9:24
Could you attach your vimrc here?
Original comment by habamax
on 18 May 2012 at 9:36
What is the output of
:verbose map <CR>
issued from vimwiki file?
Original comment by habamax
on 18 May 2012 at 9:37
My vimrc is a monster... It has 3986 lines.... (should I paste it ?)
in vimwiki, :verbose map <CR> (have not found weird maps)
v <CR> @<Plug>VimwikiNormalizeLinkVisualCR
Last set from ~/Git/dotfiles/.vim/vim-addons/vimwiki/src/ftplugin/vimwiki.vim
n <CR> @<Plug>VimwikiFollowLink
Last set from ~/Git/dotfiles/.vim/vim-addons/vimwiki/src/ftplugin/vimwiki.vim
Original comment by numbch...@gmail.com
on 18 May 2012 at 9:55
There is "Attach file" link
Original comment by habamax
on 18 May 2012 at 10:09
http://pastebin.com/cWZv9NLW
Original comment by numbch...@gmail.com
on 18 May 2012 at 10:32
With your vimwiki settings I am not experiencing the problem you described.
If you don't want to attach your vimrc here, then try to figure out yourself
possible vim option that might be in charge of that behaviour.
Use "binary search" :)
Continiously divide your vimrc into halves and check if the problem is there.
Original comment by habamax
on 18 May 2012 at 10:44
Thanks really .
Original comment by numbch...@gmail.com
on 18 May 2012 at 10:49
I found why now, AutoPairs.vim has an option let g:AutoPairsMapCR = 1, this
cause this error.
Original comment by numbch...@gmail.com
on 19 May 2012 at 7:28
Original comment by habamax
on 19 May 2012 at 8:34
Original issue reported on code.google.com by
numbch...@gmail.com
on 18 May 2012 at 7:29