Closed GoogleCodeExporter closed 9 years ago
I was not even aware of this option...
Can you easily check this on some other platform (e.g. Windows)? It sounds
like a bug in core Vim to me, but I'm not sure.
Original comment by bjorn.winckler@gmail.com
on 4 Dec 2012 at 5:25
I have checked this on vim provided by the system (7.2.108) and it works well.
I tryed on linux, it also works well with vim and gvim, with versions 7.2.330
and 7.3.429.
Actually, I tryed with Macvim's Vim command inside terminal, and i was not even
able to use mouse wheel ( yes, 'mouse' option is set to 'a' ). I only run into
this issue with MacVim
Original comment by nicola...@gmail.com
on 5 Dec 2012 at 1:22
Thanks for testing on other platforms. I'll put a note on my todo list to have
a look at the problem.
Original comment by bjorn.winckler@gmail.com
on 5 Dec 2012 at 8:23
Hmm. I just had a look and can not reproduce the problem after going through
your steps. It sounds like you may have some plugins that are interfering.
Original comment by bjorn.winckler@gmail.com
on 5 Dec 2012 at 8:32
Right ... I removed all my plugins for the tests, but a forgot to clean my
vimrc. There was a 'set rtp+=~/src/vim-eclim/', responsible of this issue.
After having re-enabled my plugins, the issue was back, because of
CuteErrorMarkers.
Sorry for the noise.
Original comment by nicola...@gmail.com
on 6 Dec 2012 at 8:43
After more investigations, i can update the steps to reproduce the problem :
the issue is encountered when the option &ballooneval is enabled :
:set ballooneval
:au CursorHold * echo reltime()
I tested these steps against gvim ( 7.2.330 and 7.3.429 ), and it is working
well. This issue only occur in MacVim.
Original comment by nicola...@gmail.com
on 6 Dec 2012 at 9:15
I can see the problem and have pushed a fix [1]. Thanks for your help
debugging this issue!
[1]
https://github.com/b4winckler/macvim/commit/965313f743b63cc1287c23f7473902a7721e
4b0d
Original comment by bjorn.winckler@gmail.com
on 8 Dec 2012 at 1:59
Original comment by bjorn.winckler@gmail.com
on 9 Jun 2013 at 2:07
Original issue reported on code.google.com by
nicola...@gmail.com
on 28 Nov 2012 at 9:33