Thursday, September 6, 2012

Re: bufexplorer has conflicts with python.vim

* Tony Mechelynck <antoine.mechelynck@gmail.com> [120906 16:49]:
> On 06/09/12 23:41, Tim Johnson wrote:
> >
> >thanks
> >
>
> Which Vim version are you using? (I mean, it's MacVim snapshot 62, but
> which version does it display on the ":intro" screen? — I'm on Linux)
It is version 7.3.315

> In the ftplugin/python.vim included in Bram's latest official sources
> (ftplugin/python.vim "Last Change: Wed, 21 Apr 2004 13:13:08 CEST",
> Mercurial tag v7-3-659 dated Wed Sep 05 19:17:42 2012 +0200), I see two
> lines' discrepancy: the closest I come to what could trigger these
> messages is at lines 23-26, as follows:
>
> >nnoremap <silent> <buffer> ]] :call
> ><SID>Python_jump('/^\(class\\|def\)')<cr>
> >nnoremap <silent> <buffer> [[ :call
> ><SID>Python_jump('?^\(class\\|def\)')<cr>
> >nnoremap <silent> <buffer> ]m :call
> ><SID>Python_jump('/^\s*\(class\\|def\)')<cr>
> >nnoremap <silent> <buffer> [m :call
> ><SID>Python_jump('?^\s*\(class\\|def\)')<cr>
>
> but in order to trigger those errors, the | immediately before
> def\)')<cr> would have to be seen as following an ex-command, not as
> part of a single-quoted string.
>
> Does bufexplorer (which is not installed on my system) invoke these four
> commands — ]] [[ ]m [m — in the {rhs} of a mapping? Or does it define a
> map!, a cmap, an abbrev or a cabbrev with an {lhs} including something
> recognizable from the {rhs} of the above mappings?

I've been using selectbuf for many years and this occured after I
installed bufexplorer. Because I was under a timeline and needed
vim to just work, I recreated the session file that I was using.
Consequently, the problem disappeared. I also deleted my viminfo
file. I suspect that the apparent conflict was a side effect of
something incompatible from either the session file or viminfo.

:) So the problem is resolved but the mystery remains unsolved.
I have found in the past that when similarly baffling anomalies
occur that recreating session files and deleting viminfo has made
if all go away.

thanks for the reply.
--
Tim
tim at tee jay forty nine dot com or akwebsoft dot com
http://www.akwebsoft.com

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments: