VimwikiFollowLink Not working in visual mode

[GoogleCodeExporter]

Enter visual mode, and either press <CR> or +, or enter the command 
:VimwikiFollowLink.  Nothing happens.

What is the expected output? What do you see instead?

I expect the text to be turned into a wiki link. Instead, nothing happens.  
When I enter visual mode, and select a range of text, and enter the command 
manually (:VimwikiFollowLink), Vim responds with E481: No range allowed.

What version of the product are you using? On what operating system?

MacVim 7.3.315, OS X Snow Leopard

Please provide any additional information below.

I have attached my .vimrc here. Note that during troubleshooting of this issue, 
I disabled all other plugins and disabled all other key bindings.

Original issue reported on code.google.com by jgle...@gmail.com on 6 Aug 2012 at 4:53

Attachments:

• .vimrc

[GoogleCodeExporter]

Only nonline-wise visual mode is supported. Try viw to select a word and press 
CR.

Original comment by habamax on 7 Aug 2012 at 4:00

[GoogleCodeExporter]

That didn't seem to work, either. Even selecting a single word in visual mode 
(not visual line) and pressing CR does not 'wikify' the link.

Original comment by jgle...@gmail.com on 7 Aug 2012 at 4:03

[GoogleCodeExporter]

I have tried your .vimrc without vundle stuff as I don't use it and don't have 
it installed. Everything works as intended.

Could you try to install vimwiki from here, turn off vundle and check if it 
works for you?

Original comment by habamax on 8 Aug 2012 at 3:51

[GoogleCodeExporter]

Original comment by habamax on 17 Aug 2012 at 4:17

• Changed state: WontFix

[GoogleCodeExporter]

I have precisely the same issue... any idea how I can figure out what is 
interfering with vimwiki? The only way I can create/follow a link is by hitting 
enter while cursor is in a word: selecting a single word, in whatever fashion, 
fails, as does selecting more than one.

Original comment by ch...@chrislott.org on 23 Dec 2012 at 6:59

[GoogleCodeExporter]

I recall there being a way to trace execution of function calls in vim ...

Original comment by stu.andrews on 27 Dec 2012 at 4:09