I have a text file that when I open it, vim prints.. E363: pattern uses more memory than 'maxmempattern' I'd attach an example, but that file contains usernames and passwords. I tried narrowing it down to an area of the file by using head -n150 / tail -n150 (It's ~300 lines long) and that made the bug go away. Removing the .txt from the filename works around it. File is formatted like: websitename<tab>username<tab>password I used awk to print out just one column at a time and generate a file for each. They load fine. Columns 1+2 loads fine. Columns 2+3 load fine. It's just the combination of everything that seems to upset it. This just started happening with the recent update to F18's vim. vim-enhanced-7.3.712-1.fc18.x86_64
Created attachment 736599 [details] log file from libreswan test suite log file that when opened with vim triggers the error: E363: pattern uses more memory than 'maxmempattern'
ping?
vim-7.3.944-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/vim-7.3.944-1.fc18
Opening west.console.verbose.txt with vim from vim-enhanced-7.3.712-1.fc18.x86_64 doesn't produce that error message on my system, so I have to rely on you to confirm if vim-7.3.944-1.fc18 from updates-testing fixes this issue.
vim-7.3.944-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/vim-7.3.944-1.fc19
I can reproduce this on one machine now and this is caused by the matchparen.vim plugin that highlights matching brackets when the cursor is on one of them. Workarounds so far: :set matchpairs= or :set maxmempattern=5000 or vim --cmd "set maxmempattern=5000" west.console.verbose.txt
Package vim-7.3.944-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing vim-7.3.944-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8213/vim-7.3.944-1.fc18 then log in and leave karma (feedback).
As the vim update didn't fix this, I've spent some more time on it and tracked it down to the asciidoc package. Remove it and it'll work without any errors. These two lines in /usr/share/vim/vimfiles/syntax/asciidoc.vim are causing this: syn match asciidocEntityRef /\\\@<!&[#a-zA-Z]\S\{-};/ syn match asciidocQuotedEmphasized /\(^\|[| \t([.,=\]]\)\@<=_\([ )\n\t]\)\@!\(.\|\n\(\s*\n\)\@!\)\{-}\S\(_\([| \t)[\],.?!;:=]\|$\)\@=\)/ contains=asciidocEntityRef I've already asked the vim maintainer if he has an idea on how to optimize these lines. Reassigning to asciidoc now...
yay! that indeed works around the problem for me! Thanks!
vim-7.3.944-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
The asciidoc syntax highlighting is really aggravating since it's *really* slow in files with long lines or that aren't asciidoc. In the ftdetect/asciidoc_filetype.vim file, can the following lines be switched out for the other (comment the first, use the second)? au BufNewFile,BufRead *.asciidoc,*.txt,README,TODO,CHANGELOG,NOTES setfiletype asciidoc "au BufRead *.txt,README,TODO,CHANGELOG,NOTES call s:FTasciidoc() I've let upstream know, but they've been unresponsive[1]. [1]http://article.gmane.org/gmane.text.formats.asciidoc/4701
Accidentally hit it too; fixed by using maxmempattern=5000 as per [comment 6]. Temporarily switching filetype might also help. Vim behaved ridiculously as it started when I tried to move up within the opened text file and encountered the line starting with "[". And agains when I hit another one few lines higher.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.