Hello,
I expected some reaction, but havn't got any. Should I just send it to bug
tracker? Could somebody reproduce issue? Is it high priority bug to fix or low?
This issue shows itself in mason.vim that embeds perl.vim. There are not many
syntax groups in perl.vim that mix contained and not
I can act as a backup if necessary, too. I've been a bit quiet recently,
but if direct questions or a direct task were in front of me I'd be able
to help out.
Thanks for the offer. John volunteered to be the backup administrator.
Perhaps you can help mentoring students? This involves having a
Comment #1 on issue 56 by dominiqu...@gmail.com: Pressing C-R
continuously to redo changes inserts 12 character after a few redo
http://code.google.com/p/vim/issues/detail?id=56
Here is a simpler way to reproduce the bug:
1) start vim with: vim -u NONE
2) Enter following Ex command which
Comment #2 on issue 56 by br...@google.com: Pressing C-R continuously to
redo changes inserts 12 character after a few redo
http://code.google.com/p/vim/issues/detail?id=56
I cannot reproduce it.
Did you try using another terminal?
--
You received this message from the vim_dev maillist.
Do
Comment #3 on issue 56 by dominiqu...@gmail.com: Pressing C-R
continuously to redo changes inserts 12 character after a few redo
http://code.google.com/p/vim/issues/detail?id=56
Did you try using another terminal?
I just tried. It happens in gnome-terminal and xterm.
It also happens in
Guotuofeng wrote:
The full crash analyze is:
Opened log file 'd:\gvimcrash.txt'
0:000 k
ChildEBP RetAddr
003bf2e8 776af5c9 ntdll!RtlReportCriticalFailure+0x29
003bf2f8 776af6a9 ntdll!RtlpReportHeapFailure+0x21
003bf32c 7766a5cb ntdll!RtlpLogHeapFailure+0xa1
003bf374 776135a7
Hi, Bram,
Thanks for your reply. Actually, I am working in Windows and don't
have valgrind.
The crash can be easily reproed by using two plugins: NERDTree and
buf_it.
Their links are:
http://www.vim.org/scripts/script.php?script_id=1658
http://www.vim.org/scripts/script.php?script_id=2833
The
