A followup:
if I compile using DYNAMIC_PYTHON=no instead of yes
make -f Make_cyg.mak CC=x86_64-w64-mingw32-gcc RC=x86_64-w64-mingw32-windres
ARCH=x86-64 PYTHON=/cygdrive/c/Python27_64 PYTHON_VER=27 DYNAMIC_PYTHON=no
PERL=/cygdrive/c/Perl64 PERL_VER=516 DYNAMIC_PERL=yes -j5 GUI=yes
the linking s
Hi Ken,
> $ make -f Make_cyg.mak CC=x86_64-w64-mingw32-gcc
> RC=x86_64-w64-mingw32-windres ARCH=x86-64 GUI=yes
this command works well and I can build gvim with it.
I was trying to compile vim using perl and python.
I have perl in c:\perl64 and python in c:\python27_64
I can compile fine usin
The documentation explicitly states that moving the cursor is okay in
an indentexpr, but this is only true when moved directly with cursor(),
setpos(), search(), etc. Moving the cursor via `normal! w` has side
effects that frustrate the attempts of get_expr_indent() to restore the
original cursor p
On Sat, Feb 9, 2013 at 12:36 AM, Cesar Romani wrote:
> I'm building vim on Windows 7 with MinGW.
> It cannot be compiled with racket 4.2 anymore.
>
Racket 4.2.3 works fine for me with gcc-3.4.5 and 4.5.2. Tried both 3m and
conservative GC versions.
If you want it fixed please provide more informa
I'm building vim on Windows 7 with MinGW.
It cannot be compiled with racket 4.2 anymore.
It used to get compiled before patch 7.3.791
Now I always get:
[...]
if_mzsch.c: In function 'window_new':
if_mzsch.c:1782:21: error: lvalue required as left operand of assignment
if_mzsch.c: In function 'buf
Bram Moolenaar wrote:
Ilya Esteban wrote:
[snip]
2) If you use a plugin or a customization that visually shows the
marks, you end up with visual garbage in your files (the old tags),
that you cant get rid of unless you delete viminfo or reuse the marks
in a different file.
Solving this proper
Hi Jorge,
2013/02/08 Fri 14:59:15 UTC+9 skeept wrote:
> I just recently got a laptop where I don't have visual studio.
> I would like to compile vim using cygwin/mingw.
> I use
> make -f Make_cyg.mak CC=x86_64-w64-mingw32-gcc ARCH=x86-64 GUI=yes
>
> It all seems fine until the linking step. I t
> This was broken by a change in syntax/perl.vim in changeset c9022997af9e.
> There's a bug report upstream,
> https://github.com/vim-perl/vim-perl/issues/40, but no resolution do far.
>
> There was a suggestion this may be a bug in Vim, and the topic was raised
> previously on this list,
> http://
Even an easier test:
1. Open a C file
2. Open another C file in another tab
3. :echo bufwinnr('*.c') -> -1. Wrong.
2013/2/8 Alexey Radkov
> Hi,
>
> :help bufwinnr says:
>
> "Only deals with the current tab page."
>
> Recently i found that this behaviour is broken if the argument of
> bufwinnr(
