Re: 0wincmd gives E16: Invalid range: 0wincmd w

[David Fishburn]

On Mon, Jan 12, 2015 at 9:52 AM, Enno  wrote:

> Le lundi 12 janvier 2015 14:41:00 UTC+1, Bram Moolenaar a écrit :
> > Enno Nagel wrote:
> >
> > > The command
> > >
> > > 0wincmd w
> > >
> > > throws an error in the latest Vim version:
> > >
> > > E16: Invalid range: 0wincmd w
> > >
> > > Before, it simply stayed in the same window.
> > > Is this a new feature or a bug?
> >
> > There is no window with the number zero, so the error is correct.
> >
> > Is this breaking some plugin?
> >
> > --
> > hundred-and-one symptoms of being an internet addict:
> > 74. Your most erotic dreams are about cybersex
> >
> >  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> > \\\  an exciting new programming language -- http://www.Zimbu.org
>   ///
> >  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> Well I have a plugin FastFold https://github.com/Konfekt/FastFold that
> uses a WinDo command that restores the current and alternate window by
>
> let curaltwin = winnr('#')
> let currwin=winnr()
> execute 'windo ' . a:command
> execute curaltwin . 'wincmd w'
> execute currwin . 'wincmd w'
>
> This used to work fine even if there was no alternate window before, but
> now there appear issue (https://github.com/Konfekt/FastFold/issues/11 and
> https://github.com/Konfekt/FastFold/issues/12) about
>
> :0wincmd w
>
> throwing an error.
>
> Perhaps it used to be that
>
> winnr('#')
>
> returned the current window number if there is no alternate window.
>
>
> When I use "gt" to switch tabs (or click on a different tab) the TagBar
plugin (http://vim.sourceforge.net/script.php?script_id=3465) reports this
error:

Error detected while processing function
99_QuitIfOnlyWindow..99_goto_win:
line8:
E16: Invalid range: 0wincmd w

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] add watch function to vim debugger

[David Fishburn]

While we are on some features for the debugger can I suggest one (or tell
me how to enable it if already there).

While debugging my plugins I generally have some terrific print statements
as I step through code.

If I have to restart Vim I loose all the debugger history of those
beautiful echo statements.

Is there anyway to maintain and cycle through the history just like I can
with the search history and cmd history?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Icon for Windows.

[David Fishburn]

>
> ...



> This icon looks much better in modern Windows, and simply reuses artwork
> already available for the Mac build. The last icon is derivative work by
> me, using the outlines of the original 16x16 icon and coloured to the 32bpp
> icon.
>
> Is there any chance of making it into the official build?
>
> Hope so, it looks nice.

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

E887: Sorry, this command is disabled, the Python's site module could not be loaded.

[David Fishburn]

I am trying to get Vim running with Python (I know nothing about Python).

I have gVim working with a dynamically loaded Perl.

I compile my own 32-bit Vim on Windows 7 64-bit.

D:\>python --version
Python 2.7

D:\>python
Python 2.7 (r27:82525, Jul  4 2010, 09:01:59) [MSC v.1500 32 bit (Intel)]
on win 32
Type "help", "copyright", "credits" or "license" for more information.
>>>

D:\>which python
d:\python27\python.EXE



C:\OpenSrc\vim>"C:\Program Files\Mercurial\hg.exe" pull
pulling from https://vim.googlecode.com/hg/
searching for changes
adding changesets
adding manifests
adding file changes
added 35 changesets with 77 changes to 39 files
(run 'hg update' to get a working copy)

C:\OpenSrc\vim>"C:\Program Files\Mercurial\hg.exe" update
39 files updated, 0 files merged, 0 files removed, 0 files unresolved



I compile it the same way I compile with Perl:


***

IF NOT DEFINED VIM_PYTHON_VER SET VIM_PYTHON_VER=27
IF NOT DEFINED VIM_PYTHON_DIR SET VIM_PYTHON_DIR=D:\Python27
IF NOT DEFINED VIM_PERL_VER SET VIM_PERL_VER=516
IF NOT DEFINED VIM_PERL_DIR SET VIM_PERL_DIR=C:\Perl

nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes FEATURES=HUGE
PYTHON=%VIM_PYTHON_DIR% DYNAMIC_PYTHON=yes PYTHON_VER=%VIM_PYTHON_VER%
PERL=%VIM_PERL_DIR% DYNAMIC_PERL=yes PERL_VER=%VIM_PERL_VER%
XPM=%VIM_XPM_DIR%

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation.  All rights reserved.

Python requested (version 27) - root dir is "D:\Python27"
Python DLL will be loaded dynamically
Perl requested (version 516) - root dir is "C:\Perl"
Perl DLL will be loaded dynamically

...

  100%   0 seconds remaining
Finished generating code
if exist gvim.exe.manifest mt.exe -nologo -manifest
gvim.exe.manifest -u
pdateresource:gvim.exe;1
cl /nologo -DNDEBUG vimrun.c
vimrun.c
cl /nologo -DNDEBUG -DWIN32 dosinst.c kernel32.lib shell32.lib
 user32.l
ib ole32.lib advapi32.lib uuid.lib
dosinst.c
if exist install.exe del install.exe
ren dosinst.exe install.exe
cl /nologo -DNDEBUG -DWIN32 uninstal.c shell32.lib advapi32.lib
uninstal.c
cd xxd
"C:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\BIN\nmake.exe" /
NOLOGO -f Make_mvc.mak
cl /nologo -DWIN32 xxd.c
xxd.c
cd ..
cd GvimExt
"C:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\BIN\nmake.exe" /
NOLOGO -f Makefile
cl -c -DCRTAPI1=_cdecl -DCRTAPI2=_cdecl -nologo -GS -D_X86_=1
 -DWIN32 -
D_WIN32 -W3 -D_WIN32_IE=0x0400 -DWINVER=0x0400 -DFEAT_GETTEXT  -D_MT -MT
gvimext
.cpp
gvimext.cpp
Rc /r -DWIN32 -D_WIN32 -DWINVER=0x0400   gvimext.rc
Microsoft (R) Windows (R) Resource Compiler Version 6.1.7600.16385
Copyright (C) Microsoft Corporation.  All rights reserved.

link  /INCREMENTAL:NO /NOLOGO -dll -def:gvimext.def
-base:0x1C00 -ou
t:gvimext.dll gvimext.obj gvimext.res ole32.lib uuid.lib oleaut32.lib
kernel32.l
ib  ws2_32.lib mswsock.lib advapi32.lib user32.lib gdi32.lib comdlg32.lib
winspo
ol.lib shell32.lib comctl32.lib
   Creating library gvimext.lib and object gvimext.exp
if exist gvimext.dll.manifest mt -nologo -manifest
gvimext.dll.manifest
-outputresource:gvimext.dll;2
cd ..

***

I don't see any errors listed while compiling.



:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr  6 2015 14:30:21)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-691
Compiled by me@myDomain
Huge version with GUI.  Features included (+) or not (-):
+acl +clipboard   +cursorshape +ex_extra
 -hangul_input+listcmds+multi_lang  +profile
+smartindent -tcl +visual  -xim
+arabic  +cmdline_compl   +dialog_con_gui  +extra_search
 +iconv/dyn   +localmap-mzscheme+python/dyn  -sniff
  -tgetent +visualextra -xterm_save
+autocmd +cmdline_hist+diff+farsi
+insert_expand   -lua +netbeans_intg   -python3
+startuptime -termresponse+viminfo +xpm_w32
+balloon_eval+cmdline_info+digraphs+file_in_path
 +jumplist+menu+ole +quickfix
 +statusline  +textobjects +vreplace
+browse  +comments-directx +find_in_path+keymap
 +mksession   +path_extra  +reltime -sun_workshop
 +title   +wildignore
++builtin_terms  +conceal -dnd +float
+langmap +modify_fname+perl/dyn+rightleft   +syntax
 +toolbar +wildmenu
+byte_offset +cryptv  -ebcdic  +folding
+libcall +mouse   +persistent_undo -ruby
 +tag_binary  +user_commands   +windows
+cindent +cscope  +emacs_tags  -footer
 +linebreak   +mouseshape  -postscript  +scrollbind
 +tag_old_static  +vertsplit   +writebackup
+clientserver+cursorbind  +eval+gettext/dyn
+lispinde

Re: E887: Sorry, this command is disabled, the Python's site module could not be loaded.

[David Fishburn]

On Tue, Apr 7, 2015 at 12:43 AM, Yukihiro Nakadaira <
yukihiro.nakada...@gmail.com> wrote:

> On Tue, Apr 7, 2015 at 3:38 AM, David Fishburn 
> wrote:
>
>> :echo has('perl') has('python') has('python3')
>> 1 1 0
>>
>> :python print 'anything'
>> E887: Sorry, this command is disabled, the Python's site module could not
>> be loaded.
>>
>>
>>
>> I have found only 1 reference to this error in vim_use or vim_dev:
>>
>>
>> https://groups.google.com/forum/#!searchin/vim_dev/the$20Python$27s$20site$20module$20could$20not$20be$20loaded/vim_dev/d4Iz0vdPJ48/HZzSJ-fVTOcJ
>>
>> Which is this:
>>
>> Patch 7.4.380
>> Problem:Loading python may cause Vim to exit.
>> Solution:   Avoid loading the "site" module. (Taro Muraoka)
>> Files:src/if_python.c
>>
>>
>> Does anyone know what I might be doing wrong?
>>
>
> Check result of "where python27.dll" in command prompt.
> I guess that Mercurial's python27.dll is found before Python's
> python27.dll.
>


I have tried:

PYTHON_HOME=D:\Python27


D:\>SET PY
PYTHON_HOME=D:\Python27

D:\>dir %PYTHON_HOME%
 Volume in drive D is D
 Volume Serial Number is FC7C-B353

 Directory of D:\Python27

07/04/2015  07:58 AM  DLLs
18/07/2014  04:43 PM  Doc
18/07/2014  04:43 PM  include
06/04/2015  10:54 AM  Lib
18/07/2014  04:44 PM  libs
18/07/2014  04:44 PM  Scripts
18/07/2014  04:44 PM  tcl
18/07/2014  04:44 PM  Tools
...
04/07/2010  09:03 AM26,624 python.exe
04/07/2010  09:04 AM27,136 pythonw.exe
04/07/2010  07:32 AM54,958 README.txt
04/07/2010  09:01 AM49,664 w9xpopen.exe
   6 File(s)438,119 bytes
  10 Dir(s)  174,812,467,200 bytes free

D:\>gvim

:python print 'anything'
E887: Sorry, this command is disabled, the Python's site module could not
be loaded.


D:\>where python27.dll
C:\Windows\System32\python27.dll
C:\Program Files\Mercurial\python27.dll

Using Explorer and checking properties on C:\Windows\System32\python27.dll
I see file Version:
2.7.3150.1013

The C:\Program Files\Mercurial\python27.dll has a file version of:
2.7.4150.1013



Trying this:

D:\>SET PATH=C:\Program Files\Mercurial;%PATH%
D:\>gvim

:python print 'anything'
E887: Sorry, this command is disabled, the Python's site module could not
be loaded.



Any other suggestions?

TIA,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: E887: Sorry, this command is disabled, the Python's site module could not be loaded.

[David Fishburn]

On Tue, Apr 7, 2015 at 4:51 PM, Ben Fritz  wrote:

> One sanity check, from within Vim, make sure your python paths match what
> you expect from your earlier test in your shell:
>
> :!where python27.dll
>
> Next step, maybe install a more recent python?
>
> Yours just shows "Python 2.7" whereas mine (which has been working fine
> for a long time) shows "Python 2.7.6". I think the 2.7.x series is supposed
> to maintain backwards compatibility with any other 2.7.x version, unlike
> Python 3.
>


I have it working now, Ben your suggestion of updating my 2.7 version seems
to have worked.  I upgraded to 2.7.9.

I had some incorrect information above:

On 64-bit Windows, 32-bit DLLs are installed in C:\Windows\SysWOW64, not
C:\Windows\System32

C:\Windows\SysWOW64\python27.dll
Shows a file version of: 2.7.9150.1013
Shows a product version of: 2.7.9

I recompiled my Vim just in case:

:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr  8 2015 09:09:46)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-691

:python print 'anything'
anything

:echo has('perl') has('python') has('python3')
1 1 0


Thanks everyone for the responses, much appreciated.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Neovim changes

[David Fishburn]

>
>
>

> Crashing is not good, no matter what the reason.
> An editor should never crash, even when the user does something stupid.
>
>
+1

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Visual Studio 12.0 win32.mak not found

[David Fishburn]

New machine, a newer installation of VS.


> "C:\Program Files\Mercurial\hg.exe" pull
pulling from https://vim.googlecode.com/hg/
searching for changes
no changes found


> "C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\Tools\vsvars32.bat"


> nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes FEATURES=HUGE
PYTHON=C:\Python27 DYNAMIC_PYTHON=yes PYTHON_VER=27 PERL=C:\Perl
DYNAMIC_PERL=yes PERL_VER=516 XPM=xpm\x86 clean

Microsoft (R) Program Maintenance Utility Version 12.00.21005.1
Copyright (C) Microsoft Corporation.  All rights reserved.

Make_mvc.mak(247) : fatal error U1052: file 'Win32.mak' not found
Stop.



Any ideas, the only ones I found in Google was this patch:
Patch 7.4.183

Patch 7.4.183
Problem:MSVC Visual Studio update not supported.
Solution:   Add version number. (Mike William)
Files:src/Make_mvc.mak


> cat vim/src/version.c

static int included_patches[] =
{   /* Add new patch number below this line */
/**/
729,
/**/
728,

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Visual Studio 12.0 win32.mak not found

[David Fishburn]

>
> ...



> set INCLUDE=%INCLUDE%;c:\Program Files (x86)\Microsoft
> SDKs\Windows\v7.1A\Include
>
> or just copy the file over to c:\Program Files (x86)\Microsoft Visual
> Studio 12.0\VC\include
>
> Perfect thanks Andrei.

I will add the INCLUDE to my .cmd file which I use to build it.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Heading for a release

[David Fishburn]

I have a couple of runtime files to update as well.
How soon do you need them?

On Thu, Oct 24, 2019 at 4:13 PM Bram Moolenaar  wrote:

>
> Christian wrote:
>
> > On Do, 24 Okt 2019, Bram Moolenaar wrote:
> >
> > > It's unlikely new strings get added.  Existing strings might still get
> > > fixes, but there should not be that many.
> >
> > Okay, here is an updated de.po file then.
>
> I'll include it, thanks.
>
> > Will also send out updated runtime files soon.
>
> Good.
>
> --
> I once paid $12 to peer at the box that held King Tutankhamen's little
> bandage-covered midget corpse at the De Young Museum in San Francisco.  I
> remember thinking how pleased he'd be about the way things turned out in
> his
> afterlife.
> (Scott Adams - The Dilbert principle)
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
>  \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org
> ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/201910242013.x9OKDoom027242%40masaka.moolenaar.net
> .
>

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAJ_EjQjEw1F66cKbBD88Lb8W0Yw%2BH%3DiVkJYyHoU_GnCHNJXksA%40mail.gmail.com.

Re: Patch 8.0.0275

[David Fishburn]

On Tue, Apr 25, 2017 at 4:19 AM, Christian Brabandt 
wrote:

> Hi vim_dev!
>
> On Sa, 22 Apr 2017, Christian Brabandt wrote:
>
> > On Sa, 22 Apr 2017, Bram Moolenaar wrote:
> >
> > > We do need to append a NUL to key_name!
> >
> > Thanks for fixing this for me. I somehow thought it would be initialized
> > with NUL.
>
> Strangely now the simalt command still does not work. Can other people
> still reproduce the issue or is this fixed for them?
>
>
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr  5 2017 08:20:27)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-543

I just ran:
:simalt f

Worked fine on my Windows 10 box.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BUG] Put contents of dot register in visual mode

[David Fishburn]

>
> ...
>


> > In the following code snippet I'm trying to replace parameter name from
> param to value, using dot register (last inserted text):
> >
> > function execute(param){
> >   var result = param.paramProcessing();
> >
> > 1. I place the cursor on the in first occurence of param (in the
> brackets)
> > 2. I type `ciwvalue` to replace param with value, and move value
> into dot register
> > 3. I go to second param occurence
> > 4. I type `viw".p` to select param, and replace it with value
> >
> > As you can see during reproduction, step #4 instead of word replacement,
> causes removal of word 'param', and leaves me in visual mode.
>
>
I can't for the life of me find this now, but I think I have run into this
same problem before.  It really annoys me and someone (thought it was
Christian) pointed out there is an option to control this behaviour.

Basically when you visually select text, and then paste over it, the
visually selected text (which was just replaced) is moved into the default
register.  I personally don't want the default register changed, as I want
to continue pasting it in other spots.

There is an option to turn it off, but after 15 minutes of looking I can't
find it.
I thought it was cpoptions or guioptions, but my search and tests were
fruitless.

Does this stir anyone's memory?

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BUG] Put contents of dot register in visual mode

[David Fishburn]

On Thu, Feb 18, 2016 at 10:48 AM, Christian Brabandt 
wrote:

> ...
>
> I can't for the life of me find this now, but I think I have run into
> this same
> > problem before.  It really annoys me and someone (thought it was
> Christian)
> > pointed out there is an option to control this behaviour.
> >
> > Basically when you visually select text, and then paste over it, the
> visually
> > selected text (which was just replaced) is moved into the default
> register.  I
> > personally don't want the default register changed, as I want to continue
> > pasting it in other spots.
> >
> ...
> Hm, I think it is the 'a' flag in the guioptions possibly in combination
> with 'unnamedplus' value in the clipboard setting.
>
>
This also happens when using vim (instead of gvim) so it can't be any of
the guioptions.

So I was looking around through the help and found this reference which
explains it:

*put-Visual-mode* *v_p* *v_P*
When using a put command like |p| or |P| in Visual mode, Vim will try to
replace the selected text with the contents of the register.  Whether this
works well depends on the type of selection and the type of the text in the
register.  With blockwise selection it also depends on the size of the block
and whether the corners are on an existing character.  (Implementation
detail:
it actually works by first putting the register after the selection and then
deleting the selection.)
The previously selected text is put in the unnamed register.  If you want to
put the same text into a Visual selection several times you need to use
another register.  E.g., yank the text to copy, Visually select the text to
replace and use "0p .  You can repeat this as many times as you like, the
unnamed register will be changed each time.


So, if you want to continue pasting the original text you have to use "0p
(which works).

Thanks for the response Christian.

Dave

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] add skip-expression to search() function

[David Fishburn]

On Wed, Feb 24, 2016 at 3:13 PM, Christian Brabandt  wrote:

> Hi,
> attached patch, enables skip expressions similar to what searchpairpos()
> already does for search() and searchpos() functions. Patch includes
> updated documentation and an updated test.
>
> I think this is useful, so you can search for e.g. "pattern" only in
> syntax group "Comment" or the other way around. Currently there is no
> way to do that, other than making a loop and manually checking each
> match.
>
>
I had to write a plugin to do this which goes a word at a time and checks
the synID, so this would be useful.

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Vim 7.5 or Vim 8?

[David Fishburn]

Vim 8.0 for me.

I think the possible changes to the plugins with the new features could
make a very big difference.

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GitHub vim scripts - duplicate of vim.org

[David Fishburn]

I notice all the vim script on vim.org seem to be duplicated under:
https://github.com/vim-scripts

Is this something Vim has done, or is this an independent process?

The reason I ask, is there are lots of comments and pull requests against
my plugins.  Given I do not own that account, all I can do is comment on
the site, rather than accept pulls and close issues and so on.

I am relatively new to GitHub, is there a process other people follow that
makes sense to deal with a community forming around this?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Add SQL comment highlighting (#3983)

[David Fishburn]

What database are you connecting to?

Vim out of the box supports many different syntax files for different
vendors databases.

C:\Vim\vim81\syntax>dir *sql*
09/02/2016  07:10 AM 2,094 esqlc.vim
09/02/2016  07:10 AM 2,390 msql.vim
09/02/2016  07:10 AM17,609 mysql.vim
09/02/2016  07:10 AM12,918 plsql.vim
09/02/2016  07:10 AM 1,120 sql.vim
09/02/2016  07:10 AM41,929 sqlanywhere.vim
09/02/2016  07:10 AM 6,734 sqlforms.vim
09/02/2016  07:10 AM11,027 sqlhana.vim
09/02/2016  07:10 AM 5,901 sqlinformix.vim
09/02/2016  07:10 AM 2,970 sqlj.vim
07/10/2018  11:10 AM 7,649 sqloracle.vim

For example, I use SQL Anywhere as my main database, not Oracle which is
the default syntax file for a SQL filetype.

If you try this:
:h ft_sql.txt

It will explain to you how Vim handles different types of databases.

For example, in my .vimrc I have this line:
let g:sql_type_default = 'sqlanywhere'

Which tells Vim to load the syntax/sqlanywhere.vim file instead of the
Oracle one for a .sql file.

You also can run:
:SQLSetType 
:SQLSetType sqlinformix.sql
:SQLSetType mysql.sql

So back to your initial question, if for example MySQL supports the # sign
as a comment marker, then the syntax/mysql.vim will most likely support and
set that up for you.
So, if you are 90% of the time connecting and using a MySQL database, you
should do this in your .vimrc:
let g:sql_type_default = 'mysql'

HTH,
David


On Sat, Feb 16, 2019 at 7:44 PM Frank Greico 
wrote:

> Currently when editing a .sql file with vim only C-Style comments get
> highlighted as a comment /* like this */ But not the one line style. # like
> this. Please added the same color of highlighting to the one line style.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> 
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How about a release?

[David Fishburn]

On Thu, Mar 8, 2018 at 5:16 PM, Christian Brabandt 
wrote:

>
> Oh and I think perhaps including the background make plugin would make
> sense for a new release.
>
>
> I have been using Dispatch.vim (Tim Pope) for this:
https://www.vim.org/scripts/script.php?script_id=4504

Is the make plugin different from this?

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Debug history in viminfo

[David Fishburn]

Does anyone know how hard it would be to add the debug command lines into
the viminfo so that they are preserved between Vim restarts?


The repeat.txt indicates this:

There is a separate command-line history for debug mode.

Which is true, I use it immensely when testing.

And viminfo:
The viminfo file is used to store:
- The command line history.
- The search string history.
- The input-line history.
- Contents of non-empty registers.
- Marks for several files.
- File marks, pointing to locations in files.
- Last search/substitute pattern (for 'n' and '&').
- The buffer list.
- Global variables.

It would be great to have:
- The command line history.
- The search string history.
- The input-line history.
* - The debug history. *

I unfortunately do not do anything with Vim source, only writing plugins.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How about a release?

[David Fishburn]

>
> > >> Oh and I think perhaps including the background make plugin would make
> > >> sense for a new release.
> > >>
> > > I have been using Dispatch.vim (Tim Pope) for this:
> > > https://www.vim.org/scripts/script.php?script_id=4504
> > >
> > > Is the make plugin different from this?
> > >
> >
> > I have uploaded the asyncmake plugin to github:
> >
> > https://github.com/yegappan/asyncmake
> >
> > The plugin starts the program set in 'makeprg' in the background. The
> > output from the make command is parsed and added to the quickfix list in
> > the background. It doesn't wait for the make command to complete, the
> > output is added to the quickfix list as it becomes available. It also
> > avoids using a quickfix list created by other plugins or the user. This
> > plugin relies on the new quickfix features added upto Vim 8.0.1040.
>
> Considering how active Yegappan has been making all of this work, I tend
> to think his plugin would be the best.  But let's hear from actual
> users.
>
>
> I have downloaded and installed it, will give it a whirl.

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please change the default for 'wildmode'

[David Fishburn]

 > What do others think?

I haven't tried the options to figure out what they do, so I will simply
describe what I like.

In bash it drives me insane when I hit Tab and it only stops at the match
and makes me type another character just to further complete.

I want:
1.  Tab to show the full file name
2.  I want to be able to cycle through those names each time I hit tab
3.  I want the status bar to show the matches, so I know (usually) how many
times I have to hit tab

I get that already from my current settings, which seem to be just:
:set wildmenu  (on Windows)

Dave

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] ctrl-c in insert mode in *.sql files wouldn't issue exit of the insert mode (Issue #12248)

[David Fishburn]

> The choice of CTRL-C as the default complete key was unfortunate. We
can't change it now without upsetting users who have gotten used to it. You
can change it by setting a variable, see ":help sql-completion-static".

Agreed Bram.

So many of the keys are already taken in Vim for various functions, I chose
this as primarily a Windows user, which worked just fine.

But as you point out, I made it as an option to be overridden by the user.

:help sql-completion-static".

The use of "" can be user chosen by using the following in your
|.vimrc|
as it may not work properly on all platforms: >
let g:ftplugin_sql_omni_key = ''

David



On Sat, Apr 15, 2023 at 4:18 PM Bram Moolenaar 
wrote:

> The choice of CTRL-C as the default completly key was unfortunate. We
> can't change it now without upsetting users who have gotten used to it. You
> can change it by setting a variable, see ":help sql-completion-static".
>
> —
> Reply to this email directly, view it on GitHub
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: 
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/12248/1509952344%40github.com
> 
> .
>

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAJ_EjQj6WeP0Z3e%3DGgLa1p2_SKMdmRqH7noOw8%3DPq7NqSDjmGg%40mail.gmail.com.

Re: 7.4a - Confirm dialog box larger than screen size

[David Fishburn]

On Thu, Aug 1, 2013 at 7:23 AM, Bram Moolenaar  wrote:

>
> Andrei Olsen wrote:
>
> > On Tuesday, July 9, 2013 3:50:20 PM UTC+2, David Fishburn wrote:
> > > I believe I saw this fixed earlier, or something related.
> > >
> > >
> > > I have tested this with:
> > >
> > > :ver
> > > VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul  9 2013 09:34:36)
> > >
> > > MS-Windows 32-bit GUI version with OLE support
> > > Included patches: 1-6
> > > Compiled by me
> > > Big version with GUI.  Features included (+) or not (-):
> > >
> > >
> > > Run on Windows 7 x64.
> > >
> > >
> > >
> > > gvim.exe -u NONE -U NONE
> > >
> > >
> > > Open Vim.
> > > Resize Vim so that the top and bottom of the Vim window is nearly
> maximized.
> > > Or
> > >
> > > Simply maximize Vim by double clicking on the title bar.
> > >
> > >
> > > Run the following:
> > >
> > > :echo confirm('Test'.repeat("\nNext line", 80))
> > >
> > >
> > >
> > > This will produce a dialog box with a scrollbar within it.
> > > The scrolling of the items is correct.
> > >
> > >
> > > But, there are 2 issues.
> > >
> > >
> > >
> > > 1.  Assuming your taskbar is at the default windows position (bottom
> > > of screen) then window is much longer than than the window size.
> > >  Many of the "Next lines" are off the screen and the OK button is no
> > > where to be seen.
> > >
> > >
> > >
> > > 2.  If you taskbar is at the top of the screen (as mine always is)
> > > then the problem may stem from the same issue of being too large,
> > > but there is an additional problem.  The top of the window is
> > > underneath the taskbar, so you cannot click on it to move it.  Many
> > > of the "Next lines" are off the screen and the OK button is no where
> > > to be seen.
> > >
> > >
> > >
> > > Please make sure Vim has either been maximized or nearly the length
> > > of the screen first.  If you do not, you will not see the same
> > > behaviour.  The confirm modal window is larger than Vim, but it will
> > > not exceed screen size if Vim isn't using most of screen
> > > real-estate.
> > >
> > >
> > >
> > > David
> >
> > The attached patch should fix it. The dialog is border size smaller
> > than the window so it would fit when the window is maximized.
> >
> > Also made the dialog a bit smaller when we don't have a window, e.g.
> > gvim -h. It didn't fit completely on my PC, part of the dialog was
> > behind the taskbar.
>
> Thanks.  Obviously one should not use a dialog with so much text, but
> not being able to click "cancel" is a problem.
>
>
> Agreed.

Before the fix there are 2 problems that I see.

1.  The Ok Cancel buttons are off the screen at the bottom.

2.  If your task bar is at the top of your screen (instead of the default
bottom) the "X" to close the window is also not visible.  Because it is not
visible, you cannot "move" the window to get access to it.
 ALT-Space-M(ove) does not work since we are in an single line edit box
waiting for user input.  To the ALT-Space-M goes into the user input.  The
Escape button (on Windows) closes the dialog.

The dialog box does have a scroll bar, so the N entries in the window will
scroll so they can still see and read what is within the dialog.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 7.4a - Confirm dialog box larger than screen size

[David Fishburn]

On Jul 31, 2013, at 8:20 PM, Andrei Olsen  wrote:

> On Tuesday, July 9, 2013 3:50:20 PM UTC+2, David Fishburn wrote:
>> I believe I saw this fixed earlier, or something related.
>> 
>> 
>> I have tested this with:
>> 
>> :ver
>> VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul  9 2013 09:34:36)
>> 
>> MS-Windows 32-bit GUI version with OLE support
>> Included patches: 1-6
>> Compiled by me
>> Big version with GUI.  Features included (+) or not (-):
>> 
>> 
>> Run on Windows 7 x64.
>> 
>> 
>> 
>> gvim.exe -u NONE -U NONE
>> 
>> 
>> Open Vim.
>> Resize Vim so that the top and bottom of the Vim window is nearly maximized.
>> Or
>> 
>> Simply maximize Vim by double clicking on the title bar.
>> 
>> 
>> Run the following:
>> 
>> :echo confirm('Test'.repeat("\nNext line", 80))
>> 
>> 
>> 
>> This will produce a dialog box with a scrollbar within it.
>> The scrolling of the items is correct.
>> 
>> 
>> But, there are 2 issues.
>> 
>> 
>> 
>> 1.  Assuming your taskbar is at the default windows position (bottom of 
>> screen) then window is much longer than than the window size.  Many of the 
>> "Next lines" are off the screen and the OK button is no where to be seen.
>> 
>> 
>> 
>> 2.  If you taskbar is at the top of the screen (as mine always is) then the 
>> problem may stem from the same issue of being too large, but there is an 
>> additional problem.  The top of the window is underneath the taskbar, so you 
>> cannot click on it to move it.  Many of the "Next lines" are off the screen 
>> and the OK button is no where to be seen.
>> 
>> 
>> 
>> Please make sure Vim has either been maximized or nearly the length of the 
>> screen first.  If you do not, you will not see the same behaviour.  The 
>> confirm modal window is larger than Vim, but it will not exceed screen size 
>> if Vim isn't using most of screen real-estate.
>> 
>> 
>> 
>> David
> 
> The attached patch should fix it. The dialog is border size smaller than the 
> window so it would fit when the window is maximized.
> 
> Also made the dialog a bit smaller when we don't have a window, e.g. gvim -h. 
> It didn't fit completely on my PC, part of the dialog was behind the taskbar.

There is still an issue and the dialog is still larger than the screen. 

Here is a picture. 
7.3 on the left. 
7.4b on the right. 

You can see it is better with your patch but still cut off. 



Thanks. 
David

<>-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Patch 7.4b.018

[David Fishburn]

On Wed, Aug 7, 2013 at 9:27 AM, Bram Moolenaar  wrote:

>
> Patch 7.4b.018 (after 7.4b.001)
> Problem:Win32: Dialog can still be too big.
> Solution:   Move the check for height further down. (Andrei Olsen)
> Files:  src/gui_w32.c
>
>
>
Confirmed fix on windows.

Thank you.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Alternate file with netrw buffer in Vim 7.4 - bug or change?

[David Fishburn]

On Aug 26, 2013, at 1:34 PM, Bram Moolenaar  wrote:

> 
> Bruno Sutic wrote:
> 
>> Hi,
>> I noticed a "new" behavior with vim 7.4 and netrw plugin.
>> Alternate buffer command (normal mode C-^ key) works differently than in vim 
>> 7.3.
>> 
>> Here are the steps how to see the difference:
>> *vim 7.3*
>> 1. /usr/bin/vim -u NORC -N (starting vim7.3)
>> 2. :e Gemfile   (open any random file)
>> 3. :E(show netrw plugin buffer)
>> 4. 
>> 5. C-^ (alternate buffer)
>> At this point vim shows netrw buffer opened in step 3
>> 
>> *vim 7.4* (the same steps)
>> 1. vim -u NORC -N (starting vim7.4)
>> 2. :e Gemfile
>> 3. :E
>> 4. 
>> 5. C-^
>> At this point vim 7.4 shows 'Gemfile' file opened in step 2
>> 
>> What do you think is this a bug or new behavior?
>> Thanks
> 
> I also see this problem.  I prefer the old way, I often go back to the
> directory view.  I thought Charles had changed it...
> 

I prefer the new way. 
After opening the file I explored to I would want to toggle back and forth 
between the last file edited not explorer. 

Sounds like an netrw option to me!
--
David Fishburn

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

[David Fishburn]

...

> Maybe control-c should cancel intervals.  As you mentioned, this would let
> users save stuff and restart vim.  At worse, plugins would be dumped into
> an inconsistent state that could cause more harm.  Also, canceling internal
> callbacks is quite opaque to users.  I don't see any great options for
> dealing with runaway plugins.
>
>
> What I typically see if lots of users have many plugins installed.  It is
very easy to forget what was installed last that could be leading to
"strange" problems in Vim.  Anything running asynchronously I assume could
easily fall under this category.

So yes, I believe an option or something to turn off asynchronous execution
would be a great idea, as it would be one more step people on this list
could suggest to see if the "symptom" goes away and allows the user to
narrow their search to find the offending code.

My 2 cents.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Trailing whitespace left at end of comment lines that wrap in the PHP filetype

[David Fishburn]

On Tue, Sep 17, 2013 at 8:33 PM, Duncan de Wet wrote:

> ...
>


> >
> > Is this not the right place to contact the maintainer of that file?
> >
> > | Duncan de Wet
>
> Never mind, I have found the Github page for that filetype so have done a
> pull
> request there.
>

Typically the Vim files have contact information at the top of them.
That is the way the maintainer should be contacted, not everyone subscribes
to vim_use or vim_dev.

I have seen my plugins on github and I have no idea how they get there.
So, if you did a "pull request" on github for any of my plugins, that would
certainly not make it to me.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [PATCH] Asynchronous functions (settimeout, setinterval, and cancelinterval)

[David Fishburn]

On Mon, Sep 23, 2013 at 8:53 PM, kans  wrote:

> ...
>


> > Like others I'm worried that some plugin creates a timer with a problem,
> >
> > and it keeps triggering over and over.  The user must have a way to stop
> >
> > it.
>
> The new behavior cancels intervals if they error in any way.
>  Additionally, upon further thought, there is no way around ctrl-C.  That
> is, we have to use signals and ctrl-c (SIGINT) is the only convenient one.
>  In the newest version, ctrl-c will cancel a given timeout/interval and all
> future calls.
>
>
FYI, I often use CTRL-C when Vim is taking too long (for example, my home
drive is N: and I am not connected to the network).  I understand why we
want this, but I am just wondering how often people use CTRL-C within Vim.

What I would _very_ much like to see is when CTRL-C is pressed, and there
are timed events, Vim would display the name of each timed event canceled.
 I would also like to see future events differentiated.

CTRL-C
Cancelled 21_DB_timedEvent
Future events cancelled
21_DB_timedEvent
34_SS_MyTimedEvent
87_GG_hisTimedEvent

That way, if I see a pattern that I am a canceling the same event over and
over, I can start vimgrepping my plugin / autoload directories to figure
out what plugin is installing that timed event.



> > Also, there will be plugins that have interference with what some
> >
> > timer is doing, there needs to be a way to temporary disable them.
>
> The new solution is good enough from the user's perspective.  If a rogue
> timer exists, the only possible action is to cancel it, save buffers, and
> restart vim after removing the offending plugin.  No plugin is going to
> continue to work after its timers are canceled.
>

If the CTRL-C shows the above information, we can at least identify
potential issue plugins.

I think when we document this feature in the Vim Help files, it is
important to indicated every timed event should reference a GLOBAL variable
which will allow the plugin to disable the timed event.

So, similar to how plugin developers follow the standard:

if exists('g:loaded_myplugin')
finish
endif
let g:loaded_myplugin = 1

In our timed event sample (prominently displayed) in the help we could have:

let g:myplugin_allow_timedevent = 1

function! MyPlugin_timedEvent()
if g:myplugin_allow_timedevent == 0
return
endif

 -- Do stuff here
endfunction

This might help (especially) first time plugin writers of the timed event
feature to put in some safe guards ahead of time.


David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Regression after 7.4.03x] Selection is kept after copying over it

[David Fishburn]

On Wed, Sep 25, 2013 at 10:43 AM, Axel Bender
wrote:

> Please compare the following case using the current (7.4.35) and a
> previous (7.4ß = the last I can return to) version of gvim (here: Windows 7
> 64 bit).
>
> In the current version a selection - after being copied over with the
> contents of a register - is kept (no deselection).
>
> In the previous version the selection is deselected.
>
> Nice catch, I just this second ran into this.

Dave

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 7.4a - Confirm dialog box larger than screen size

[David Fishburn]

On Mon, Sep 2, 2013 at 9:15 PM, David Fishburn wrote:

>
> Turns out this problem also affects Linux (gnome in this case).
>
> ...
>

Can anyone confirm the same (incorrect) behaviour on non-Windows platforms?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Feature Request: ChangeDirectory Autocmd

[David Fishburn]

On 2013-10-02, Amadeus Demarzi wrote:

> > This is a feature I would find highly useful, and could enable
> > many plugins to operate more efficiently.
>
> Isn't this autochdir?

:h autochdir

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

NFA 3 times slower, syntime doesn't help

[David Fishburn]

NFA engine takes almost three times (300 vs 107 seconds) as long to
complete my plugin task.

:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Oct 11 2013 09:03:38)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-52

My SQLUtilities plugin reformats SQL statements, through the use of many
regular expressions using:
:s///
substitute()
synID()
syncIDtrans()
search()

I thought I would use :syntime to help identify what expressions were
causing issues, but the results do not help me much.  I am also not certain
if perhaps I an running things correctly to help identify where the issue
might be.

Basically, I do the following:
:set re=x
:syntime on
my plugin call
:syntime report
paste to this email.

:set re=x
:syntime clear
my plugin call
:syntime report
paste to this email.


Here are the results:

:set re=0

With :syntime off, this takes 3 minute and 20 seconds.

  TOTAL  COUNT  MATCH   SLOWEST AVERAGE   NAME   PATTERN
  0.148406   2095   60  0.0012230.71  sqlNumber
 -\=\<\d*\.\=[0-9_]\>
  0.014026   2035   0   0.0001420.07  sqlDashComment --
  0.013963   2035   0   0.780.07  sqlMultiComment/\*
  0.013940   2095   60  0.0001520.07  sqlString  '
  0.013811   2035   0   0.0002000.07  sqlSlashComment\/\/
  0.002153   16919  16253   0.020.00  sqlString  "
  0.001525   7521   75210.080.00  sqlString  "
  0.07   36 36  0.000.00  sqlString  '

  0.207830   34771


:set re=1

With :syntime off, this takes 1 minute and 47 seconds.

  TOTAL  COUNT  MATCH   SLOWEST AVERAGE   NAME   PATTERN
  0.295036   4295   120 0.0012230.69  sqlNumber
 -\=\<\d*\.\=[0-9_]\>
  0.065744   4965   795 0.0014540.13  sqlString  '
  0.028317   4175   0   0.0002330.07  sqlDashComment --
  0.028185   4175   0   0.0001990.07  sqlMultiComment/\*
  0.027620   4175   0   0.0002000.07  sqlSlashComment\/\/
  0.004863   34883  33451   0.0002630.00  sqlString  "
  0.003288   15763  15763   0.120.00  sqlString  "
  0.11   72 72  0.000.00  sqlString  '

  0.453065   72503


I don't even see many of the regexp expressions I used.  Given I am
formatting SQL statements, I am searching for many SQL keywords, (SELECT,
INSERT, UPDATE, DELETE, ...) and I don't see those words even referenced in
the syntime report output.

Thanks for any input.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Feature request: flag to 'complete' so that i_Ctrl-N ignores remote buffers

[David Fishburn]

On Wed, Nov 13, 2013 at 9:03 AM, Christian Brabandt wrote:

> On Tue, November 12, 2013 16:53, Ben Fritz wrote:
> > On Monday, November 11, 2013 10:45:15 PM UTC-6, Suresh Govindachar wrote:
> >> Hello,
> >>
> >>
> >>
> >> Please consider providing the feature whereby i_Ctrl-N would ignore
> >>
> >> buffers whose name begins with \\machine_name\ and machine_name is a
> >>
> >> remote machine (Microsoft Uniform Naming Convention (UNC)).
> >>
> >
> > I think what you're really asking is for a way to exclude buffers or
> files
> > from being processed by insert-mode completion, if you know scanning them
> > will be slow.
> >
> > This could be true for very large file, or for files on a network share,
> > or files that require reading with autocmds to unzip them or something.
> >
> > I support such an option. I like keeping 'path' fairly large for
> searching
> > with :find for a file, but this makes insert completion very slow if I
> > allow it to search in included files. Previously when we were using
> > ClearCase on my team, EVERY insert completion that scanned other files
> was
> > slow, because the ClearCase "dynamic view" mapped network drive is
> > painfully slow. I had to turn off most of the completion functions. I'd
> > certainly use a filter to remove specific directories from insert
> > completion scanning, were it available.
>
> So this would mean, having a new buffer local option like
> 'completebufignore' that is off by default and could be set to
> ignore the current buffer from being processed for completion?
>
>
To me it sounded more like in the buffer where you are running C-X C-O, you
would have an option where you could list all the buffers you do not want
to complete from.

Kind of like browsefilter, but in this case, I can access the filetypes or
filenames of the buffers to exclude.

My 2 cents.
Dave

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Linker error: COFF: file invalid or corrupt

[David Fishburn]

I believe I compiled 7.4 last on Nov 11th.

I just did my usual .cmd file to fetch and build Vim and it failed.
So I deleted my vim directory and refetched and ran my usual process.

Compiles fine, but linker error:

...

cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -D
FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400
 /Fo
.\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
-DDYNAMIC_IC
ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
 -DDYNAMIC_PYTHON_DLL=\"pyt
hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
 -DDYNAMIC_PYTHON3_DLL=\"python33.d
ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
-DFEAT_HUGE /
Fd.\ObjGOLYHi386/ /Zi blowfish.c buffer.c charset.c diff.c digraph.c edit.c
eval
.c ex_cmds.c ex_cmds2.c ex_docmd.c ex_eval.c ex_getln.c fileio.c fold.c
getchar.
c hardcopy.c hashtab.c main.c mark.c mbyte.c memfile.c memline.c menu.c
message.
c misc1.c misc2.c move.c normal.c ops.c option.c os_mswin.c winclip.c
os_win32.c
 popupmnu.c quickfix.c regexp.c screen.c search.c sha256.c spell.c syntax.c
tag.
c term.c ui.c undo.c window.c gui.c gui_beval.c gui_w32.c os_w32exe.c
if_cscope.
c netbeans.c
blowfish.c
buffer.c
charset.c
diff.c
digraph.c
edit.c
eval.c
ex_cmds.c
ex_cmds2.c
ex_docmd.c
ex_eval.c
ex_getln.c
fileio.c
fold.c
getchar.c
hardcopy.c
hashtab.c
main.c
mark.c
mbyte.c
Compiling...
memfile.c
memline.c
menu.c
message.c
misc1.c
misc2.c
move.c
normal.c
ops.c
option.c
os_mswin.c
winclip.c
os_win32.c
popupmnu.c
quickfix.c
regexp.c
screen.c
search.c
sha256.c
spell.c
Compiling...
syntax.c
tag.c
term.c
ui.c
undo.c
window.c
gui.c
gui_beval.c
gui_w32.c
os_w32exe.c
if_cscope.c
netbeans.c
cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -D
FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400
 /Fo
.\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
-DDYNAMIC_IC
ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
 -DDYNAMIC_PYTHON_DLL=\"pyt
hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
 -DDYNAMIC_PYTHON3_DLL=\"python33.d
ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
-DFEAT_HUGE /
Fd.\ObjGOLYHi386/ /Zi if_ole.cpp
if_ole.cpp
cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -D
FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400
 /Fo
.\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
-DDYNAMIC_IC
ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
 -DDYNAMIC_PYTHON_DLL=\"pyt
hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
 -DDYNAMIC_PYTHON3_DLL=\"python33.d
ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
-DFEAT_HUGE /
Fd.\ObjGOLYHi386/ /Zi version.c
version.c
link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe
.\Ob
jGOLYHi386\blowfish.obj  .\ObjGOLYHi386\buffer.obj
 .\ObjGOLYHi386\charset.obj
.\ObjGOLYHi386\diff.obj  .\ObjGOLYHi386\digraph.obj
 .\ObjGOLYHi386\edit.obj  .\
ObjGOLYHi386\eval.obj  .\ObjGOLYHi386\ex_cmds.obj
 .\ObjGOLYHi386\ex_cmds2.obj
.\ObjGOLYHi386\ex_docmd.obj  .\ObjGOLYHi386\ex_eval.obj
 .\ObjGOLYHi386\ex_getln
.obj  .\ObjGOLYHi386\fileio.obj  .\ObjGOLYHi386\fold.obj
 .\ObjGOLYHi386\getchar
.obj  .\ObjGOLYHi386\hardcopy.obj  .\ObjGOLYHi386\hashtab.obj
 .\ObjGOLYHi386\ma
in.obj  .\ObjGOLYHi386\mark.obj  .\ObjGOLYHi386\mbyte.obj
 .\ObjGOLYHi386\memfil
e.obj  .\ObjGOLYHi386\memline.obj  .\ObjGOLYHi386\menu.obj
 .\ObjGOLYHi386\messa
ge.obj  .\ObjGOLYHi386\misc1.obj  .\ObjGOLYHi386\misc2.obj
 .\ObjGOLYHi386\move.
obj  .\ObjGOLYHi386\normal.obj  .\ObjGOLYHi386\ops.obj
 .\ObjGOLYHi386\option.ob
j  .\ObjGOLYHi386\os_mswin.obj  .\ObjGOLYHi386\winclip.obj
 .\ObjGOLYHi386\os_wi
n32.obj  .\ObjGOLYHi386\pathdef.obj  .\ObjGOLYHi386\popupmnu.obj
 .\ObjGOLYHi386
\quickfix.obj  .\ObjGOLYHi386\regexp.obj  .\ObjGOLYHi386\screen.obj
 .\ObjGOLYHi
386\search.obj  .\ObjGOLYHi386\sha256.obj  .\ObjGOLYHi386\spell.obj
 .\ObjGOLYHi
386\syntax.obj  .\ObjGOLYHi386\tag.obj  .\ObjGOLYHi386\term.obj
 .\ObjGOLYHi386\
ui.obj  .\ObjGOLYHi386\undo.obj  .\ObjGOLYHi386\window.obj
 .\ObjGOLYHi386\vim.r
es .\ObjGOLYHi386\gui.obj  .\ObjGOLYHi386\gui_beval.obj
 .\ObjGOLYHi386\gui_w32.
obj  .\ObjGOLYHi386\os_w32exe.obj .\ObjGOLYHi386\if_ole.obj
 .\ObjGOLYHi386\if
_perl.obj .\ObjGOLYHi386\if_perlsfio.obj .\ObjGOLYHi386\if_python.obj
.\ObjGOLYH
i386\if_python3.obj .\ObjGOLYHi386/if_cscope.obj
.\ObjGOLYHi386/netbeans.obj
  .\ObjGOLYHi386/xpm_w32.obj .\ObjGOLYHi386\version.obj oldnames.lib
kernel32.li
b advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib uuid.lib
/machine:i
386 /nodefaultlib gdi32.lib version.lib   winspool.lib comctl32.lib
advapi32.lib
 shell32.lib  /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib
 user32.lib
   /nodefaultlib:python27.lib /nodefaultlib:python33.libWSock32.lib
xpm\x86\
lib\libXpm.lib /PDB:gvim.pdb -debug
Generating code
  100%   0 seconds remaining
Finished generating code
LINK : fatal error LNK1123: failure duri

Re: Linker error: COFF: file invalid or corrupt

[David Fishburn]

On Thu, Nov 28, 2013 at 3:39 PM, David Fishburn wrote:

> I believe I compiled 7.4 last on Nov 11th.
>
> I just did my usual .cmd file to fetch and build Vim and it failed.
> So I deleted my vim directory and refetched and ran my usual process.
>
> Compiles fine, but linker error:
>
> ...
>
> cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
> -DFEAT_CSCOPE -D
> FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
> -D_WIN32_WINNT=0x0400  /Fo
> .\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
> -DDYNAMIC_IC
> ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
>  -DDYNAMIC_PYTHON_DLL=\"pyt
> hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
>  -DDYNAMIC_PYTHON3_DLL=\"python33.d
> ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
> -DFEAT_HUGE /
> Fd.\ObjGOLYHi386/ /Zi blowfish.c buffer.c charset.c diff.c digraph.c
> edit.c eval
> .c ex_cmds.c ex_cmds2.c ex_docmd.c ex_eval.c ex_getln.c fileio.c fold.c
> getchar.
> c hardcopy.c hashtab.c main.c mark.c mbyte.c memfile.c memline.c menu.c
> message.
> c misc1.c misc2.c move.c normal.c ops.c option.c os_mswin.c winclip.c
> os_win32.c
>  popupmnu.c quickfix.c regexp.c screen.c search.c sha256.c spell.c
> syntax.c tag.
> c term.c ui.c undo.c window.c gui.c gui_beval.c gui_w32.c os_w32exe.c
> if_cscope.
> c netbeans.c
> blowfish.c
> buffer.c
> charset.c
> diff.c
> digraph.c
> edit.c
> eval.c
> ex_cmds.c
> ex_cmds2.c
> ex_docmd.c
> ex_eval.c
> ex_getln.c
> fileio.c
> fold.c
> getchar.c
> hardcopy.c
> hashtab.c
> main.c
> mark.c
> mbyte.c
> Compiling...
> memfile.c
> memline.c
> menu.c
> message.c
> misc1.c
> misc2.c
> move.c
> normal.c
> ops.c
> option.c
> os_mswin.c
> winclip.c
> os_win32.c
> popupmnu.c
> quickfix.c
> regexp.c
> screen.c
> search.c
> sha256.c
> spell.c
> Compiling...
> syntax.c
> tag.c
> term.c
> ui.c
> undo.c
> window.c
> gui.c
> gui_beval.c
> gui_w32.c
> os_w32exe.c
> if_cscope.c
> netbeans.c
> cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
> -DFEAT_CSCOPE -D
> FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
> -D_WIN32_WINNT=0x0400  /Fo
> .\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
> -DDYNAMIC_IC
> ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
>  -DDYNAMIC_PYTHON_DLL=\"pyt
> hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
>  -DDYNAMIC_PYTHON3_DLL=\"python33.d
> ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
> -DFEAT_HUGE /
> Fd.\ObjGOLYHi386/ /Zi if_ole.cpp
> if_ole.cpp
> cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
> -DFEAT_CSCOPE -D
> FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
> -D_WIN32_WINNT=0x0400  /Fo
> .\ObjGOLYHi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
> -DDYNAMIC_IC
> ONV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
>  -DDYNAMIC_PYTHON_DLL=\"pyt
> hon27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
>  -DDYNAMIC_PYTHON3_DLL=\"python33.d
> ll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
> -DFEAT_HUGE /
> Fd.\ObjGOLYHi386/ /Zi version.c
> version.c
> link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
> -out:gvim.exe .\Ob
> jGOLYHi386\blowfish.obj  .\ObjGOLYHi386\buffer.obj
>  .\ObjGOLYHi386\charset.obj
> .\ObjGOLYHi386\diff.obj  .\ObjGOLYHi386\digraph.obj
>  .\ObjGOLYHi386\edit.obj  .\
> ObjGOLYHi386\eval.obj  .\ObjGOLYHi386\ex_cmds.obj
>  .\ObjGOLYHi386\ex_cmds2.obj
> .\ObjGOLYHi386\ex_docmd.obj  .\ObjGOLYHi386\ex_eval.obj
>  .\ObjGOLYHi386\ex_getln
> .obj  .\ObjGOLYHi386\fileio.obj  .\ObjGOLYHi386\fold.obj
>  .\ObjGOLYHi386\getchar
> .obj  .\ObjGOLYHi386\hardcopy.obj  .\ObjGOLYHi386\hashtab.obj
>  .\ObjGOLYHi386\ma
> in.obj  .\ObjGOLYHi386\mark.obj  .\ObjGOLYHi386\mbyte.obj
>  .\ObjGOLYHi386\memfil
> e.obj  .\ObjGOLYHi386\memline.obj  .\ObjGOLYHi386\menu.obj
>  .\ObjGOLYHi386\messa
> ge.obj  .\ObjGOLYHi386\misc1.obj  .\ObjGOLYHi386\misc2.obj
>  .\ObjGOLYHi386\move.
> obj  .\ObjGOLYHi386\normal.obj  .\ObjGOLYHi386\ops.obj
>  .\ObjGOLYHi386\option.ob
> j  .\ObjGOLYHi386\os_mswin.obj  .\ObjGOLYHi386\winclip.obj
>  .\ObjGOLYHi386\os_wi
> n32.obj  .\ObjGOLYHi386\pathdef.obj  .\ObjGOLYHi386\popupmnu.obj
>  .\ObjGOLYHi386
> \quickfix.obj  .\ObjGOLYHi386\regexp.obj  .\ObjGOLYHi386\screen.obj
>  .\ObjGOLYHi
> 386\search.obj  .\ObjGOLYHi386\sha256.obj  .\ObjGOLYHi386\spell.obj
>  .\ObjGOLYHi
> 386\syntax.obj  .\ObjGOLYHi386\tag.obj  .\ObjGOLYHi386\term.obj
>  .\ObjGOLYHi386\
> ui.obj  .\ObjGOLYHi386\undo.obj  .\ObjGOLYHi386\window.obj

Re: Linker error: COFF: file invalid or corrupt

[David Fishburn]

>
> ...
> > > Finished generating code
> > > LINK : fatal error LNK1123: failure during conversion to COFF: file
> > > invalid or c
> > > orrupt
> > > NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual
> > > Studio 10.0
> > > \VC\BIN\link.EXE"' : return code '0x463'
> > > Stop.
> > >
> > >
> > >
> > I just did a complete refresh from source today and am still getting this
> > error.
> >
> > Anyone have any suggestions for me?
>
> Looks like a problem with MS Visual Studio. According to this
> stackowerflow question (http://stackoverflow.com/questions/10888391), it
> might help so simply disable incremental linking or install VS2010 SP1
>
> You are a good man Christian.

Never considered it was a VS issue, assumed it was Vim code.

SP1 installed, code compiled and running 7.4.1-154.

Dave

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [RFC] Revision of Objective-C Syntax

[David Fishburn]

On Thu, Jan 23, 2014 at 11:25 PM, Adam Sharp  wrote:

> ...
>
> So it turns it I was doing it wrong: after moving the file into
> ~/.vim/syntax and running it through dos2unix, it started working. No
> more red braces.
>
> If I do find any issues, is this still the right place to report them?
>
>
> Start on vim_use.  Typically someone there would direct you here is
required.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Request to add pgsql syntax file for postgresql source code files

[David Fishburn]

On Sat, Apr 12, 2014 at 12:22 AM, Gang Liang
wrote:

> Here is a minor request for your consideration:
>
> Postgresql (http://www.postgresql.org/) is one of the best open source
> database solutions. Its source files might have an extension of either .sql
> or .pgsql. Here, I would like to request to add its syntax file pgsql.vim
> to the $VIMRUNTIME/syntax directory. In addition, $VIMRUNTIME/filetype.vim
> would be slightly modified to recognize the .pgsql file extension.
>
>
As a FYI .

If you add syntax\pgsql.vim, and you want Vim to default to using this
syntax file instead of the Oracle (plsql.vim) default, then you can add the
following to your .vimrc:

let g:sql_type_default = 'pgsql'

To change this temporarily for a buffer you can use:
:SQLSetType
:SQL   - will list the options available to choose from
(including pgsql)
:SQLSetType  - with no parameter, restored to default (Oracle)

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Enabling Python on Windows

[David Fishburn]

Been building Vim for years, trying to get the Python builds to work and am
failing.

I can't see what is wrong, the parameters I pass to make a pretty clear.
I know I have built with Python in the past and not much has changed.

If anyone can see anything for me to try it would be appreciated.


Vim 7.4.1-258

:echo has('python') has('python2') has('python3')
0 0 0

C:\OpenSrc\vim\src>which python27.dll
c:\Python27\python27.dll


C:\OpenSrc>dir c:\Python27
 Volume in drive C is OSDisk
 Volume Serial Number is E8F1-79E4

 Directory of c:\Python27

13/04/2014  07:57 PM  .
13/04/2014  07:57 PM  ..
13/04/2014  07:56 PM  DLLs
18/09/2012  02:51 PM  Doc
18/09/2012  02:51 PM  include
03/02/2014  02:27 PM  Lib
18/09/2012  02:51 PM  libs
02/10/2013  10:05 AM  Scripts
18/09/2012  02:51 PM  tcl
18/09/2012  02:51 PM  Tools
10/04/2012  11:31 PM40,092 LICENSE.txt
10/04/2012  11:18 PM   310,875 NEWS.txt
10/04/2012  11:24 PM27,136 python.exe
06/04/2013  07:55 PM 3,003,392 python27.dll
10/04/2012  11:24 PM27,648 pythonw.exe
18/03/2012  11:58 PM54,973 README.txt


nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes FEATURES=HUGE
PYTHON=C:\Python27 DYNAMIC_PYTHON=yes PYTHON_VER=27 PERL=C:\Perl
DYNAMIC_PERL=yes PERL_VER=510 XPM=xpm\x86 clean




:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 13 2014 20:37:47)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-258
Compiled by me
Huge version with GUI.  Features included (+) or not (-):
+acl +cmdline_compl   +diff+find_in_path
 +langmap +mouse   -postscript  +signs   -tcl
  +visualextra +xpm_w32
+arabic  +cmdline_hist+digraphs+float
+libcall +mouseshape  +printer +smartindent
-tgetent +viminfo
+autocmd +cmdline_info-dnd +folding
+linebreak   +multi_byte  +profile -sniff
-termresponse+vreplace
+balloon_eval+comments-ebcdic  -footer
 +lispindent  +multi_lang  +python/dyn  +startuptime
+textobjects +wildignore
+browse  +conceal +emacs_tags  +gettext/dyn
+listcmds-mzscheme-python3 +statusline  +title
  +wildmenu
++builtin_terms  +cryptv  +eval-hangul_input
 +localmap+netbeans_intg   +quickfix-sun_workshop
 +toolbar +windows
+byte_offset +cscope  +ex_extra+iconv/dyn   -lua
  +ole +reltime +syntax  +user_commands
  +writebackup
+cindent +cursorbind  +extra_search+insert_expand   +menu
 +path_extra  +rightleft   +tag_binary  +vertsplit
  -xfontset
+clientserver+cursorshape +farsi   +jumplist
 +mksession   +perl/dyn-ruby+tag_old_static
 +virtualedit -xim
+clipboard   +dialog_con_gui  +file_in_path+keymap
 +modify_fname+persistent_undo +scrollbind  -tag_any_white
+visual  -xterm_save
   system vimrc file: "$VIM\vimrc"
 user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$HOME\vimfiles\vimrc"
 3rd user vimrc file: "$VIM\_vimrc"
  user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$HOME\vimfiles\gvimrc"
3rd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
-D_WIN32_WINNT=0x0400  /Fo.\ObjGOLYi386/ /Ox /GL
-DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32 -DDYNAMIC_ICONV
-DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
 -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PERL -DDYNAMIC_PERL
-DDYNAMIC_PER
L_DLL=\"perl510.dll\" -DFEAT_HUGE /Fd.\ObjGOLYi386/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib
kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib
uuid.lib /machine:i386 /nodefaultlib gdi
32.lib version.lib   winspool.lib comctl32.lib advapi32.lib shell32.lib
 /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib  user32.lib
 /nodefaultlib:python27.lib WSock32.lib xpm
\x86\lib\libXpm.lib /PDB:gvim.pdb -debug


Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enabling Python on Windows

[David Fishburn]

On Wed, Apr 16, 2014 at 6:34 AM, Charles  wrote:

>
> On Wed, Apr 16, 2014 at 9:15 AM, David Fishburn 
> wrote:
>
>> Been building Vim for years, trying to get the Python builds to work and
>> am failing.
>>
>> I can't see what is wrong, the parameters I pass to make a pretty clear.
>> I know I have built with Python in the past and not much has changed.
>>
>
> You can try these things
>
> 1. Copy python27.dll to the same directory as gvim.exe
> 2. Add let $PYTHONHOME=C:\python27 to vimrc (at the top before any :py
> calls)
>
>
Tried both of these, same result, no python.

Thanks for the suggestion.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enabling Python on Windows

[David Fishburn]

On Wed, Apr 16, 2014 at 5:00 AM, Ken Takata  wrote:

> ...
>
> Do you use 32-bit version of python?
> If you use 32-bit Vim, you should use 32-bit python. 64-bit python won't
> work.
>
> Sorry Ken, should have mentioned that.

I am running on Windows 7 64-bit.

But I only use and build 32-bit Vim.
The Python 2.7 I have installed is 32-bit.
The Perl I have installed is 32-bit.

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enabling Python on Windows

[David Fishburn]

On Wed, Apr 16, 2014 at 8:32 AM, Charles  wrote:

>
> On Wed, Apr 16, 2014 at 7:27 PM, David Fishburn 
> wrote:
>
>> Tried both of these, same result, no python.
>>
>> Thanks for the suggestion.
>>
>
>
> Looking at the file size of python27.dll it's surely 64 bit python as Ken
> said before. So you'll need to install 32 bit python first, and if it still
> does not work try doing those two steps.
>
>
Right you were Charles.

Looks like the DLL was picked up from Mecurial:

$ file /cygdrive/c/Program\ Files/Mercurial/python27.dll
/cygdrive/c/Program Files/Mercurial/python27.dll: PE32+ executable (DLL)
(GUI) x86-64, for MS Windows


I re-downloaded Python 2.7 32-bit, re-ran the installer.
Removed all found references to python27.dll.

C:\Python27>dir C:\WINDOWS\system32\python27.dll
 Volume in drive C is OSDisk
 Volume Serial Number is E8F1-79E4

 Directory of C:\WINDOWS\system32

10/04/2012  11:24 PM 2,987,520 python27.dll


$ file /cygdrive/c/windows/system32/python27.dll
/cygdrive/c/windows/system32/python27.dll: PE32 executable (DLL) (GUI)
Intel 80386, for MS Windows

:echo has('python') has('python2') has('python3')
1 0 0

Thanks for everyone's help.
Much appreciated.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problems with star (*) mappings in vim 7.4 (with MS Windows)

[David Fishburn]

On Fri, May 30, 2014 at 9:46 AM, Christian Brabandt 
wrote:

> Hi Pedro!
>
> On So, 25 Mai 2014, Pedro Ferrari wrote:
>
> > I believe that the problem (bug?) is that the * (star) key cannot be
> > remapped: if I start vim with "vim -N -u NONE" (Vim 7.4 with patches
> > 1-274) and run the command "noremap * :echo "star"" and press *,
> > vim tries to perform a search.
>
> I can't reproduce this. Is this gvim/vim and on what Operating system?
>
> I tried this on Windows 7 (64) running 32-bit Vim.

:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 13 2014 20:37:47)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-258

When I press *, I get "star" written, no search performed.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Improved Javascript indenting and syntax for inclusion

[David Fishburn]

On Thu, Apr 3, 2014 at 1:36 PM, Darrick Wiebe  wrote:

> Hi all,
>
> The vim-javascript plugin at https://github.com/pangloss/vim-javascript
> is significantly better than the one built in to Vim, which I am told is
> currently unmaintained. Vim-javascript has an active group of contributors
> and maintainers, while the indenter works well and has been mostly stable
> since 2009.
>
> Tim Pope recently created an issue on the project suggesting that we
> contribute it to Vim for inclusion in the next release. I think that's a
> good idea and probably should have been done long ago.
>

Darrick,

I have been using this version (daily) since you sent out this email and
found it to be a significant improvement.  So thank you.

Couple of comments:

1.  You have a plugin for this already here:
Better Javascript Indentation : Vastly improved javascript indentation
http://www.vim.org/scripts/script.php?script_id=2765

Could you update that version with this one.

2.  I knew I had recently downloaded a new Javascript indent script and was
trying to figure out where I got it from.  This is the top of the
indent/javascript.vim file:
" Vim indent file
" Language: Javascript
" Acknowledgement: Based off of vim-ruby maintained by Nikolai Weibull
http://vim-ruby.rubyforge.org

This doesn't tell me much, and it took me some digging to find this email
and the web site, plus diffing a bunch of different javascript.vim files to
determine this is one I am using.


This ties into #1.  If you could add headers, plus authors, plus how to
contact the author (for suggestions and bug) to the top of each file
included in this update it would be quite useful.

I believe all this information will be required before Bram would include
it in the official release as well.

Thanks for new scripts, great improvement.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] Separate filetype for JSON

[David Fishburn]

+1

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] Handle files with mixed LF - CRLF line endings when doing tag search

[David Fishburn]

On Mon, Apr 1, 2013 at 11:16 AM, Lech Lorens  wrote:

> People using ctags while working on code which is edited by multiple
> people in various editors will be familiar with this situation: the code
> ends up with a mix of line endings – some of them are Unix-style, some
> of them are DOS-style.
>
> The problem is that if Vim reads such a file with ff=unix, it will fail
> to find tags if the tag pattern searched should match on a DOS-style
> line. The attached patch handles the problem in a naïve but surprisingly
> effective way: if a pattern search fails, Vim will try putting "\r\*"
> before the last "$" in the pattern and will retry the search.
>
> I haven't looked at the patch, but what is the behaviour when
fileformats=unix,dos,mac

Does it exhibit the same behaviour?
I would think this patch should alter it's behaviour based on the values in
this setting.

My $0.02

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Variable for "motion type" in Operator-pending mode

[David Fishburn]

On Apr 19, 2013, at 5:50 PM, glts <676c7...@gmail.com> wrote:
...
> 
> Here's a good real-life example.
> 
> The textobj-word-column.vim plugin lets you select a column (Visual
> block) of words/WORDs based on the word/WORD under the cursor. If
> v:motiontype were available, the plugin could let you do, for example,
> yVac (yank linewise a word-column), basically allowing you to yank a
> range of lines which have a vertical component in common, so to speak.
> See? Well, I think that is very useful.
> 

For the YankRing plugin I use expression maps. I have to pass in the motion to 
figure this out and take appropriate action. 

There are still many cases where I have to guess and try to do the right thing. 

So this too would help with it. 


--
David Fishburn

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

NFA regression on split()

[David Fishburn]

Using 7.3.1004 on Win 7 64 bit.

gvim -u NONE -U NONE --noplugins

:set re=0
:echo split(" TBD NOTE XXX FIXME TODO \n")
['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO', '
']

:set re=1
:echo split(" TBD NOTE XXX FIXME TODO \n")
['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO']

This is a distilled case, it is affecting the results from the
autoload/syntaxcomplete.vim plugin.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Building Vim in windows with python perl support

[David Fishburn]

On Wed, May 22, 2013 at 11:24 AM, ashwin sathya wrote:

> Hi,
>
> Is there any wiki doc where i can find instructions on building vim with
> latest patches (not using Cygwin, using the make_mvc.mak, Visual Studio)
> with support for Python (2, 3) and Perl ?
> ...
>

I wrote a batch file to do my compiling for me.

The issues I have run into is different versions of Perl don't necessarily
work.  I think I have read others having similar problems, though, this may
have been resolved.

I have attached what I have, rename it to .cmd.

You can see the various environment variables I set at the top, you should
just need to update those.

This builds with Python 3.3.0 and Perl 5.10.1 and VS 2010.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


@setlocal
@echo off
@echo.
@echo After using vim_update.cmd to get the latest source from source
@echo control this command file will build the following targets for VIM:
@echo CFG="Vim - Win32 Release gvim OLE"
@echo CFG="Vim - Win32 Debug gvim OLE"
@echo CFG="Vim - Win32 Release vim"
@echo CFG="Vim - Win32 Debug vim"
@echo.

rem Need to check if we are using the 4NT shell...
if "%@eval[2+2]" == "4" goto NO_USE_4NT

IF NOT DEFINED VIM_DIR SET VIM_DIR=vim
IF NOT DEFINED VIM_XPM_DIR SET VIM_XPM_DIR=xpm\x86
IF NOT DEFINED VIM_XPM_DIR SET VIM_XPM_DIR=C:\OpenSrc\vim\src\xpm\x86
@rem IF NOT DEFINED VIM_XPM_DIR SET 
VIM_XPM_DIR=C:\download\OpenSrc\vim\XPM_support_for_Netbeans\xpm-4.2.0

IF NOT DEFINED VIM_PYTHON_VER_ARCH SET VIM_PYTHON_VER_ARCH=3
IF NOT DEFINED VIM_PYTHON_VER SET VIM_PYTHON_VER=33
IF NOT DEFINED VIM_PYTHON_DIR SET VIM_PYTHON_DIR=C:\Python33
@rem IF NOT DEFINED VIM_PYTHON_VER_ARCH SET VIM_PYTHON_VER_ARCH=
@rem IF NOT DEFINED VIM_PYTHON_VER SET VIM_PYTHON_VER=27
@rem IF NOT DEFINED VIM_PYTHON_DIR SET VIM_PYTHON_DIR=C:\Python27
IF NOT DEFINED VIM_PERL_VER SET VIM_PERL_VER=510
IF NOT DEFINED VIM_PERL_VER SET VIM_PERL_VER=516
IF NOT DEFINED VIM_PERL_VER SET VIM_PERL_VER=514
IF NOT DEFINED VIM_PERL_DIR SET VIM_PERL_DIR=C:\Perl
@rem IF NOT DEFINED VIM_PERL_DIR SET VIM_PERL_DIR=C:\Programs\perl_for_vim
IF NOT DEFINED MVC_DIR SET MVC_DIR=C:\Program Files (x86)\Microsoft Visual 
Studio 10.0\Common7\Tools
IF NOT DEFINED MVC_DIR SET MVC_DIR=C:\Program Files (x86)\Microsoft Visual 
Studio 9.0\Common7\Tools
IF NOT DEFINED MVC_DIR SET MVC_DIR=C:\Program Files\Microsoft Visual Studio 
8\Common7\Tools
IF NOT DEFINED MVC_DIR SET MVC_DIR=C:\Program Files\Microsoft Visual Studio 
.Net 2003\Common7\Tools
IF NOT EXIST "%MVC_DIR%" GOTO MVC_NOT_EXIST

@echo.
@echo First setup the Microsoft environment
@echo Check for environment variable DevEnvDir
@echo.
@echo on
IF NOT DEFINED DevEnvDir ECHO "%MVC_DIR%\vsvars32.bat"
IF NOT DEFINED DevEnvDir CALL "%MVC_DIR%\vsvars32.bat"
@echo off

:BUILD
chdir %VIM_DIR%\src

IF %1. NEQ . GOTO %1

:GVIM
@rem nmake -f Make_ivc.mak CFG="Vim - Win32 Release gvim OLE"
@echo on
@echo.
@echo *
@echo Building GVim
@echo *
set title=Building GVim
nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes 
PYTHON%VIM_PYTHON_VER_ARCH%=%VIM_PYTHON_DIR% 
DYNAMIC_PYTHON%VIM_PYTHON_VER_ARCH%=yes 
PYTHON%VIM_PYTHON_VER_ARCH%_VER=%VIM_PYTHON_VER% PERL=%VIM_PERL_DIR% 
DYNAMIC_PERL=yes PERL_VER=%VIM_PERL_VER% XPM=%VIM_XPM_DIR% clean
nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes 
PYTHON%VIM_PYTHON_VER_ARCH%=%VIM_PYTHON_DIR% 
DYNAMIC_PYTHON%VIM_PYTHON_VER_ARCH%=yes 
PYTHON%VIM_PYTHON_VER_ARCH%_VER=%VIM_PYTHON_VER% PERL=%VIM_PERL_DIR% 
DYNAMIC_PERL=yes PERL_VER=%VIM_PERL_VER% XPM=%VIM_XPM_DIR% 
@rem no_perl nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes 
PYTHON=%VIM_PYTHON_DIR% DYNAMIC_PYTHON=yes PYTHON_VER=%VIM_PYTHON_VER% 
XPM=%VIM_XPM_DIR% clean
@rem no_perl nmake -f Make_mvc.mak debug=no gui=yes cscope=yes OLE=yes 
PYTHON=%VIM_PYTHON_DIR% DYNAMIC_PYTHON=yes PYTHON_VER=%VIM_PYTHON_VER% 
XPM=%VIM_XPM_DIR% 
@echo.
@echo off
@if errorlevel 1 goto ERROR
IF "%1." NEQ "." GOTO END

:VIM
@rem nmake -f Make_ivc.mak CFG="Vim - Win32 Release vim"
@echo on
@echo.
@echo *
@echo Building Vim
@echo *
set title=Building Vim
nmake -f Make_mvc.mak debug=no gui=no cscope=yes PERL=%VIM_PERL_DIR% 
DYNAMIC_PERL=yes PERL_VER=%VIM_PERL_VER% 
@echo.
@echo off
@if errorlevel 1 goto ERROR
IF %1. NEQ . GOTO END


@rem Just stop after the gvim build
GOTO END

:GVIMD
@rem nmake -f Make_ivc.mak CFG="Vim - Win32 Debug gvim OLE"
@echo on
@echo.
@echo *

Re: NFA regression on split()

[David Fishburn]

On Thu, May 23, 2013 at 9:45 AM, Bram Moolenaar  wrote:

>
> > > David Fishburn wrote:
> > >
> > > > Using 7.3.1004 on Win 7 64 bit.
> > > >
> > > > gvim -u NONE -U NONE --noplugins
> > > >
> > > > :set re=0
> > > > :echo split(" TBD NOTE XXX FIXME TODO \n")
> > > > ['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO', '
> > > > ']
> > > >
> > > > :set re=1
> > > > :echo split(" TBD NOTE XXX FIXME TODO \n")
> > > > ['TBD', 'NOTE', 'XXX', 'FIXME', 'TODO']
> > > >
> > > > This is a distilled case, it is affecting the results from the
> > > > autoload/syntaxcomplete.vim plugin.
> > >
> > > I think patch 1005 fixed this as well.  The matching of line breaks was
> > > implemented in a wrong way.  Hopefully my solution fixes many patterns
> > > that match a line break.
> >
> > No, same incorrect behaviour using this:
> >
> > :ver
> > VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 22 2013 21:08:23)
> > MS-Windows 32-bit GUI version with OLE support
> > Included patches: 1-1005
>
> Then why can't I reproduce this problem?
> For me re=0 and re=1 do the same thing.
> That's on 32 bit, but it's unlikely that makes a difference (not
> impossible though).
>
> I build a 32-bit version of Vim.

I also do a nmake clean before nmake.

I just tried with this version and still have the change in behaviour:
:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 27 2013 09:14:00)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-1031
Compiled by dfishburn@host
Big version with GUI.  Features included (+) or not (-):
+arabic  +cmdline_hist+digraphs+float
+libcall +mouseshape  +printer +smartindent
-tgetent +viminfo
+autocmd +cmdline_info-dnd +folding
+linebreak   +multi_byte  -profile -sniff
-termresponse+vreplace
+balloon_eval+comments-ebcdic  -footer
 +lispindent  +multi_lang  -python  +startuptime
+textobjects +wildignore
+browse  +conceal +emacs_tags  +gettext/dyn
+listcmds-mzscheme+python3/dyn +statusline  +title
  +wildmenu
++builtin_terms  +cryptv  +eval-hangul_input
 +localmap+netbeans_intg   +quickfix-sun_workshop
 +toolbar +windows
+byte_offset +cscope  +ex_extra+iconv/dyn   -lua
  +ole +reltime +syntax  +user_commands
  +writebackup
+cindent +cursorbind  +extra_search+insert_expand   +menu
 +path_extra  +rightleft   +tag_binary  +vertsplit
  -xfontset
+clientserver+cursorshape +farsi   +jumplist
 +mksession   +perl/dyn-ruby+tag_old_static
 +virtualedit -xim
+clipboard   +dialog_con_gui  +file_in_path+keymap
 +modify_fname+persistent_undo +scrollbind  -tag_any_white
+visual  -xterm_save
+cmdline_compl   +diff+find_in_path+langmap +mouse
  -postscript  +signs   -tcl +visualextra
  +xpm_w32
   system vimrc file: "$VIM\vimrc"
 user vimrc file: "$HOME\_vimrc"
 2nd user vimrc file: "$VIM\_vimrc"
  user exrc file: "$HOME\_exrc"
  2nd user exrc file: "$VIM\_exrc"
  system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -DFEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
-D_WIN32_WINNT=0x0400  /Fo.\ObjGOLHi3
86/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32 -DDYNAMIC_ICONV
-DDYNAMIC_GETTEXT -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3
 -DDYNAMIC_PYTHON3_DLL=\"python33.dll\" -DFEAT_PERL -
DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\" -DFEAT_BIG
/Fd.\ObjGOLHi386/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /LTCG:STATUS oldnames.lib
kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib ole32.lib
uuid.lib /machine:i386 /node
faultlib gdi32.lib version.lib   winspool.lib comctl32.lib advapi32.lib
shell32.lib  /machine:i386 /nodefaultlib libcmt.lib oleaut32.lib
 user32.lib   /nodefaultlib:python3
3.libWSock32.lib xpm\x86\lib\libXpm.lib /PDB:gvim.pdb -debug


With this nmake command:

C:\OpenSrc\vim\src>nmake -f Make_mvc.mak debug=no gui=yes cscope=yes
OLE=yes PYT
HON3=C:\Python33 DYNAMIC_PYTHON3=yes PYTHON3_VER=33 PERL=C:\Perl
DY

Re: Python error: E448 (Py_InitModule4) and E263

[David Fishburn]

On Wed, May 29, 2013 at 6:22 PM, Andrei Olsen wrote:

> On Wednesday, May 29, 2013 7:11:13 PM UTC+2, Axel Bender wrote:
> > I'm using gvim 7.3 (64 bits, 1036) with dynamic python 2.7 support on
> Windows 7 (64 bits). Python 2.7 (64 bits) works from the command line.
> >
> > :py print "hello" gives me
>

Windows 7 64.

:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 29 2013 18:37:51)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-1053
 +python3/dyn

Python 3.3.0

I have never used python before.

:py print "hello"
E319: Sorry, the command is not available in this version

:py3 print "hello"
  File "", line 1
print "hello"
^
SyntaxError: invalid syntax


Not sure if this is expected or not.

An aside question, if you are compiled with +python3/dyn, why wouldn't :py
just do what :py3 does?  After all, there are not 2 versions available?

:h :py, should probably also say, see :py3 if you are using python 3 as a
first time user wouldn't really understand why it didn't work.

But maybe this is obvious to python users.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Latest changes to regexengine have made vim really slow

[David Fishburn]

On Jun 2, 2013, at 6:06 AM, Axel Bender  wrote:

> Comparing versions 7.3.1078 and 7.3.1090 (both compiled by myself) show a 
> very slow behavior of the latest(?) version e.g. when paging through a file, 
> independent of the regexpengine chosen.
> 
> 
I also noticed this last night. 
When I did a:
Set re=1

No difference. 

--
David Fishburn

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [RFC] Revision of Objective-C Syntax

[David Fishburn]

...>

> > "AdjustIo.h" 81L, 2743C
> > Error detected while processing /usr/share/vim/vim73/syntax/objc.vim:
> > line6:
> > E492: Not an editor command: ^M
> > line8:
> > E15: Invalid expression: exists("b:current_syntax")^M
> > line  107:
> > E488: Trailing characters
> > line  110:
> > E171: Missing :endif
> > Press ENTER or type command to continue
> >
> > What am I doing wrong?
>
> You are trying to open file with CRLF (Windows) line endings on *nix
> (linux or Mac OS). It is not you, but sender who is doing wrong.
>
>

You can quickly work around this issue by opening the objc.vim in Vim.
 Anytime files are sent to Bram for inclusion they should be using the Unix
fileformat (ff).
:e set ff=unix
:wq

Then start Vim again and try your test.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [RFC] Revision of Objective-C Syntax

[David Fishburn]

...

> Yes the update fixed the problems. You saved it with Windows line endings
>> again though.
>>
>> I apologize to you for getting you into trouble again.  Though the file
>> itself is in unix format and I double-checked not to send window-friendly
>> attachments, my Mail did something unnecessary.
>
>
>
Kazunobu,

What do you have in your .vimrc for this setting:
fileformats

You might want to try:
set fileformats=unix,dos,mac  " Leave files in Unix format first

That way, if the file is already in unix format, leave it that way.  It
allows you to open up any of those fileformats without forcing a change
when you save them.
This means when you create a new file, it will be in Unix format first.

If you primarily work on Windows, then you might want to try this:

if has('win32') || has('win64') || has('win16') || has('win95')
set fileformats=dos,unix,mac  " Leave files in DOS format first
elseif has('mac')
set fileformats=mac,unix,dos  " Leave files in Mac format first
else
set fileformats=unix,dos,mac  " Leave files in Unix format first
endif

But then, when you create a file for Bram, make sure you change the ff=unix
once.  There after, you should never have to worry about the format
changing with the above setting.

People may have other suggestions, but this works for me.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Patch 7.3.1112

[David Fishburn]

...
> Thanks I did not know this pattern and it is very handy.  I always felt

> > that the search commands /, ? should have a range, so that one can limit
> > the search to part of a text.  What about having two commands :/
> > and :? for searches limited to the  of lines.
>
> You can use the range-search plugin
> (http://www.vim.org/scripts/script.php?script_id=1396) for that.
>

I use this one:
vis : Extended Visual Mode Commands, Substitutes, and Searches
http://www.vim.org/scripts/script.php?script_id=1195
By Dr. Chip

It creates a simple mapping // to do a range search over my highlighted
region.  I find it quite convienent.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

nfa regression with 114?

[David Fishburn]

Bram,

The most recent changes (been a few days sync I last synced) broke on of
the plugins I use.

>set re=1
>echo match('" test.vim - Test header', '\v\C%(set re=2
>echo match('" test.vim - Test header', '\v\C%(ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun  7 2013 13:21:33)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-1141
Compiled by I826639@SAP_ALL
Big version with GUI.  Features included (+) or not (-):
+arabic  +comments+eval+insert_expand
+modify_fname+printer +startuptime +toolbar
-xfontset
+autocmd +conceal +ex_extra+jumplist+mouse
  -profile +statusline  +user_commands   -xim
+balloon_eval+cryptv  +extra_search+keymap
 +mouseshape  -python  -sun_workshop+vertsplit
-xterm_save
+browse  +cscope  +farsi   +langmap
+multi_byte  +python3/dyn +syntax  +virtualedit +xpm_w32
++builtin_terms  +cursorbind  +file_in_path+libcall
+multi_lang  +quickfix+tag_binary  +visual
+byte_offset +cursorshape +find_in_path+linebreak
-mzscheme+reltime +tag_old_static  +visualextra
+cindent +dialog_con_gui  +float   +lispindent
 +netbeans_intg   +rightleft   -tag_any_white   +viminfo
+clientserver+diff+folding +listcmds+ole
  -ruby-tcl +vreplace
+clipboard   +digraphs-footer  +localmap
 +path_extra  +scrollbind  -tgetent +wildignore
+cmdline_compl   -dnd +gettext/dyn -lua
+perl/dyn+signs   -termresponse+wildmenu
+cmdline_hist-ebcdic  -hangul_input+menu
 +persistent_undo +smartindent +textobjects +windows
+cmdline_info+emacs_tags  +iconv/dyn   +mksession
-postscript  -sniff   +title   +writebackup

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

7.4a - Confirm dialog box larger than screen size

[David Fishburn]

I believe I saw this fixed earlier, or something related.

I have tested this with:
:ver
VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul  9 2013 09:34:36)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-6
Compiled by me
Big version with GUI.  Features included (+) or not (-):

Run on Windows 7 x64.

gvim.exe -u NONE -U NONE

Open Vim.
Resize Vim so that the top and bottom of the Vim window is nearly maximized.
Or
Simply maximize Vim by double clicking on the title bar.

Run the following:
:echo confirm('Test'.repeat("\nNext line", 80))

This will produce a dialog box with a scrollbar within it.
The scrolling of the items is correct.

But, there are 2 issues.

1.  Assuming your taskbar is at the default windows position (bottom of
screen) then window is much longer than than the window size.  Many of the
"Next lines" are off the screen and the OK button is no where to be seen.

2.  If you taskbar is at the top of the screen (as mine always is) then the
problem may stem from the same issue of being too large, but there is an
additional problem.  The top of the window is underneath the taskbar, so
you cannot click on it to move it.  Many of the "Next lines" are off the
screen and the OK button is no where to be seen.

Please make sure Vim has either been maximized or nearly the length of the
screen first.  If you do not, you will not see the same behaviour.  The
confirm modal window is larger than Vim, but it will not exceed screen size
if Vim isn't using most of screen real-estate.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Vim 7.4a echon - Press ENTER or type command to continue

[David Fishburn]

This sympton I was only able to reproduce on some Unix machines, I can now
produce it on Windows machines too.

If you execute this command:
let msg = "Enter character:" | echo msg | let c = getchar() | let c =
nr2char(c)
| echon c

The output you get is:
Enter character:j


Some users on different *nix machines report they get:
Enter character:
j
Press Enter or type command to continue.

Where I cannot reproduce this exactly, there is a simple variant which can
be reproduced.

gvim -u NONE -U NONE -N
:let msg = "Enter character:" | echo msg | let c = getchar() | let c =
nr2char(c)
| echon c

If the command fits on one line, I get:
Enter character:j


If you make the width of the screen smaller so that the command above (90
characters long) must wrap, when you execute it you get:
Enter character:j
Press ENTER or type command to continue.

Is this a bug or is it expected?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 7.4a - Confirm dialog box larger than screen size

[David Fishburn]

Can anyone else reproduce this?

Any GUI experts out there?

Thanks,
David


On Tue, Jul 9, 2013 at 11:13 AM, Bram Moolenaar  wrote:

>
> David Fishburn wrote:
>
> > I believe I saw this fixed earlier, or something related.
> >
> > I have tested this with:
> > :ver
> > VIM - Vi IMproved 7.4a BETA (2013 Jul 6, compiled Jul  9 2013 09:34:36)
> > MS-Windows 32-bit GUI version with OLE support
> > Included patches: 1-6
> > Compiled by me
> > Big version with GUI.  Features included (+) or not (-):
> >
> > Run on Windows 7 x64.
> >
> > gvim.exe -u NONE -U NONE
> >
> > Open Vim.
> > Resize Vim so that the top and bottom of the Vim window is nearly
> maximized.
> > Or
> > Simply maximize Vim by double clicking on the title bar.
> >
> > Run the following:
> > :echo confirm('Test'.repeat("\nNext line", 80))
> >
> > This will produce a dialog box with a scrollbar within it.
> > The scrolling of the items is correct.
> >
> > But, there are 2 issues.
> >
> > 1.  Assuming your taskbar is at the default windows position (bottom of
> > screen) then window is much longer than than the window size.  Many of
> the
> > "Next lines" are off the screen and the OK button is no where to be seen.
> >
> > 2.  If you taskbar is at the top of the screen (as mine always is) then
> the
> > problem may stem from the same issue of being too large, but there is an
> > additional problem.  The top of the window is underneath the taskbar, so
> > you cannot click on it to move it.  Many of the "Next lines" are off the
> > screen and the OK button is no where to be seen.
> >
> > Please make sure Vim has either been maximized or nearly the length of
> the
> > screen first.  If you do not, you will not see the same behaviour.  The
> > confirm modal window is larger than Vim, but it will not exceed screen
> size
> > if Vim isn't using most of screen real-estate.
>
> Perhaps the height computatins do not add the height of the buttons?
>
> --
>[The rest of the ARMY stand around looking at a loss.]
> INSPECTOR END OF FILM: (picks up megaphone) All right!  Clear off!  Go on!
>  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES
> LTD
>
>  /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
> \\\
> ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/\\\
> \\\  an exciting new programming language -- http://www.Zimbu.org
>  ///
>  \\\help me help AIDS victims -- http://ICCF-Holland.org
>  ///
>

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: 7.4a - Confirm dialog box larger than screen size

[David Fishburn]

On Wed, Jul 31, 2013 at 11:24 AM, Mike Williams <
mike.willi...@globalgraphics.com> wrote:

> On 31/07/2013 14:06, David Fishburn wrote:
>
>> Can anyone else reproduce this?
>>
>
> Yep, reproduced.  Even happens with gui VIM on linux builds and without
> increasing the window height from the default 25 lines.  No idea for other
> platforms.
>
>
>  Any GUI experts out there?
>>
>
> A quick look at the Windows code for the dialog shows it limits the
> message content of the dialog to the height of the Window used by VIM, but
> takes no account of the title bar or any buttons and title bar extending
> beyond top and bottom of the window/screen.
>
> I haven't looked at the GTK code but it would seem it has no checks at all
> on the dialog height relative to the window or screen dimensions. Other
> platforms may vary again.
>
> While not nice, what is the usage scenario where such a tall dialog is
> useful?
>
>
When using the confirm() function, you can ask the user for input.
In my particular case (dbext.vim plugin) you can create "named connection
profiles".
When you first use the plugin it will prompt you (by #) which profile you
would like to use.

This is simply generated by entries you have put in your .vimrc.

So in the end you are prompted like this:

Enter profile #:
1.  Oracle - DB_x
2.  MySQL - MythTV
3.  Sybase

Ok   Cancel

In my case, I have over 75 profiles.  The 75 lines easily create a box that
is larger than the window, so I expect it to scroll within the window.

confirm() is a nice generic way to get input, the text added can easily be
large.

Thanks for testing and confirming.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Compiler warning on Windows

[David Fishburn]

:ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 29 2015 11:12:16)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-994


ps.c
option.c
os_mswin.c
winclip.c
os_win32.c
os_win32.c(679) : warning C4996: 'GetVersionExA': was declared deprecated
C:\Program Files (x86)\Windows
Kits\8.1\include\um\sysinfoapi.h(433) : see declaration of 'GetVersionExA'
popupmnu.c

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Invalid range using 1-994

[David Fishburn]

I get this error using:

>ver
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Dec 29 2015 11:12:16)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-994
Compiled by Me
Huge version with GUI.  Features included (+) or not (-):
+acl +cmdline_hist-directx +folding
+lispindent  -mzscheme+quickfix+syntax
 +vertsplit   -xim
+arabic  +cmdline_info-dnd -footer
 +listcmds+netbeans_intg   +reltime +tag_binary
 +virtualedit -xterm_save
+autocmd +comments-ebcdic  +gettext/dyn
+localmap+ole +rightleft   +tag_old_static  +visual
 +xpm_w32
+balloon_eval+conceal +emacs_tags  -hangul_input-lua
  +path_extra  -ruby-tag_any_white   +visualextra
+browse  +cryptv  +eval+iconv/dyn   +menu
 +perl/dyn+scrollbind  -tcl +viminfo
++builtin_terms  +cscope  +ex_extra+insert_expand
+mksession   +persistent_undo +signs   -tgetent
+vreplace
+byte_offset +cursorbind  +extra_search+jumplist
 +modify_fname-postscript  +smartindent -termresponse
 +wildignore
+cindent +cursorshape +farsi   +keymap  +mouse
  +printer -sniff   +textobjects +wildmenu
+clientserver+dialog_con_gui  +file_in_path+langmap
+mouseshape  +profile +startuptime +title   +windows
+clipboard   +diff+find_in_path+libcall
+multi_byte  +python/dyn  +statusline  +toolbar
+writebackup
+cmdline_compl   +digraphs+float   +linebreak
+multi_lang  -python3 -sun_workshop+user_commands
-xfontset


I only get this error (it seems) when I open a new window at the top of the
screen.
Then I am trying to move back to the originating window.

So I have a vertical split window of which my cursor is in the right side
(2 windows).
Then I create a new horizontal window at the top (3 windows).
While in the top, I try to move back to the bottom right side:

>exec s:dbext_buffer_last_winnr . "wincmd w"
E16: Invalid range: 3wincmd w
>echo type(s:dbext_buffer_last_winnr)
0
>exec s:dbext_buffer_last_winnr . "wincmd w"
E16: Invalid range: 3wincmd w
>exec "" . s:dbext_buffer_last_winnr . "wincmd w"
E16: Invalid range: 3wincmd w
>exec 3 . "wincmd w"
E16: Invalid range: 3wincmd w
>exec "3" . "wincmd w"
E16: Invalid range: 3wincmd w
>exec "3wincmd w"
E16: Invalid range: 3wincmd w
>exec ":3wincmd w"
E16: Invalid range: :3wincmd w


If the new window is opened to the bottom of the screen instead of the top,
the command works as advertised.

Also, if I manually execute the command:
:3wincmd w

There are no errors and it does what I expect.

Any ideas?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [patch] fix possible bug in searchpair

[David Fishburn]

On Mon, Jan 11, 2016 at 3:06 PM, Christian Brabandt 
wrote:

> Bram,
> this patch fies an issue reported by David Fishburn about a misbehaving
> searchpairpos(). I traced it back to syntax.c and I think what happens
> is, that Vim gets confused about the current syntax stack. I added a
> newstyle test, that lets the problem reproduce, given the plugin from
> David. I hope it is okay, to include some plugins for the tests.
>
> I have fixed that behaviour for David back in October and haven't heard
> from him back since then. I think, this patch should be included for a
> possible vim 7.5.
> CC'ing David for his opinion.
>


Patch is working correctly and I haven't seen any of the old (wrong)
behaviour since.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugins - Vim licence?

[David Fishburn]

When plugins are developed and made available on the Vim website, do they
adopt the Vim licence?

Thanks,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fwd: clipboard=unnamedplus, v:register and yanks

[David Fishburn]

Can anyone on the dev list comment on this one?

Thanks,
Dave

 Original Message 
Subject:clipboard=unnamedplus, v:register and yanks
Date:   Tue, 20 Sep 2011 08:25:55 -0400
From:   David Fishburn 
To: vim_use 



Sorry if this shows up twice, used the wrong email account to send it 
the first time.



Vim 7.3.1-315

unnamedplusA variant of "unnamed" flag which uses the clipboard
register '+' (|quoteplus|) instead of register '*' for
all operations except yank.  Yank shall copy the text
into register '+' and also into '*' when "unnamed" is
included.
Only available with the |+X11| feature.
Availability can be checked with: >
if has('unnamedplus')

So if I read that correctly, when using unnamedplus all yank operations 
should use the '*' register and not the '+' register.


The register contents behaviour I see is also correct (will demonstrate 
below).


But what appears to be wrong is the value of v:register.

gvim -u NONE -U NONE --noplugin -N

Create a new buffer with the following lines:
1
2
3
4
5

:set clipboard=
:echo v:register
"

Go to first line, yy
:echo v:register
"
:echo @"
1

Go to 2nd line, "ayy
:echo v:register
a
:echo @"
2
:echo @a
2


Good.


:set clipboard=unnamedplus
:echo v:register
+
Go to 3rd line, yy
:echo v:register
+
:echo @"
3
:echo @+
Something else
:echo @*
Something else


Go to 4th line, dd
:echo v:register
+
:echo @"
4
:echo @+
4
:echo @*
4



So, referring back to the text again:
unnamedplusA variant of "unnamed" flag which uses the clipboard
register '+' (|quoteplus|) instead of register '*' for
all operations except yank.  Yank shall copy the text
into register '+' and also into '*' when "unnamed" is
included.


If the + and * registers are not modified by yank operations, then 
shouldn't v:register = " when yanking text (3rd line in the above 
sample).  Since @+ is not modified at all.


Thanks,
Dave


--
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 http://www.vim.org/maillist.php

Re: Fwd: clipboard=unnamedplus, v:register and yanks

[David Fishburn]

...

If the + and * registers are not modified by yank operations, then
shouldn't v:register = " when yanking text (3rd line in the above
sample). Since @+ is not modified at all.


:help v:register mentions nothing about the *effective register*, only 
the one supplied (and since 7.3.186, this considers the changed 
default for the "unnamed" and "unnamedplus" values).

v:registerThe name of the register supplied to the last normal
mode command.  Empty if none were supplied. |getreg()| |setreg()|


In my understanding, v:register is mainly necessary for custom 
operations that work with registers, not for built-in commands like 
yank. Is your inquiry about theoretical correctness, or do you have an 
actual use case that is affected by this? In the latter case, I would 
agree that v:register should account for the yank command. (But I 
don't know how easy that would be to implement.)


Then YankRing plugin 
(http://www.vim.org/scripts/script.php?script_id=1234) relies upon 
v:register to determine:

a) which register to capture changes from
b) which register to update when retrieving the next value (from the 
ring) for pasting


Unfortunately, there really is no work around for it either.

I could choose "+yy, or in this case yy.  There is no way to distinguish 
those commands.


Dave

--
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 http://www.vim.org/maillist.php

Re: added TextDeleted and TextYanked events

[David Fishburn]

I will also add this to the YankRing plugin (script #1234). 

I don't se the patch # to put a conditional check in for it. 

Could someone let me know. 

Thanks. 

--
David Fishburn


On Mar 16, 2012, at 1:28 AM, Philippe Vaucher  
wrote:

>> Do you maybe have a yankring-like plugin that makes use of the feature?
>> That could help people try it out in real-world scenarios.
> 
> Yes there is, see https://github.com/the-isz/MinYankRing.vim/tree/events
> 
> Philippe
> 
> -- 
> 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 http://www.vim.org/maillist.php

-- 
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 http://www.vim.org/maillist.php

Re: added TextDeleted and TextYanked events

[David Fishburn]

On Mar 18, 2012, at 6:16 PM, "Benjamin R. Haskell"  wrote:

> On Sun, 18 Mar 2012, David Fishburn wrote:
> 
>> I will also add this to the YankRing plugin (script #1234).
>> 
>> I don't se the patch # to put a conditional check in for it.
> 
> It hasn't been applied yet, but you shouldn't check by patch # anyway. 
> exists() can detect whether an autocommand for a particular event is 
> supported.  Use:
> 
> exists('##TextDeleted')
> 
> and
> 
> exists('##TextYanked')
> 
Perfect thanks Ben. 

--
David Fishburn

-- 
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 http://www.vim.org/maillist.php

Re: Apparent Bug with SessionLoadPost autocmd - please check and confirm for me

[David Fishburn]

On 4/14/2012 6:56 AM, Philip Morant wrote:

Hi,

I use BufExplorer.vim plugin with VIm 7.  After years of faithful
service it suddenly developed a fault for no obvious reason.  I have
traced the cause:  Vim is triggering the SessionLoadPost autocmd
whenever I press Return in the BufExplorer window in order to switch
to a new buffer.  It shouldn't do this  (it never used to).

I can reproduce this on my machine.  I start Vim with the command line
"gvim -S /home/philip/tmp/vim2.session 2>/dev/null&".  I invoke
BufExplorer with \bewww.  I select a different buffer and press
Return.  I get that buffer on-screen but BufExplorer's BEReset()
method has been called because of the spurious SessionLoadPost
autocmd, and that call to BEReset resets the MRU list.

I have two session files both of which exhibit the same problem.  So I
assume that the problem is not with the session files.


I have also run into this, though it only happens when I create the 
session with SessionMan 
(http://www.vim.org/scripts/script.php?script_id=2010) instead of the 
built in Vim command:mksession.


I am also working on all the little kinks with the plugin logic to 
address the issue and and working with Jeff (BufExplorer) author to 
include the changes in his next release.


Dave

--
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 http://www.vim.org/maillist.php

Fwd: inputdialog() should use cancel value parameter

[David Fishburn]

Any comments from the dev list?

Thanks,
Dave



 Original Message 
Subject:inputdialog() should use cancel value parameter
Date:   Tue, 10 Jul 2012 08:30:28 -0400
From:   David Fishburn 
To: vim_use 



When using
:echo inputdialog( 'What is your name?', 'Type it here', '-1' )

From gVim and you hit Esc or the Cancel button when prompted you get:
-1

:set guioptions+=c
:echo inputdialog( 'What is your name?', 'Type it here', '-1' )

and you hit Esc or CTRL-C, you get a blank value back.

This is also true if you use console vim, instead of the GUI.

This was tested using my Windows 7 box:
:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May  1 2012 21:26:33)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-515
Compiled by fishburn@FISHBURN-WIN7
Big version with GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +conceal +cryptv +cscope +cursorbind +cursorshape
+dialog_con_gui +diff +digraphs -dnd -ebcdic +emacs_tags +eval +ex_extra
+extra_search +farsi +file_in_path +find_in_path +float +folding -footer
+gettext/dyn -hangul_input +iconv/dyn +insert_expand
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
+localmap -lua +menu +mksession +modify_fname +mouse +mouseshape
+multi_byte +multi_lang -mzscheme +netbeans_intg +ole +path_extra
+perl/dyn +persistent_undo -postscript +printer -profile +python/dyn
-python3 +quickfix +reltime +rightleft -ruby +scrollbind +signs
+smartindent -sniff +startuptime +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white -tcl -tgetent -termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit
+visual +visualextra +viminfo +vreplace +wildignore +wildmenu
+windows +writebackup -xfontset -xim -xterm_save +xpm_w32


And my Ubuntu 12.04 box:
:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May  4 2012 04:10:09)
Included patches: 1-429
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by buildd@
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff
+digraphs
 +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi
+file_in_path
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds +localmap +lua +menu +mksession +modify_fname +mouse +mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm -mouse_sysmouse
+mouse_xterm
+mouse_urxvt +multi_byte +multi_lang -mzscheme +netbeans_intg
+path_extra +perl
+persistent_undo +postscript +printer +profile +python -python3 +quickfix
+reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff
+startuptime
+statusline -sun_workshop +syntax +tag_binary +tag_old_static
-tag_any_white +tcl
 +terminfo +termresponse +textobjects +title +toolbar +user_commands
+vertsplit
+virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu
+windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard
-xterm_save


Is there anyway we can get it to act the same way?

Thanks,
Dave






--
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 http://www.vim.org/maillist.php

Re: Patch 7.3.604

[David Fishburn]

On 16/07/2012 1:27 PM, Bram Moolenaar wrote:

Patch 7.3.604
Problem:inputdialog() doesn't use the cancel argument in the console.
(David Fishburn)
Solution:   Use the third argument. (Christian Brabant)
Files:  src/eval.c



I can confirm when hitting Escape on the echo inputdialog() it now 
reports -1.


Hitting CTRL-C shows nothing, but I suspect that is the desired 
behaviour, the echo is cancelled as well as the inputdialog().


Thanks for the fix.
Dave

--
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 http://www.vim.org/maillist.php

Re: [PATCH] New autocmds: OperationPending, OperationExecuted, OperationCleared

[David Fishburn]

On Wed, Oct 10, 2012 at 4:30 PM, Mohammed Chelouti  wrote:
...
> A much more elegant solution would be to have an event to be called when an
> operation is pending. I've looked at the Vim code and added the following
> three autocommands:
>
> - OperationPending: is executed when an operation is called which needs a
> motion.
>
> - OperationExecuted: is executed after the pending operation was executed
> (i.e. a motion or a second keystroke like yy, dd etc. is passed).
>
> - OperationCleared: is executed after every command that doesn't enter
> operation-pending-mode. (executed after OperationExecuted)

Mohammed,

What information is available within these events?
Usually this is through some v: scoped variable or something like
 and so on.

I would expect the usual stuff like:

v:register  - Register currently being operated on
v:operator - Current operator (i.e. "f" for cf)
v:count - Count given for the command

Right now, the YankRing plugin had to create expression maps for these
and prompt the user for the remaining part of the command.  It sounds
like I could use this feature instead of some of those maps, if the
required information is available.

Thanks,
Dave

-- 
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 http://www.vim.org/maillist.php

RE: Issue 87 in vim: Patch for /runtime/autoload/syntaxcomplete.vim

[David Fishburn]

> -Original Message-
> From: vim_dev@googlegroups.com [mailto:vim_dev@googlegroups.com] On Behalf
Of v...@googlecode.com
> Sent: October-18-12 9:27 AM
> To: vim_...@vim.org
> Subject: Re: Issue 87 in vim: Patch for
/runtime/autoload/syntaxcomplete.vim
> 
> 
> Comment #1 on issue 87 by ben...@benizi.com: Patch for  
> /runtime/autoload/syntaxcomplete.vim
> http://code.google.com/p/vim/issues/detail?id=87
> 
> Added this patch directly to issue 86.  This should be closed.

I am the maintainer of this file.

I don't really see why this is necessary.

:call search('-') works as does :call search(escape('-', '\'))

Can someone explain why is it necessary?

Thanks,
Dave


-- 
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 http://www.vim.org/maillist.php

Build issue: Cannot find xpm.h

[David Fishburn]

I use a batch file for building Vim.
Ran it last about 2 weeks ago.

Just trying to test on of Bram's patches.

I updated via:
C:\OpenSrc>"C:\Program Files\Mercurial\hg.exe" clone
https://vim.googlecode.com/hg/  vim


On Windows 7 (64-bit).
I get the following:
...
cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
-DFEAT_CSCOPE -D
FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400 -D_WIN32_WINNT=0x0400
 /Fo
.\ObjGOLYi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
-DDYNAMIC_ICO
NV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
 -DDYNAMIC_PYTHON_DLL=\"pyth
on27.dll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
-DFEAT_
BIG /Fd.\ObjGOLYi386/ /Zi -I
C:\download\OpenSrc\vim\XPM_support_for_Netbeans\xpm-4.2.0\include -I
C:\download\OpenSrc\vim\XPM_support_for_Netbeans\xpm-4.2.0\..
\include xpm_w32.c
xpm_w32.c
xpm_w32.c(31) : fatal error C1083: Cannot open include file: 'xpm.h': No
such file or directory
NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\BIN\cl.EXE"' : return code '0x2'
Stop.


So something changed in the last couple of weeks related to this?

I read up on :h configure-netbeans

On MS-Windows:
--

The Win32 support is now in beta stage.

To use XPM signs on Win32 (e.g. when using with NetBeans) you can compile
XPM by yourself or use precompiled libraries from http://iamphet.nm.ru/misc/


Those are the XPM files I am using and they are from 2004.

Any ideas?

Thanks,
Dave

-- 
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 http://www.vim.org/maillist.php

Re: Build issue: Cannot find xpm.h

[David Fishburn]

Thanks for the link Christian.

Change my env variable to:
IF NOT DEFINED VIM_XPM_DIR SET VIM_XPM_DIR=xpm\x86
from:
IF NOT DEFINED VIM_XPM_DIR SET
VIM_XPM_DIR=C:\full\path\to\file\XPM_support_for_Netbeans\xpm-4.2.0


Worked, as I build for Windows 32bit.

I haven't ventured into finding Perl and Python for 64 bit yet as I already
have to twiddle the different Perl versions on win32 to get it working.

Thanks,
David



On Tue, Nov 20, 2012 at 11:37 AM, Christian Brabandt wrote:

> On Tue, November 20, 2012 17:21, David Fishburn wrote:
> > I use a batch file for building Vim.
> > Ran it last about 2 weeks ago.
> >
> > Just trying to test on of Bram's patches.
> >
> > I updated via:
> > C:\OpenSrc>"C:\Program Files\Mercurial\hg.exe" clone
> > https://vim.googlecode.com/hg/  vim
> >
> >
> > On Windows 7 (64-bit).
> > I get the following:
> > ...
> > cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32
> > -DFEAT_CSCOPE -D
> > FEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -DWINVER=0x0400
> > -D_WIN32_WINNT=0x0400
> >  /Fo
> > .\ObjGOLYi386/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_GUI_W32
> > -DDYNAMIC_ICO
> > NV -DDYNAMIC_GETTEXT -DFEAT_PYTHON -DDYNAMIC_PYTHON
> >  -DDYNAMIC_PYTHON_DLL=\"pyth
> > on27.dll\" -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl510.dll\"
> > -DFEAT_
> > BIG /Fd.\ObjGOLYi386/ /Zi -I
> > C:\download\OpenSrc\vim\XPM_support_for_Netbeans\xpm-4.2.0\include -I
> > C:\download\OpenSrc\vim\XPM_support_for_Netbeans\xpm-4.2.0\..
> > \include xpm_w32.c
> > xpm_w32.c
> > xpm_w32.c(31) : fatal error C1083: Cannot open include file: 'xpm.h': No
> > such file or directory
> > NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual
> > Studio
> > 10.0\VC\BIN\cl.EXE"' : return code '0x2'
> > Stop.
> >
> >
> > So something changed in the last couple of weeks related to this?
> >
> > I read up on :h configure-netbeans
> >
> > On MS-Windows:
> > --
> >
> > The Win32 support is now in beta stage.
> >
> > To use XPM signs on Win32 (e.g. when using with NetBeans) you can compile
> > XPM by yourself or use precompiled libraries from
> > http://iamphet.nm.ru/misc/
> >
> >
> > Those are the XPM files I am using and they are from 2004.
> >
> > Any ideas?
>
> There were some patches, regarding an xpm header file. See the thread
> starting here:
> http://groups.google.com/group/vim_dev/msg/18797fd7a6870517
>
> See also patch 7.3.622, 7.3.639, 7.3.653 and 7.3.655
>
> regards,
> Christian
>
> --
> 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 http://www.vim.org/maillist.php
>

-- 
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 http://www.vim.org/maillist.php

Re: increase font size and you don't see the command line any more (bug?)

[David Fishburn]

On Tue, Nov 20, 2012 at 6:33 AM, Roland Puntaier
wrote:

> On 11/20/2012 12:03 PM, Bram Moolenaar wrote:
>
>> Roland Puntaier wrote:
>>
>>  One probably doesn't change the font size very often, but I recently did
>>> and
>>> could not see the command line any more. Looking into the code I've seen
>>> that vim increases the window size instead of adapting the line number,
>>> but interestingly not so for windows. I happen to use Xmonad,
>>> where window size does not change, so I first regarded this as a bug.
>>> Still the behavior seems not sensible to me. When I change the font size
>>> I don't think of changing the window size.
>>> Or: The windows size seems more important to me than the line number.
>>>
>>> If you agree, please apply the following patch:
>>>
>>> diff -r 57e8b75298d6 src/gui.c
>>> --- a/src/gui.cTue Oct 23 05:35:34 2012 +0200
>>> +++ b/src/gui.cSun Nov 18 11:34:58 2012 +0100
>>> @@ -905,13 +905,7 @@
>>># endif
>>>gui_mch_set_font(gui.norm_**font);
>>>#endif
>>> -gui_set_shellsize(FALSE,
>>> -#ifdef MSWIN
>>> -TRUE
>>> -#else
>>> -FALSE
>>> -#endif
>>> -, RESIZE_BOTH);
>>> +gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH);
>>>}
>>>
>>>return ret;
>>>
>> I can't remember why it's different for MS-Windows.  Perhaps because it
>> didn't work reliably on Unix?
>>
>> I could just include this patch and wait until someone complains...
>>
>>
>> I just tried this on Windows 7.
NOTE: My Taskbar is on the top of my screen not in the default bottom
location.

:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 20 2012 14:29:01)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-725

I started using:
gvim -u NONE -U NONE --noplugins

The moved the window down so that the bottom was near to the bottom of my
screen.  Then using the menu Edit -> Select Font -> bumped it from 9 -> 14
-> 22 and so on.

The bottom of Vim is off screen each time I increase it.

David

-- 
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 http://www.vim.org/maillist.php

Re: Errors compiling with Python 3.3 on Windows

[David Fishburn]

On Fri, Nov 23, 2012 at 1:46 AM, Ken Takata  wrote:

> Hi David,
>
> 2012/11/23 Fri 0:42:51 UTC+9 David Fishburn:
> > Python requested (version 33) - root dir is "C:\Python33"
> > Python DLL will be loaded dynamically
> > Perl requested (version 510) - root dir is "C:\Perl"
> > Perl DLL will be loaded dynamically
>
> It seems that you set PYTHON=C:\Python33 instead of PYTHON3=C:\Python33.
> If you use Python 3.x, you should set PYTHON3, PYTHON3_VER and
> DYNAMIC3_PYTHON.
>
> Yes, that was it.

Thanks Ken, up and running now.

David

-- 
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 http://www.vim.org/maillist.php

E341: Internal error: lalloc(0, )

[David Fishburn]

I was just trying some tests on my Ubuntu 12.04 box and compiled my own Vim:
Included patches: 1-729

I started Vim using:
gvim -u .vimrc -U .gvimrc --noplugin -S
/usr/share/vim/vimfiles/plugin/yankring.vim foo

"foo" [converted] 5L, 42C
Error detected while processing function 11_YRCheckClipboard:
line5:
E341: Internal error: lalloc(0, )
Error detected while processing function
11_YRFocusGained..11_YRCheckClipboard:
line5:
E341: Internal error: lalloc(0, )
Press ENTER or type command to continue


I can't reproduce this reliably, but since I compiled this myself, I should
be able to use a debug version and get a stack trace.

Unfortunately, my Linux skills are a little light.

I compiled my Vim using (note I am using lightdm window manager):
sudo ./configure --with-features=huge --enable-gui=gnome2 --prefix=/usr
--enable-perlinterp --enable-pythoninterp --enable-rubyinterp

If someone could point out how to enable debug (with Windows I just add
debug=yes with nmake) .



:ver
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 27 2012 23:20:33)
Included patches: 1-729
Compiled by root@myth
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff
+digraphs
 +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi
+file_in_path
+find_in_path +float +folding -footer +fork() +gettext -hangul_input +iconv
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse +mouseshape
+mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_sgr
-mouse_sysmouse
+mouse_urxvt +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg
+path_extra -perl +persistent_undo +postscript +printer +profile -python
-python3
 +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent -sniff
+startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static
-tag_any_white -tcl +terminfo +termresponse +textobjects +title +toolbar
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace
+wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim
+xsmp_interact
+xterm_clipboard -xterm_save
   system vimrc file: "$VIM/vimrc"
 user vimrc file: "$HOME/.vimrc"
  user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
user gvimrc file: "$HOME/.gvimrc"
system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12
-pthread -DORBIT2=1 -D_REENTRANT -I/usr/include/libgnomeui-2.0
-I/usr/include/libart-2.0 -I/usr/include/gconf/2
-I/usr/include/gnome-keyring-1 -I/usr/include/libgnome-2.0
-I/usr/include/libbonoboui-2.0 -I/usr/include/libgnomecanvas-2.0
-I/usr/include/gtk-2.0 -I/usr/include/gdk-pixbuf-2.0
-I/usr/include/gnome-vfs-2.0
-I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/dbus-1.0
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/orbit-2.0
-I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0
-I/usr/include/libxml2 -I/usr/include/pango-1.0 -I/usr/include/gail-1.0
-I/usr/include/freetype2 -I/usr/include/atk-1.0
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/cairo
-I/usr/include/gio-unix-2.0/ -I/usr/include/pixman-1
-I/usr/include/libpng12   -I/usr/local/include  -g -O2 -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1
Linking: gcc   -L/usr/local/lib -Wl,--as-needed -o vim   -lgtk-x11-2.0
-lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0
-lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0
-lglib-2.0 -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2
-lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2
-lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0
-lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype
-lfontconfig -lgconf-2 -lgthread-2.0 -lgmodule-2.0 -lrt -lgobject-2.0
-lglib-2.0   -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo
-lnsl  -lselinux -lgpm -ldl


Thanks,
David

-- 
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 http://www.vim.org/maillist.php

Re: E341: Internal error: lalloc(0, )

[David Fishburn]

On Wed, Nov 28, 2012 at 5:02 PM, Dominique Pellé
wrote:

> David Fishburn  wrote:
> ...
>


> The 'yankring.vim' file is not part of any Ubuntu package
> as far as I know. So how did it end up in /usr/share/...?
>
> Yes, I put it there.


> If you installed it yourself, it should not go in /usr/... but
> in $HOME/.vim/...
>

The reason I put it there rather than $HOME/.vim is I wanted it available
to all users on the system, not just my local account.  It is a personal
machine, and I have at least my account, root and 1 other that I routinely
log in as.


I tried to reproduce the bug but I could not.  Which version
> of the yankring plugin are you using?
>

I am the author of the plugin.  It is most likely a pre-release, which I
have been running in Windows for at least 3 months without issues.

This just showed up as I built my own gVim on Ubuntu trying to test out an
issue with 'unnamedplus'.  I have never seen something like this before
either.

The good news is it is very few files, the bad news is I still don't really
have a reproducible yet, I was waiting until I could run a debug version of
gVim to hopefully capture more information as I try to repro it.

Thanks,
David

-- 
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 http://www.vim.org/maillist.php

Re: E341: Internal error: lalloc(0, )

[David Fishburn]

...
Rebuild Vim. Then you can run Vim with gdb with a breakpoint

> when Vim gives E341:
>
> $ cd vim/src
>
> $ grep -n E341 *c
> misc2.c:902:EMSGN(_("E341: Internal error: lalloc(%ld, )"), size);
>
> $ gdb --args ./vim -f -g
>
> (gdb) br misc2.c:902
> Breakpoint 1 at 0x4eb006: file misc2.c, line 902.
> (gdb) run
>
> Then when Vim hits the breakpoint, you can type gdb command "bt"
> to get a backtrace.
>
>

For some background.
This crash only happens on Ubuntu in my case.

Clipboard must have unnamedplus in it.
I am copying Unicode characters (Chinese in this case) and flipping between
GUI Vim and Chrome.
set clipboard=unnamedplus,autoselect,exclude:cons|linux

The YankRing plugin has a Focus autocmd which checks it and if it is
different adds it to the ring.

Here is :set

:set
--- Options ---
noarabicshape hlsearchscrolloff=2   nottybuiltin
  autoindent  ignorecase  shiftwidth=4ttyscroll=0
  background=dark incsearch   shortmess=atvisualbell
  cmdheight=2 laststatus=2showbreak=>>
 whichwrap=<,>,h,l
  cursorcolumn  noloadplugins showcmd wildmenu
  cursorline  modelines=10showmatch   window=32
  expandtab   mouse=a smartcase nowritebackup
  helplang=en nrformats=hex nostartofline
  hidden  ruler   timeoutlen=3000
  history=500 scroll=15   ttimeoutlen=100
  backspace=indent,eol,start
  clipboard=unnamedplus,autoselect,exclude:cons|linux
  comments=b:#,:%,n:>
  cpoptions=aABceFs$
  fileencodings=iso-8859-15,iso-8859-3,ucs-bom,utf-8,utf-16
  fileformats=unix,dos,mac
  foldopen=block,hor,mark,percent,quickfix,search,tag,undo,jump
  formatoptions=cqtro
  grepprg=grep -nH $*
  guifont=DejaVu Sans Mono 11
  scrollopt=ver,jump,hor
  statusline= %-.50f%r%y%m B:%n%=%l,%c%V %p%%
  termencoding=utf-8
  viminfo="50,'1000,h,f1,rA:,r/tmp:,:500,/500,!,n$HOME/.viminfo




Here is the back trace.

#0  lalloc (size=0, message=1) at misc2.c:902
#1  0x00508b64 in lalloc_clear (size=0, message=1) at misc2.c:875
#2  0x00535a00 in str_to_reg (y_ptr=0x899170, yank_type=228,
str=0xc8db09 "", len=-1, blocklen=0) at ops.c:6372
#3  0x0053510a in clip_yank_selection (type=228, str=0xc8db09
"",  len=-1, cbd=0x89fbe0) at ops.c:5960
#4  0x005eb467 in selection_received_cb (widget=0xa46550,
data=0x7fffa2a0, time_=0, user_data=0x0) at gui_gtk_x11.c:1264
#5  0x76e45ca2 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x76e56d71 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x76e5f099 in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x76e5f754 in g_signal_emit_by_name ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9  0x7793b513 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#10 0x7793ef0a in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#11 0x778d6dd8 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x76e45ca2 in g_closure_invoke ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x76e57339 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x76e5ed7e in g_signal_emit_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x76e5f242 in g_signal_emit ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x779f1191 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#17 0x778d54fb in gtk_main_do_event ()
   from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#18 0x77549cac in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#19 0x76b88d53 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x76b890a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x76b89164 in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x005f2b43 in clip_mch_request_selection (cbd=0x89fbe0)
at gui_gtk_x11.c:5654
#23 0x005ca562 in clip_gen_request_selection (cbd=0x89fbe0)
at ui.c:1450
#24 0x005350a9 in clip_get_selection (cbd=0x89fbe0) at ops.c:5937
#25 0x0052b2df in may_get_selection (regname=43) at ops.c:941
#26 0x005354f4 in get_reg_contents (regname=43, allowexpr=1,
expr_src=1) at ops.c:6159
#27 0x0045ccfd in eval7 (arg=0x7fffb240, rettv=0x7fffb0f0,
evaluate=1, want_string=0) at eval.c:5111
#28 0x0045c71b in eval6 (arg=0x7fffb240, rettv=0x7fffb0f0,
evaluate=1, want_string=0) at eval.c:4810
#29 0x0045c28a in eval5 (arg=0x7fffb240, rettv=0x7fffb0f0,
evaluate=1) at eval.c:4626
#30 0x0045b689 in eval4 (arg=0x7fffb240, rettv=0x7fffb0f0,
evaluate=1) at eval.c:4319
#31 0x000

Re: Issue 96 in vim: Use of memory after free when pasting in read-only file using Perforce plugin

[David Fishburn]

On Wed, Dec 12, 2012 at 3:02 PM,  wrote:

> Updates:
> Status: Fixed
>
> Comment #6 on issue 96 by brammool...@gmail.com: Use of memory after free
> when pasting in read-only file using Perforce plugin
> http://code.google.com/p/vim/**issues/detail?id=96
>
>
I will attempt to reproduce the issue with the YankRing, and then try it
with this patch.  But so far I haven't been able to reliably reproduce the
crash.

David

-- 
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 http://www.vim.org/maillist.php

echon - Press ENTER or type command to continue

[David Fishburn]

I am seeing different behaviour (gVim or console Vim) distilled down to
this ex cmd:

:let msg = "Enter character:" | echo msg | let c = getchar() | let c =
nr2char(c) | echon c

On my Ubuntu 12.04 (Vim 7.3.pretty current) and Mac Mountain Lion (MacVim
7.3.390) box I get this output:
:Enter character:j

But I have some users reporting they get this:
:Enter character:j
Press ENTER or type command to continue

So far we see this behaviour with at least these versions:
uname -a
Linux iaintapps1 2.6.18-8.1.14.el5 #1 SMP Tue Sep 25 11:45:53 EDT 2007 i686
i686 i386 GNU/Linux
Vim 7.1.147

Linux, Slackware current and Debian Squeeze 6.0.6.
Vim 7.3.645

cmdheight = 1 in all cases, cmdheight = 2 problem goes away, but a lot of
users don't want to change this.

Can anyone think of reasons this might happen?
The screen width is far wider than the text displayed on the screen.

Originally, it seems that if TERM = *-256color that problem occurs.
So xterm-256color and screen-256color.
When TERM=xterm the problem went away sometimes, a little too inconsistent.

I am trying to get a consistent behaviour in my plugin, and will look for
work arounds in code if I can determine why it is happening.

TIA,
David

-- 
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 http://www.vim.org/maillist.php

Re: echon - Press ENTER or type command to continue

[David Fishburn]

On Dec 18, 2012, at 3:09 PM, Christian Brabandt  wrote:

> Hi David!
> 
> On Di, 18 Dez 2012, David Fishburn wrote:
> 
>> I am seeing different behaviour (gVim or console Vim) distilled down to
>> this ex cmd:
>> 
>> :let msg = "Enter character:" | echo msg | let c = getchar() | let c =
>> nr2char(c) | echon c
>> 
>> On my Ubuntu 12.04 (Vim 7.3.pretty current) and Mac Mountain Lion (MacVim
>> 7.3.390) box I get this output:
>> :Enter character:j
>> 
>> But I have some users reporting they get this:
>> :Enter character:j
>> Press ENTER or type command to continue
>> 
>> So far we see this behaviour with at least these versions:
>> uname -a
>> Linux iaintapps1 2.6.18-8.1.14.el5 #1 SMP Tue Sep 25 11:45:53 EDT 2007 i686
>> i686 i386 GNU/Linux
>> Vim 7.1.147
>> 
>> Linux, Slackware current and Debian Squeeze 6.0.6.
>> Vim 7.3.645
>> 
>> cmdheight = 1 in all cases, cmdheight = 2 problem goes away, but a lot of
>> users don't want to change this.
>> 
>> Can anyone think of reasons this might happen?
>> The screen width is far wider than the text displayed on the screen.
>> 
>> Originally, it seems that if TERM = *-256color that problem occurs.
>> So xterm-256color and screen-256color.
>> When TERM=xterm the problem went away sometimes, a little too inconsistent.
>> 
>> I am trying to get a consistent behaviour in my plugin, and will look for
>> work arounds in code if I can determine why it is happening.
> 
> Hm, could it be, that the screen size is smaller, so that the whole 
> command line wraps?
> 
> 
Good point.

I can now reproduce this on a vanilla Ubuntu 12.04 with Unity VM and the Vim 
which is in the depot. 

Yes if the ex cmd spans two lines when I execute it you will get the Press 
ENTER. 

When I shorten the cmd to fit on one line the Press ENTER went away on the good 
systems but still persists on the bad systems. 


--
David Fishburn

-- 
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 http://www.vim.org/maillist.php

Re: echon - Press ENTER or type command to continue

[David Fishburn]

These machines are both running on Ubuntu 12.04, though with different
window managers.
I used the console version to generate this output.
The same behaviour is shown when using the GUI version.


Here is a side by side comparison from the :ver output.

Right side, there is no Press ENTER prompt:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Nov 27 2012 23:20:33)
Included patches: 1-729
Compiled by root@myth
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):


Left side there is a Press ENTER prompt:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May  4 2012 04:10:09)
Included patches: 1-429
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by buildd@
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):



Just below I show you the differences between them

-- Works  -- Press ENTER prompt
+arabic   +arabic
+autocmd  +autocmd
+balloon_eval +balloon_eval
+browse   +browse
++builtin_terms   ++builtin_terms
+byte_offset  +byte_offset
+cindent  +cindent
+clientserver +clientserver
+clipboard+clipboard
+cmdline_compl+cmdline_compl
+cmdline_hist +cmdline_hist
+cmdline_info +cmdline_info
+comments +comments
+conceal  +conceal
+cryptv   +cryptv
+cscope   +cscope
+cursorbind   +cursorbind
+cursorshape  +cursorshape
+dialog_con_gui   +dialog_con_gui
+diff +diff
+digraphs +digraphs
+dnd  +dnd
-ebcdic   -ebcdic
+emacs_tags   +emacs_tags
+eval +eval
+ex_extra +ex_extra
+extra_search +extra_search
+farsi+farsi
+file_in_path +file_in_path
+find_in_path +find_in_path
+float+float
+folding  +folding
-footer   -footer
+fork()   +fork()
+gettext  +gettext
-hangul_input -hangul_input
+iconv+iconv
+insert_expand+insert_expand
+jumplist +jumplist
+keymap   +keymap
+langmap  +langmap
+libcall  +libcall
+linebreak+linebreak
+lispindent   +lispindent
+listcmds +listcmds
+localmap +localmap
-lua  +lua
+menu +menu
+mksession+mksession
+modify_fname +modify_fname
+mouse+mouse
+mouseshape   +mouseshape
+mouse_dec+mouse_dec
+mouse_gpm+mouse_gpm
-mouse_jsbterm-mouse_jsbterm
+mouse_netterm+mouse_netterm
+mouse_sgr
-mouse_sysmouse   -mouse_sysmouse
+mouse_urxvt  +mouse_xterm
+mouse_xterm  +mouse_urxvt
+multi_byte   +multi_byte
+multi_lang   +multi_lang
-mzscheme -mzscheme
+netbeans_intg+netbeans_intg
+path_extra   +path_extra
-perl +perl
+persistent_undo  +persistent_undo
+postscript   +postscript
+printer  +printer
+profile  +profile
-python   +python
-python3  -python3
+quickfix +quickfix
+reltime  +reltime
+rightleft+rightleft
-ruby +ruby
+scrollbind   +scrollbind
+signs+signs
+smartindent  +smartindent
-sniff-sniff
+startuptime  +startuptime
+statusline   +statusline
-sun_workshop -sun_workshop
+syntax   +syntax
+tag_binary   +tag_binary
+tag_old_static   +tag_old_static
-tag_any_white-tag_any_white
-tcl  +tcl
+terminfo +terminfo
+termresponse +termresponse
+textobjects  +textobjects
+title+title
+toolbar  +toolbar
+user_commands+user_commands
+vertsplit+vertsplit
+virtualedit  +virtualedit
+visual   +visual
+visualextra  +visualextra
+viminfo  +viminfo
+vreplace +vreplace
+wildignore   +wildignore
+wildmenu +wildmenu
+windows  +windows
+writebackup  +writebackup
+X11  +X11
-xfontset -xfontset
+xim  +xim
+xsmp_interact+xsmp_interact
+xterm_clipboard  +xterm_clipboard
-xterm_save   -xterm_save

Out of the above list here are the differences:
-lua  +lua
+mouse_sgr
-perl +

Re: New feature: absolute line number in relativenumber for the current line

[David Fishburn]

On Thu, Jan 31, 2013 at 7:42 PM, Charles E Campbell <
drc...@campbellfamily.biz> wrote:

> Ben Fritz wrote:
>
>> I only rarely edit files with 1 or more lines. Most of the time for
>> me, my 'rnu' column takes 4 columns, and my 'nu' column takes 5. I don't
>> care about the extra width, and would probably never turn off the option to
>> show the absolute number on the current line if there were such an option.
>> I'd support doing it that way always, but I'd accept an option as well.
>>
>>  When some users of some simulation s/w I helped write have a problem, I
> usually end up with 10-150G long debugging traces; I usually break these up
> into 1G chunks and "edit" (more usually, examine) these.  So I often end up
> with files having considerably more than 10,000 lines in them.  Since the
> patch has been accepted which installs the current line number, I'll
> probably just use my RltvNmbr plugin instead.
>
>
> I am in this exact situation:

wc -l xaa2.sql
19,461,476 xaa2.sql

I think the patch should be "smart" enough.
If the current line number exceeds available space, simply put a 0.
If it will fit in the space alloted, put the current line number.

Maybe it already does this?

My 2 cents.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [vim/vim] Is it very difficult to hide cmd window when calling 'system()' on windows ? (#922)

[David Fishburn]

On Thu, Jul 14, 2016 at 4:02 AM, Linwei  wrote:

> Taglist (or tagbar) is the top-1 rated plugin in vim.org, many windows
> gvim users are using it in their every day work. But the system() window
> (Taglist using system() to invoke ctags.exe) will pop up on the windows
> taskbar each time when a new file is open or a file is closed, which is
> very annoying:
>
> As system() is a very commonly used function in many plugins.
>
> I wonder is there a irresistible reason to show that cmd window on windows
> taskbar ?
> Why invoking system() can be slient in other vim/gvim versions ?
> Is it possible to hide the cmd window on windows taskbar ?
> Can we choose some alternative apis like WinExec(..., SW_HIDE) to solve
> this problem ?
> Or at least can we add an option to system() on windows to use SW_HIDE ?
>
> Could system() on windows become as smooth as other versions some day ?
>

I am on the fence on this one.
If Vim shells out to run something and that something is taking a _very_
long time, your Vim is essentially hung.
This happens to me frequently.
At least with the Window there, I can close it, which returns an error to
Vim (via the system() call) and I get my Vim back.
Without that I have to terminate Vim, and that is a real pain.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.2231

[David Fishburn]

On Sat, Aug 20, 2016 at 12:37 PM, Bram Moolenaar  wrote:

>
> Patch 7.4.2231
> Problem:":oldfiles" output is a very long list.
> Solution:   Add a pattern argument. (Coot, closes #575)
>
>
I was wondering if something similar to this could be added to the :let
command (though it has a lot of permutations).

I can do the following:
:let g:

I would love to do the following:
:let g:loaded_db\w\+

And return only those matching variables.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Patch 7.4.2231

[David Fishburn]

>
> >
> > I can do the following:
> > :let g:
> >
> > I would love to do the following:
> > :let g:loaded_db\w\+
> >
> > And return only those matching variables.
> >
> > David
>
> Indeed this might be useful.  You can do
>
> :let g:loaded_db
>
> One of my plugins does this, so I don't believe that would be an option.

Thanks for the input.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

has('channel')

[David Fishburn]

Just reading through channel.txt and noticed there is not reference to how
to check if Vim supports channels or not for jobs.

Perhaps the samples in there should have:

if has('channel')
...
endif

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] defaults.vim overwrites /etc/vimrc (#1033)

[David Fishburn]

On Fri, Sep 2, 2016 at 4:24 PM, Christian Hesse 
wrote:

> Since version 7.4.2111 we load a less conservative defaults.vim file if
> ~/.vimrc is not found. These options can not be overwritten from global
> /etc/vimrc.
> For example the new defaults enable mouse integration. To disable mouse
> integration I have to create ~/.vimrc for every user. I can *not* disable
> mouse integration from /etc/vimrc.
>
> IMHO /etc/vimrc should have precedence to the default settings.
>
>
I second this on my *nix systems, I only create a vimrc (no .vimrc) so that
I get the same settings for each and every user on the machine.

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Is it possible that vim support php like Python? (#1172)

[David Fishburn]

>
> ...
>
Did anybody see any Perl, Lua, or TCL vim plugin lately?
>
>
> I am a regular use of Vim's Perl interface.

When I last checked, Perl still has features (DBI - database interface, in
this case) which Python just doesn't have.
Python may have created a specification for it, but if no one has
implemented it for the myriad of databases out there, it is essentially
useless.

My 2 cents.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

[David Fishburn]

> You don't like the maintainer model; I differ.  Many times I have had to 
> reject
incorrect changes;

Totally agree.



On Wed, Nov 9, 2016 at 12:48 PM, Charles E Campbell <
drc...@campbellfamily.biz> wrote:

> mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for  a long time. Most of
> operations which use Windows commands of cmd.exe doesn't work because netrw
> checks the command exists by executable(). The commands are defined like:
> >
> > let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"
> >
> > So executable() always return 0 on Windows.
> >
> > And I met more bugs about netrw.
> >
> > * mz (decompress) doesn't work
> > * documentation bug about ms
> >
> > I'm sorry but I say netrw is often buggy. But I want to fix them. So I
> hope you that put the code of netrw on github or somewhere. And please
> permit us to modify the code of netrw for vim-dev or vim-jp.
> >
> What do you have  g:netrw_compress  and g:netrw_decompress set to?
> Windows does not provide such commands; one needs to install them and
> tell netrw (via those settings) how to invoke them.
>
> You don't like the maintainer model; I differ.  Many times I have had to
> reject incorrect changes; the latest rejection was to the documentation
> (for the production of :Lexplore windows being affected by
> g:netrw_browse_split).  If you have suggestions, please send them to
> me.  If you have error reports, please send them to me.  The more
> information the better (ie. "netrw is buggy" is worthless) - give
> commands that can invoke the problem, and mention what o/s  is in use
> (also read :help netrw-debug).  Have a patch?  Send them to me (along
> with what it fixes, commands to illustrate, etc).
>
> Chip Campbell
>
> --
> --
> 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 http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why make visual mode default? This editor is now useless to me.

[David Fishburn]

On Wed, Dec 21, 2016 at 11:37 AM, Ervin Ruci  wrote:

> After your recent update the behavior of the mouse changed.
>
> Selecting some text with the mouse automatically enters visual mode. I
> rarely use the visual feature and when I use it I prefer using the v
> keyboard command.
>
> This new setting is pretty annoying and it is hard to turn off. Why did
> you break a previously functioning editor? You just wasted a few hours of
> my time for no good reason.
>
>
Merry Christmas.

Are you asking for help, or did you manage to disable the visual mode and
get the editor back the way you like it?

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

job_info returns invalid JSON

[David Fishburn]

Running on Windows using:

:ver
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-233

job_info(...) returned the following:

{
'status': 'run',
'stoponexit': 'term',
'exitval': 0,
'exit_cb': 0,
'channel': channel 0 open,
'process': 10912
}

This should be in quotes:
channel 0 open

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: job_info returns invalid JSON

[David Fishburn]

On Fri, Jan 27, 2017 at 8:42 PM, Nikolay Aleksandrovich Pavlov <
zyx@gmail.com> wrote:

> 2017-01-28 4:33 GMT+03:00 David Fishburn :
> > Running on Windows using:
> >
> > :ver
> > VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jan 24 2017 13:37:57)
> > MS-Windows 32-bit GUI version with OLE support
> > Included patches: 1-233
> >
> > job_info(...) returned the following:
> >
> > {
> > 'status': 'run',
> > 'stoponexit': 'term',
> > 'exitval': 0,
> > 'exit_cb': 0,
> > 'channel': channel 0 open,
> > 'process': 10912
> > }
> >
> > This should be in quotes:
> > channel 0 open
>
> It should not, it is not a string. What are you trying to do?
>
>
I was trying to get access to "exitval" and thought I could do it with the
new json stuff.

So I was experimenting:


>echo job_info(s:dbext_job)
{'status': 'run', 'stoponexit': 'term', 'exitval': 0, 'exit_cb': 0,
'channel': channel 1 open, 'process': 3524}

>echo json_decode(job_info(s:dbext_job))
Error detected while processing function 83_DB_runCmdJobUpdateStatus:
line1:
E731: using Dictionary as a String
v:none

>echo string(json_decode(job_info(s:dbext_job)))
E731: using Dictionary as a String
v:none

Thought it might have been happening due to invalid JSON.

Thanks for your response.
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [bug] Exiting insertion mode with C-c extremely slow when file extension is .sql

[David Fishburn]

On Fri, Mar 3, 2017 at 9:23 AM, 'Jürgen Krämer' via vim_dev <
vim_dev@googlegroups.com> wrote:

>
> Hi,
>
> Grégoire Verdier schrieb am 03.03.2017 um 13:32:
> > Hi !
> > I'm using C-c instead of Esc and I've recently faced a problem when
> editing sql files.
> >
> > Whenever I press C-c to exit the insertion mode, it takes at least 2 or
> 3 seconds.
> >
> ...
>


> the standard SQL filetype plugin defines some insert mode mappings that
> start with . You can see them with
>
>   :verb imap 
>
> When you press  Vim waits for another key press in case you wanted
> to enter one of those mappings. If the 'timeout' option is set Vim will
> stop waiting for another key press after 'timeoutlen' milliseconds.
>
> If you don't use those mappings you can undefine them with
>
>   iunmap R
>   iunmap L
>   ...
>
> in a ~/.vim/after/ftplugin/sql.vim file.
>
>
Another option is to choose a key other than CTRL-C.

" Key to trigger SQL completion
if !exists('g:ftplugin_sql_omni_key')
let g:ftplugin_sql_omni_key = ''
endif


So, in your .vimrc, choose a different key.  Problem is, Vim uses most of
them.

HTH,
David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: added TextDeleted and TextYanked events

[David Fishburn]

>
> ...



> I don't personally feel the need for one, but I know many people would
> like a "yank ring" style of plugin or other sort of clipboard management
> which this patch would enable.
>
>
FYI:

YankRing.vim : Maintains a history of previous yanks, changes and deletes
http://www.vim.org/scripts/script.php?script_id=1234

David

-- 
-- 
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 http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: bad default shellxquote in Widows

[David Fishburn]

On Thu, Nov 6, 2008 at 12:58 PM, Ben Fritz <[EMAIL PROTECTED]> wrote:
>
> On Nov 4, 3:08 pm, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>>
...
> Plugins are another question though. For testing, I placed my proposed
> values of shellxquote and shellcmdflag in my vimrc, and immediately
> broke the TagList plugin.
>
> This seems to be caused by a bug in TagList, actually. I don't think
> the following code is needed, and it is the root of the bug. But, I'm
> not actually sure what the intent of it is:
>
>if &shellxquote == '"'
>" Double-quotes within double-quotes will not work in the
>" command-line.If the 'shellxquote' option is set to double-
> quotes,
>" then escape the double-quotes in the ctags command-line.
>let ctags_cmd = escape(ctags_cmd, '"')
>endif
>
> Later (in Windows), Taglist writes ctags_cmd to a temporary batch file
> and executes the batch file with system().

I am the one who supplied the code to Yegappan to create the ctags_cmd file.

This is not just affecting Vim, it seems cmd.exe will not execute
commands with more than 1 set of double quotes.  I guess you are
saying above, you can by simply doubling up the first and the last.

Gee, I wish I had figured that our earlier.  I have had to do the old
cmd file for several different projects (unrelated to Vim).

Dave

--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---

Re: How can I send a patch?

[David Fishburn]

On Fri, Nov 7, 2008 at 2:19 AM, François Ingelrest
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Nov 6, 2008 at 23:36, Roberto Miura Honji <[EMAIL PROTECTED]> wrote:
>>  - Auto-complete using a tab key (like ctrl-p).
>>  - When the word have a '/' (linux separator of directories) auto-complete
>> like a file (ctrl-x ctrl-f).
>>  - When the list search is returned, the tab can be used to scroll through
>> the list.
>>  - when the previous char is space, tab, the cursor position is a col = 0 or
>> ctrl-x ctrl-i is typed, the char tab is insert normally)
>
> Maybe I didn't get what you mean, but 1, 3, and 4 can already be done
> using the right mappings. I actually use something similar in my own
> setup. Regarding 2, I think this should also be quite easy to do
> without modifying Vim source code.

That is true and I have also installed some plugins to give me the
same functionality.

But, if this change is simple (I never look at the Vim code) it might
be worthwhile for the greater community.  Before I installed these
plugins I didn't know what Vim could do.  Those types of changes have
made it very useful and there are still many many Vim users which:
a) do not install plugins
b) are not allowed to install plugins
c) lack the experience to look for and install plugins to help them

These are useful features.

Having said that, I don't know if:
a) This would interfere with other features.
b) Whether we would then need some options to disable this which of
course Bram would kbosh.

Dave

--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---