Friday, September 7, 2012

Re: bufexplorer has conflicts with python.vim

On Fri, September 7, 2012 09:56, Tony Mechelynck wrote:
> On 07/09/12 07:28, Jürgen Krämer wrote:
>> Tony Mechelynck wrote:
>>>
>>> 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.
>>
>> the 'b' flag in 'cpoptions' could be responsible for this.
>
> Well, it might, except that the Python plugin includes
>
> let s:keepcpo= &cpo
> set cpo&vim

Here, you have your 2 lines discrepancy. I have Vim 7.4.462 and the
distributed ftplugin\python.vim file does not include those 2 lines.
This problem has recently been fixed in Revision d1e4abe8342c (see
http://code.google.com/p/vim/source/detail?spec=svn1052677493beb941eab0d1e33d63c73ee4148350&r=d1e4abe8342c4adb1890bf1833a6f41f7a310b01)

Since the OP has Vim 7.3.315, he probably does not have the latest
distributed runtime files.

So probably the missing b flag in 'cpoptions' could have cause this.


regards,
Christian

--
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: