Why I don't have conceal* options in my build?

Hi there. I built vim v7.4.963 from git with this configure flags: --enable-luainterp --enable-perlinterp --enable-python3interp --enable-tclinterp --enable-rubyinterp --enable-cscope --with-gnome For some reason I don't have conceal* options. `set conceallevel?` gives me a message: “E519:

Re: Why I don't have conceal* options in my build?

On Tue, Dec 8, 2015 at 10:29 AM, Viacheslav Lotsmanov wrote: > Hi there. I built vim v7.4.963 from git with this configure flags: > > --enable-luainterp --enable-perlinterp --enable-python3interp > --enable-tclinterp --enable-rubyinterp --enable-cscope --with-gnome > > For

Re: Why I don't have conceal* options in my build?

Hi Viacheslav, 2015-12-8(Tue) 18:44:33 UTC+9 Viacheslav Lotsmanov: > Hi there. I built vim v7.4.963 from git with this configure flags: > > --enable-luainterp --enable-perlinterp --enable-python3interp > --enable-tclinterp --enable-rubyinterp --enable-cscope --with-gnome > > For some reason I

Re: Why I don't have conceal* options in my build?

On 2015-12-08, Viacheslav Lotsmanov wrote: > Hi there. I built vim v7.4.963 from git with this configure flags: > > --enable-luainterp --enable-perlinterp --enable-python3interp > --enable-tclinterp --enable-rubyinterp --enable-cscope --with-gnome > > For some reason I don't have conceal*

Re: Should MatchParen plugin restore current window?

On Dec 8, 2015 14:34, "Benjamin Fritz" wrote: > > Currently the MatchParen plugin distributed with Vim, will automatically cycle through all windows with :windo, when you use the :NoMatchParen or :DoMatchParen command. > > This causes problems with (for example) the

Should MatchParen plugin restore current window?

Currently the MatchParen plugin distributed with Vim, will automatically cycle through all windows with :windo, when you use the :NoMatchParen or :DoMatchParen command. This causes problems with (for example) the LargeFile plugin from Dr. Chip, since that plugin calls NoMatchParen *prior to*

Re: Should MatchParen plugin restore current window?

Benjamin Fritz wrote: > Currently the MatchParen plugin distributed with Vim, will > automatically cycle through all windows with :windo, when you use the > :NoMatchParen or :DoMatchParen command. > > This causes problems with (for example) the LargeFile plugin from Dr. > Chip, since that plugin

Patch 866 Problem

Hello! Bram asked me to send you my small script which evokes a problem I'm having with Patch #866. To use it: vim -u NONE Hang.vim :set nocp :so % :Hang What happens: Hang sets up a remote gvim server which also sources Hang.vim. The server then gets told to call Hang#ToClient() which uses

Re: Patch 866 Problem

Hi Chip, 2015-12-9(Wed) 8:26:41 UTC+9 Charles Campbell: > Hello! > > Bram asked me to send you my small script which evokes a problem I'm > having with Patch #866. To use it: > > vim -u NONE Hang.vim > :set nocp > :so % > :Hang > > What happens: Hang sets up a remote gvim server which also

Re: test_cdo fails when using another language

Kenichi Ito wrote: > Hi list, > > test_cdo fails like this. > 15c15 > < Unsaved file change test failed > --- > > Unsaved file change test passed > 48c48 > < Unsaved file change test failed > --- > > Unsaved file change test passed > > > This patch fixes it. Thanks! -- hundred-and-one

Re: Should MatchParen plugin restore current window?

On Tuesday, December 8, 2015 at 2:26:06 PM UTC-6, DrChip wrote: > I glanced at LargeFile (v7c) -- its already saving the current window > and jumping back to it Well thanks for pointing that out...I had been using the version from vim.org which is a couple years old. Hopefully that solves my

Re: Should MatchParen plugin restore current window?

On Tue, Dec 8, 2015 at 4:15 PM, Ben Fritz wrote: > On Tuesday, December 8, 2015 at 2:26:06 PM UTC-6, DrChip wrote: >> I glanced at LargeFile (v7c) -- its already saving the current window >> and jumping back to it > > Well thanks for pointing that out...I had been using