On Thu, Jun 6, 2013 at 4:42 AM, Marek Schimara <[email protected]>wrote:
> Hello,
>
> I traced this error down to matchparen.vim plugin:
>
> Error detected while processing function <SNR>13_Highlight_Matching_Pair:
> line 59:
> E363: pattern uses more memory than 'maxmempattern'
> Press ENTER or type command to continue
>
> It's impossible to use vim as this error interrupts me all the time when
> getting around the file.
> It happens when loading a relatively small (198kB) text file containing
> port load dump from opensm (attached). I suspect the problem comes from the
> contents - the file contains mostly (about 97% lines) of text like this:
>
> [1] => IN 1106 OUT 1116
> [2] => IN 1106 OUT 1098
> [3] => IN 1106 OUT 1116
> [4] => IN 1106 OUT 1098
> [5] => IN 1106 OUT 1080
> [snip]
>
> Interestingly, I get the error also when starting vim with --noplugin, bun
> only once, and if my .vimrc contains colorscheme.
> If I comment it out, the error goes away (still with --noplugin).
> Without --noplugin, it doesn't matter if colorscheme is used or not.
>
> BUT, with --noplugin, colorcheme left out of .vimrc, then added with
> ':colorscheme chocolateliquor' once inside vim, I get no error !?? If I
> source /usr/share/vim/vim73/plugin/matchparen.vim, I get it again.
> This is getting quite confusing.
>
> So I disabled colorscheme and removed
> /usr/share/vim/vim73/plugin/matchparen.vim. Both seem necessary to get rid
> of the error...
>
> I have tried other schemes (adrian, camo, ...) with the same results.
>
>
> Thanks for any tips how to proceed.
> Marek
>
My guess is that the --noplugin/colorscheme behavior is a red herring.
If you are getting the same error message, then matchparen.vim is getting
:source'd somewhere. (You can confirm with :scriptnames). Remember, a
colorscheme file (or a syntax file ...) can contain any vim command,
including :source and :runtime.
I am pretty sure that the problem is caused by all the unmatched ">"
characters. If you try
:verbose set mps?
does it include "<:>"?
Hm, I cannot reproduce the problem while editing your file. Maybe we
have both misdiagnosed the problem ...
HTH --Benji Fisher
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
