Version : 7.4.52
Also happens on a vanilla 7.4 (without patches). I'll run it through valgrind.
Igmar
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
Op vrijdag 18 oktober 2013 14:40:29 UTC+2 schreef Igmar Palsenberg:
Version : 7.4.52
Also happens on a vanilla 7.4 (without patches). I'll run it through valgrind.
Valgrind says :
=2856== Memcheck, a memory error detector
==2856== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et
On Friday, October 18, 2013 1:57:13 AM UTC-5, Igmar Palsenberg wrote:
Hi,
I've been prepping my new vim setup, and run into a reproducable segfault.
Version : 7.4.52
Config :
All my vim stuff is on github : https://github.com/igmar/vim-dotfiles
That's also the config that triggers
Op vrijdag 18 oktober 2013 15:30:44 UTC+2 schreef Ben Fritz:
On Friday, October 18, 2013 1:57:13 AM UTC-5, Igmar Palsenberg wrote:
Hi,
I've been prepping my new vim setup, and run into a reproducable segfault.
Version : 7.4.52
Config :
All my vim stuff is on github :
On Oct 18, 2013, at 8:13, Igmar Palsenberg ig...@palsenberg.com wrote:
Version : 7.4.52
Also happens on a vanilla 7.4 (without patches). I'll run it through
valgrind.
You are able to reproduce it with an empty vimrc?
--
--
You received this message from the vim_dev maillist.
Do not
This is the patch for the bug reported by Yggdroot Chen in vim_use mailing list
(https://groups.google.com/forum/#!topic/vim_use/jR2lDzMPb9Y).
# HG changeset patch
# User ZyX kp-...@ya.ru
# Date 1382108836 -14400
# Fri Oct 18 19:07:16 2013 +0400
# Branch fix-py-vim-interrupt
# Node ID
Version : 7.4.52
Also happens on a vanilla 7.4 (without patches). I'll run it through
valgrind.
You are able to reproduce it with an empty vimrc?
No, it's a YCM issue. Sorry for wasting people's time on this.
Igmar
--
--
You received this message from the vim_dev
On Sa, 28 Sep 2013, Bram Moolenaar wrote:
Dimitar Dimitrov wrote:
Hi,
The call to histdel below doesn't seem to be doing what I want it to do.
It doesn't delete my 3 search patterns added by the 2 :substitute and
the :global calls. Not sure what it does exactly, it seems to delete
I recently discovered that the FileType autocmd can fire in the middle of the
sequence of BufRead autocmds if you have several BufRead/BufNewFile autocmds
like:
autocmd BufRead *.foo setfiletype foo
autocmd BufRead *.foo set shiftwidth=8
autocmd FileType foo set shiftwidth=4
This can