On 07/09/12 07:28, Jürgen Krämer wrote:
Hi,
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.
Regards,
Jürgen
Well, it might, except that the Python plugin includes
let s:keepcpo= &cpo
set cpo&vim
near the beginning, and
let &cpo = s:keepcpo
unlet s:keepcpo
at the very end. This is intentional, to avoid settings changed
elsewhere (e.g. in the vimrc) to cause malfunctions in this plugin; and
many other plugins do the same.
This could explain the two-line discrepancy: if someone (Tim? Björn?)
deleted these lines, that's why the plugin is malfunctioning.
Best regards,
Tony.
--
Man is the only animal that can remain on friendly terms with the
victims he intends to eat until he eats them.
-- Samuel Butler
--
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
