Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

2016-01-08 Fir de Conversatie Christian Brabandt
Hi Justin! On Fr, 08 Jan 2016, Justin M. Keyes wrote: > Instead of requiring , the default behavior could be changed. > Can anyone give a single reason why the old behavior is desirable or > useful, or necessary for backwards compatibility? > > Ben mentioned that the existing behavior gives the

question about expression mappings

2016-01-08 Fir de Conversatie Christian Brabandt
Hi, I think I found an inconsistency. #v+ vim -u NONE -N :let @a='foobar' :fu AB() return "a" :endfu :fu CD() return "\a" :endfu :imap ab 'a' :imap cd AB() :imap ef CD() #v- Now enter insert mode: 1) Inserting ab results in: foobar 2) Inserting cd results in: a 3) Inserting ef

Suggestion for "has" blowfish detection

2016-01-08 Fir de Conversatie smu johnson
Dear Vim Mailing List, I wanted to quickly suggest the idea of has('blowfish') support for Vim. It would make my .vimrc a bit more legible to prevent < 7.3 version errors when trying to execute the command: "set cryptmethod=blowfish" inside of it. Just a thought. -- smu johnson

Re: question about expression mappings

2016-01-08 Fir de Conversatie Nikolay Aleksandrovich Pavlov
2016-01-09 0:53 GMT+03:00 Christian Brabandt : > Hi, > I think I found an inconsistency. > > #v+ > vim -u NONE -N > :let @a='foobar' > :fu AB() > return "a" > :endfu > :fu CD() > return "\a" > :endfu > :imap ab 'a' > :imap cd AB() > :imap ef CD() > #v- > Now enter

Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

2016-01-08 Fir de Conversatie Justin M. Keyes
On Fri, Jan 8, 2016 at 12:15 PM, Charles E Campbell wrote: > Ben Fritz wrote: >> On Friday, January 8, 2016 at 2:33:04 AM UTC-6, Christian Brabandt wrote: >>> Having said that, I personally don't like the argument as >>> well. Perhaps we could use a new command

Re: Update to vim CMake syntax files

2016-01-08 Fir de Conversatie Justin M. Keyes
On Fri, Jan 8, 2016 at 9:09 AM, Dimitri Merejkowsky wrote: >> >> There also is no ftplugin for cmake, so the 'commentstring' is wrong. >> It should be: >> >> setlocal commentstring=#\ %s >> > You mean I have to add an other line ? Or do I need to add a ftplugin for > cmake ? >

[if_perl][patch] Improve I/O integration

2016-01-08 Fir de Conversatie Damien
Hi list, Actually, Perl users cannot use 'print' operator for wrinting directly in standard IO witch embed perl interpreter. The attached patch add a minimal implementation of PerlIO Layer feature and try to use it for STDOUT/STDERR. Please check it. Regards, Damien -- -- You received this

Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

2016-01-08 Fir de Conversatie Christian Brabandt
Hi Charles! On Fr, 08 Jan 2016, Charles E Campbell wrote: > Ben Fritz wrote: > > On Friday, January 8, 2016 at 2:33:04 AM UTC-6, Christian Brabandt wrote: > >> Having said that, I personally don't like the argument as > >> well. Perhaps we could use a new command modifier like > >> :keeppos

Re: Patch 7.4.1051

2016-01-08 Fir de Conversatie Olaf Dabrunz
Dominique, thanks for catching this. This was caused by my patch, sorry. The problem is that backwards compatible versions of v: variables are not handled properly (VV_COMPAT variables in vimvars). These are: count errmsg shell_error this_session version For some, the code

Re: Updating runtime files without version control

2016-01-08 Fir de Conversatie Ken Takata
Hi Bram and all, 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote: > Can we please gather the complete, step-by-step instructions? Probably > the best place for this is src/INSTALLpc.txt. I wrote it. Please review. I also updated the appveyor script:

Re: [patch][doc] how to use the help

2016-01-08 Fir de Conversatie Christian Brabandt
And this time with an actual attachment. On Fr, 08 Jan 2016, Christian Brabandt wrote: > Bram, > here is a patch, that documents, how to use the help. I have written > down this in the vim-use ml and thought it would be useful to have in > the help itself. > >

[patch][doc] how to use the help

2016-01-08 Fir de Conversatie Christian Brabandt
Bram, here is a patch, that documents, how to use the help. I have written down this in the vim-use ml and thought it would be useful to have in the help itself. https://groups.google.com/d/msg/vim_use/2ZKTBdhsBC4/hETpTMnEAQAJ https://groups.google.com/d/msg/vim_use/2ZKTBdhsBC4/uaDrb15LAgAJ

Re: Update to vim CMake syntax files

2016-01-08 Fir de Conversatie Dimitri Merejkowsky
> > > There also is no ftplugin for cmake, so the 'commentstring' is wrong. > It should be: > > setlocal commentstring=#\ %s > > You mean I have to add an other line ? Or do I need to add a ftplugin for cmake ? I don't see the string 'commentstring' in the 'syntax/cmake.vim' file -- -- You

Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

2016-01-08 Fir de Conversatie Ben Fritz
On Friday, January 8, 2016 at 2:33:04 AM UTC-6, Christian Brabandt wrote: > > Having said that, I personally don't like the argument as > well. Perhaps we could use a new command modifier like > :keeppos windo ... > > That could be useful for other commands as well. > I like that idea better

Re: [bug] error E201 when opening 3 large files with -o option when using LargeFile plugin

2016-01-08 Fir de Conversatie Charles E Campbell
Ben Fritz wrote: > On Friday, January 8, 2016 at 2:33:04 AM UTC-6, Christian Brabandt wrote: >> Having said that, I personally don't like the argument as >> well. Perhaps we could use a new command modifier like >> :keeppos windo ... >> >> That could be useful for other commands as well. >> > I