Re: [vim/vim] I'm sad to hear the news. (Discussion #12737)

2023-08-28 Fir de Conversatie skeept 
I am just someone that followed the discussion google mailing lists. I 
guess the reason I did is because I always found the community to be trying 
to help each other and Bram always caring about vim and the users.
Another recurring thing I remember was someone sending some patch he would 
just find some ingenious (often simpler) way of fixing the same thing.




On Sunday, August 27, 2023 at 5:06:48 AM UTC-5 ole12138 wrote:

> RIP Bram. Thank you for your awesome VIM.
>
> —
> Reply to this email directly, view it on GitHub 
> .
>
> You are receiving this because you commented.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/49f19967-135c-48ce-ae21-4be98ab41916n%40googlegroups.com.

Re: Ruby for MSVC?

2013-08-12 Fir de Conversatie skeept 
On Monday, August 12, 2013 12:54:32 PM UTC-6, tux. wrote:
 Hi,
 
 
 
 I've seen that Ruby 2.0.0 is out. I thought I could include it with my
 
 Vim builds. Where can I find a MSVC-compatible version? Ruby itself
 
 only supports MingW.

Please check this thread:
https://groups.google.com/forum/#!search/skeept$20ruby/vim_dev/P8l30hk9hyE/-foxzWPPJxsJ

Andrei Olsen has explained there how to build ruby with visual studio and I can 
confirm it works as I am using it now.

Regards

-- 
-- 
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.

Issue compiling vim in windows: coof invalid

2013-07-10 Fir de Conversatie skeept 
I am trying to compile vim in windows7 and I am getting and error. 
There are some conversion warnings during compilation but all files compile. 
When linking I get the error that follows below. 
I am using visual studio 10 to compile vim.
 

   cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE 
-DFEAT_NETBEANS_INTG  -DWINV
ER=0x0500 -D_WIN32_WINNT=0x0500  /Fo.\ObjGOULYRAMD64/ /Ox /GL -DNDEBUG  /Zl /MT 
-DFEAT_OLE -DFEAT_MBYTE_IME -D
DYNAMIC_IME -DGLOBAL_IME -DFEAT_MBYTE -DFEAT_GUI_W32 -DDYNAMIC_ICONV 
-DDYNAMIC_GETTEXT -DFEAT_LUA -DDYNAMIC_LU
A  -DDYNAMIC_LUA_DLL=\lua52.dll\ -DFEAT_PYTHON -DDYNAMIC_PYTHON  
-DDYNAMIC_PYTHON_DLL=\python27.dll\ -DFEA
T_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_RUBY 
-DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=20  -DD
YNAMIC_RUBY_DLL=\x64-msvcr100-ruby200.dll\ -DFEAT_HUGE /Fd.\ObjGOULYRAMD64/ 
/Zi version.c
version.c
link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe 
.\ObjGOULYRAMD64\blowfish.obj  .\O
bjGOULYRAMD64\buffer.obj  .\ObjGOULYRAMD64\charset.obj  
.\ObjGOULYRAMD64\diff.obj  .\ObjGOULYRAMD64\digraph.ob
j  .\ObjGOULYRAMD64\edit.obj  .\ObjGOULYRAMD64\eval.obj  
.\ObjGOULYRAMD64\ex_cmds.obj  .\ObjGOULYRAMD64\ex_cmd
s2.obj  .\ObjGOULYRAMD64\ex_docmd.obj  .\ObjGOULYRAMD64\ex_eval.obj  
.\ObjGOULYRAMD64\ex_getln.obj  .\ObjGOULY
RAMD64\fileio.obj  .\ObjGOULYRAMD64\fold.obj  .\ObjGOULYRAMD64\getchar.obj  
.\ObjGOULYRAMD64\hardcopy.obj  .\O
bjGOULYRAMD64\hashtab.obj  .\ObjGOULYRAMD64\main.obj  .\ObjGOULYRAMD64\mark.obj 
 .\ObjGOULYRAMD64\mbyte.obj  .
\ObjGOULYRAMD64\memfile.obj  .\ObjGOULYRAMD64\memline.obj  
.\ObjGOULYRAMD64\menu.obj  .\ObjGOULYRAMD64\message
.obj  .\ObjGOULYRAMD64\misc1.obj  .\ObjGOULYRAMD64\misc2.obj  
.\ObjGOULYRAMD64\move.obj  .\ObjGOULYRAMD64\norm
al.obj  .\ObjGOULYRAMD64\ops.obj  .\ObjGOULYRAMD64\option.obj  
.\ObjGOULYRAMD64\os_mswin.obj  .\ObjGOULYRAMD64
\winclip.obj  .\ObjGOULYRAMD64\os_win32.obj  .\ObjGOULYRAMD64\pathdef.obj  
.\ObjGOULYRAMD64\popupmnu.obj  .\Ob
jGOULYRAMD64\quickfix.obj  .\ObjGOULYRAMD64\regexp.obj  
.\ObjGOULYRAMD64\screen.obj  .\ObjGOULYRAMD64\search.o
bj  .\ObjGOULYRAMD64\sha256.obj  .\ObjGOULYRAMD64\spell.obj  
.\ObjGOULYRAMD64\syntax.obj  .\ObjGOULYRAMD64\tag
.obj  .\ObjGOULYRAMD64\term.obj  .\ObjGOULYRAMD64\ui.obj  
.\ObjGOULYRAMD64\undo.obj  .\ObjGOULYRAMD64\window.o
bj  .\ObjGOULYRAMD64\vim.res .\ObjGOULYRAMD64\dimm_i.obj 
.\ObjGOULYRAMD64\glbl_ime.obj .\ObjGOULYRAMD64\gui.ob
j  .\ObjGOULYRAMD64\gui_beval.obj  .\ObjGOULYRAMD64\gui_w32.obj  
.\ObjGOULYRAMD64\os_w32exe.obj .\ObjGOULYRAMD
64\if_ole.obj  .\ObjGOULYRAMD64\if_lua.obj  .\ObjGOULYRAMD64\if_perl.obj 
.\ObjGOULYRAMD64\if_perlsfio.obj .\Ob
jGOULYRAMD64\if_python.obj  .\ObjGOULYRAMD64\if_ruby.obj
.\ObjGOULYRAMD64/if_cscope.obj .\ObjGOULYRAMD64/ne
tbeans.obj   .\ObjGOULYRAMD64\version.obj oldnames.lib kernel32.lib 
advapi32.lib shell32.lib gdi32.lib  comdlg
32.lib ole32.lib uuid.lib /machine:AMD64 /nodefaultlib gdi32.lib version.lib   
winspool.lib comctl32.lib advap
i32.lib shell32.lib  /machine:AMD64 /nodefaultlib libcmt.lib oleaut32.lib  
user32.lib   /nodefaultlib:lua52.li
b   /nodefaultlib:python27.lib WSock32.lib  /PDB:gvim.pdb -debug
Generating code
  100%   0 seconds remaining
Finished generating code
LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or 
corrupt
NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\BIN\x86_amd64\link.EXE' :
 return code '0x463'
Stop.

Any idea on why this happens? I used to be able to compile vim with exactly the 
same settings I have now.

Regards,
Jorge

-- 
-- 
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] Store vimrc and gvimrc in your ~/.vim, ~\vimfiles\ directory

2013-06-04 Fir de Conversatie skeept 
On Monday, April 15, 2013 6:49:57 AM UTC-5, Bram Moolenaar wrote:
 Lech Lorens wrote:
 
 
 
  On 13-Apr-2013 Bram Moolenaar wrote:
 
   Thanks.  Thus only when ~/.vimrc does not exist then ~/.vim/vimrc will
 
   be used.  That should work for places where a new Vim is installed.  For
 
   older Vim versions one would have to create a ~/.vimrc file that sources
 
   ~/.vim/vimrc.
 
  
 
  Do we want to change the priority? I meant not to confuse people if by 
 
  any chance they have both ~/.vimrc and ~/.vim/vimrc.
 
 
 
 In my opinion, when a user sees a ~/.vimrc he expects it to be used and
 
 would be very surprised when it is skipped.  That is both for existing
 
 Vim users and any generic Unix user.  Far fewer people would know about
 
 the possibility for a ~/.vim/vimrc to exist.
 
 

I don't remember if the patch discussed in this thread made it vim already...
If not is it to late to include for 7.4?

Regards,

Jorge

-- 
-- 
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: Windows doesn't support -f option

2013-05-26 Fir de Conversatie skeept 
On Friday, May 24, 2013 2:15:36 PM UTC-5, skeept wrote:
 On Friday, May 24, 2013 10:07:09 AM UTC-5, Andrei Olsen wrote:
 
  kl. 04:17:42 UTC+2 mandag 20. mai 2013 skrev Ben Fritz følgende:
 
  
 
   I'm using the Vim without Cream build, version 7.3.822, on Windows 7 
   64-bit.
 
  
 
   
 
  
 
   And cmd.exe really does stop responding when I pass gvim the -f flag. No 
   prompt appears until Vim closes. Any typing done in the cmd.exe window 
   does not appear until Vim closes. When Vim closes, any text typed while 
   Vim was open does appear on the command line.
 
  
 
  
 
  
 
  
 
  
 
  I'm a bit baffled as why it works for you. I tried Vim without Cream 
  build 822 and 829 and none of them stop when I pass -f flag from Windows 
  command prompt (cmd.exe).
 
  
 
  
 
  
 
  I should add that -f works fine with any build if I start it from MSYS 
  shell.
 
 
 
 I compiled my own vim in windows with visual studio and -f works fine.
 
 This is the output of version:
 
 VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 22 2013 17:58:33)
 
 MS-Windows 64-bit GUI version with OLE support
 
 Included patches: 1-944
 
 Compiled by skeept@GLOBAL
 
 Huge version with GUI.  Features included (+) or not (-):
 
 +arabic +digraphs   +libcall+printer  
   -tgetent
 
 +autocmd-dnd+linebreak  +profile  
   -termresponse
 
 +balloon_eval   -ebcdic +lispindent +python/dyn   
   +textobjects
 
 +browse +emacs_tags +listcmds   -python3  
   +title
 
 ++builtin_terms +eval   +localmap   +quickfix 
   +toolbar
 
 +byte_offset+ex_extra   +lua/dyn+reltime  
   +user_commands
 
 +cindent+extra_search   +menu   +rightleft
   +vertsplit
 
 +clientserver   +farsi  +mksession  +ruby/dyn 
   +virtualedit
 
 +clipboard  +file_in_path   +modify_fname   +scrollbind   
   +visual
 
 +cmdline_compl  +find_in_path   +mouse  +signs
   +visualextra
 
 +cmdline_hist   +float  +mouseshape +smartindent  
   +viminfo
 
 +cmdline_info   +folding+multi_byte_ime/dyn -sniff
   +vreplace
 
 +comments   -footer +multi_lang +startuptime  
   +wildignore
 
 +conceal+gettext/dyn-mzscheme   +statusline   
   +wildmenu
 
 +cryptv -hangul_input   +netbeans_intg  -sun_workshop 
   +windows
 
 +cscope +iconv/dyn  +ole+syntax   
   +writebackup
 
 +cursorbind +insert_expand  +path_extra +tag_binary   
   -xfontset
 
 +cursorshape+jumplist   +perl/dyn   +tag_old_static   
   -xim
 
 +dialog_con_gui +keymap +persistent_undo-tag_any_white
   -xterm_save
 
 +diff   +langmap-postscript -tcl  
   -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  -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 
  /Fo.\ObjGOULYRAMD64/ /Ox /GL -DNDEBUG  /Zl /MT -DFEAT_OLE -DFEAT_MBYTE_IME 
 -DDYNAMIC_IME -DGLOBAL_IME -DFEAT_MBYTE -DFEAT_GUI_W32 -DDYNAMIC_ICONV 
 -DDYNAMIC_GETTEXT -DFEAT_LUA -DDYNAMIC_LUA  -DDYNAMIC_LUA_DLL=\lua52.dll\ 
 -DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\ 
 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_RUBY 
 -DDYNAMIC_RUBY -DDYNAMIC_RUBY_VER=20 
 -DDYNAMIC_RUBY_DLL=\x64-msvcr100-ruby200.dll\ -DFEAT_HUGE 
 /Fd.\ObjGOULYRAMD64/ /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:AMD64 /nodefaultlib gdi32.lib version.lib   winspool.lib 
 comctl32.lib advapi32.lib shell32.lib  /machine:AMD64 /nodefaultlib 
 libcmt.lib oleaut32.lib  user32.lib   /nodefaultlib:lua52.lib   
 /nodefaultlib:python27.lib WSock32.lib  /PDB:gvim.pdb -debug
 
 
 
 
 
 and the script I use to build vim is:
 
 
 
 @echo off
 
 rem To be used on MS-Windows for Visual C++ 2010 Express Edition
 
 rem aka Microsoft Visual Studio 10.0.
 
 rem See INSTALLpc.txt for information.
 
 REM inspired in 
 https://bitbucket.org/rko/vim/src/5e5285bfe982bfc5dbf5dce3a3541b0d3b8f22e7/src/_msvc.bat?at=default
 
 REM
 
 REM to compile GvimExt/... should specify CPU=AMD64 after calling this file 
 once

Re: [PATCH] Fix compilation failure with Ruby 2.0.0

2013-05-21 Fir de Conversatie skeept 
 
 
 
 Thanks.  I hope a few people can try it out.
 
 

Was this patch applied already? 

I tried compiling a 64 bit windows but if failed complaining that some include 
file could not be found.

If possible could this patch be included for the next release?
A small example on how to use rubydo (similar to the example on how to use 
perldo) would be useful for people like me, that don't know much about ruby but 
would like to learn.

Also for the next release, if possible would it be possible to distribute a 64 
bit for windows as well a 32 bit? 

Thanks!

-- 
-- 
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] Fix compilation failure with Ruby 2.0.0

2013-05-21 Fir de Conversatie skeept 
 
  Was this patch applied already? 
 
  
 
  I tried compiling a 64 bit windows but if failed complaining that some
 
  include file could not be found.
 
  
 
  If possible could this patch be included for the next release?
 
 
 
 AFAIK this was included in patch 7.3.889.
 

Well, I have downloaded the 64 bit 2.0-p195 rubyinstaller from 
http://rubyinstaller.org/downloads/
and configured ruby with 
RUBY=C:\htemp\Ruby200-x64 DYNAMIC_RUBY=yes RUBY_VER=20 RUBY_VER_LONG=2.0.0 ^

when compiling I get the error:
c:\htemp\ruby200-x64\include\ruby-2.0.0\ruby/ruby.h(24) : fatal error C1083: 
Cannot open include file: 'ruby/c
onfig.h': No such file or directory
NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\BIN\x86_amd64\cl.EXE' : r
eturn code '0x2'
Stop.

if I don't include the configuration for ruby then I can compile fine (Included 
patches 1-944).

Is there a different installer I should be using or different configuration 
options?


 
 
  A small example on how to use rubydo (similar to the example on how to
 
  use perldo) would be useful for people like me, that don't know much
 
  about ruby but would like to learn.
 
  
 
  Also for the next release, if possible would it be possible to
 
  distribute a 64 bit for windows as well a 32 bit? 
 
 
 
 It's not all that useful.  It uses more memory, is probably a bit
 
 slower.  I haven't heard real practical advantages.  But perhaps that
 
 changed with Windows 8?
 

I am not sure how much bigger the memory usage will be, but I would not think 
it would be that big.
64 bit windows users will probably already use 64 bit python and perl so if 
there is a 64 bit vim they won't have to install additional 32 bit versions.

Jorge

-- 
-- 
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: compiling windows binary using cygwin fails

2013-05-12 Fir de Conversatie skeept 

 If you want to build a Win32 binary, use i686-pc-mingw32-gcc or
 i686-w64-mingw-gcc, not i686-pc-cygwin-gcc.
 i686-pc-cygwin-gcc is a compiler for building cygwin binary.
 
 Thanks,
 Ken Takata


Thanks for you help.
Indeed changing to a different compiler name allows me to build gvim, although 
it fails when it tries to build gvimext:

make -f Make_cyg.mak SHELL=bash CC=i686-w64-mingw32-gcc 
CXX=i686-w64-mingw32-g++ RC=i686-w64-mingw32-windres ARCH=i686 
CROSS_COMPILE=x86_64-w64-mingw32- USEDLL=no PYTHON=/cygdrive/c/Python27 
PYTHON_VER=27 DYNAMIC_PYTHON=yes PERL=/cygdrive/c/htemp/Perl PERL_VER=516 
DYNAMIC_PERL=yes GUI=yes
i686-w64-mingw32-gcc -O3 -fomit-frame-pointer -freg-struct-return 
-fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG  -DWINVER=0x0500 
-D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL 
-DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_PYTHON -DDYNAMIC_PYTHON 
-DDYNAMIC_PYTHON_DLL=\python27.dll\ -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV 
-DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG 
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -march=i686 -Iproto 
-I/cygdrive/c/htemp/Perl/lib/CORE -s  -o gvim.exe gobj/blowfish.o  
gobj/buffer.o  gobj/charset.o  gobj/diff.o  gobj/digraph.o  gobj/edit.o  
gobj/eval.o  gobj/ex_cmds.o  gobj/ex_cmds2.o  gobj/ex_docmd.o  gobj/ex_eval.o  
gobj/ex_getln.o  gobj/fileio.o  gobj/fold.o  gobj/getchar.o  gobj/hardcopy.o  
gobj/hashtab.o  gobj/main.o  gobj/mark.o  gobj/memfile.o  gobj/memline.o  
gobj/menu.o  gobj/message.o  gobj/misc1.o  gobj/misc2.o  gobj/move.o  
gobj/mbyte.o  gobj/normal.o  gobj/ops.o  gobj/option.o  gobj/os_win32.o  
gobj/os_mswin.o  gobj/winclip.o  gobj/pathdef.o  gobj/popupmnu.o  
gobj/quickfix.o  gobj/regexp.o  gobj/screen.o  gobj/search.o  gobj/sha256.o  
gobj/spell.o  gobj/syntax.o  gobj/tag.o  gobj/term.o  gobj/ui.o  gobj/undo.o  
gobj/version.o  gobj/vimrc.o  gobj/window.o  gobj/if_perl.o gobj/if_python.o 
gobj/if_cscope.o gobj/netbeans.o gobj/gui.o gobj/gui_w32.o gobj/gui_beval.o 
gobj/os_w32exe.o  -luuid -lole32 -lwsock32 -mwindows -lcomctl32 -lversion
make -C GvimExt -f Make_cyg.mak CROSS_COMPILE=x86_64-w64-mingw32-
make[1]: Entering directory `/cygdrive/c/htemp/vim/src/GvimExt'
i686-w64-mingw32-g++ -shared -O2 -mno-cygwin -s -o gvimext.dll \
-Wl,--enable-auto-image-base \
-Wl,--enable-auto-import \
-Wl,--whole-archive \
gvimext.o gvimext.res gvimext_ming.def \
-Wl,--no-whole-archive \
-luuid
gvimext.res: file not recognized: File format not recognized
collect2: ld returned 1 exit status
Make_cyg.mak:62: recipe for target `gvimext.dll' failed
make[1]: *** [gvimext.dll] Error 1
make[1]: Leaving directory `/cygdrive/c/htemp/vim/src/GvimExt'
Make_cyg.mak:589: recipe for target `GvimExt/gvimext.dll' failed
make: *** [GvimExt/gvimext.dll] Error 2

This is not a big deal, since the program I really wanted to build is the gvim 
binary.

Thanks,
Jorge

-- 
-- 
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.

Compiling vim with visual studio 2012 express

2013-05-12 Fir de Conversatie skeept 
I tried compiling gvim in windows using the cygwin interface and also visual 
studio express. 

When compiling with visual studio express update 2 you immediately get the 
error:

C:\htemp\vim\srcnmake -f Make_mvc.mak

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

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

Since I had Win32.mak in other computer where I can access visual studio I 
copied it to the vim sources folder.

Once I did this I could compile all the sources until the link stage:

C:\htemp\vim\srcnmake -f Make_mvc.mak FEATURES=HUGE OLE=yes MBYTE=yes IME=yes 
DYNAMIC_IME=yes GIME=yes DYNAMIC_PYTHON=y
es PYTHON=C:\Python27_64 PYTHON_VER=27 PERL=C:\Perl64 PERL_VER=516 
DYNAMIC_PERL=yes CPU=AMD64 WINVER=0x0601 GUI=yes


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

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

cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE 
-DFEAT_NETBEANS_INTG   -DFEAT_XPM_W32   -D
WINVER=0x0601 -D_WIN32_WINNT=0x0601  /Fo.\ObjGOLYAMD64/ /Ox /GL -DNDEBUG  /Zl 
/MT -DFEAT_OLE -DFEAT_MBYTE_IME -DDYNAMIC_
IME -DGLOBAL_IME -DFEAT_MBYTE -DFEAT_GUI_W32 -DDYNAMIC_ICONV -DDYNAMIC_GETTEXT 
-DFEAT_PYTHON -DDYNAMIC_PYTHON  -DDYNAMIC
_PYTHON_DLL=\python27.dll\ -DFEAT_PERL -DDYNAMIC_PERL 
-DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_HUGE /Fd.\ObjGOLYAMD64
/ /Zi version.c
version.c
  /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe 
.\ObjGOLYAMD64\blowfish.obj  .\ObjGOLYAMD64\buffer.obj
.\ObjGOLYAMD64\charset.obj  .\ObjGOLYAMD64\diff.obj  .\ObjGOLYAMD64\digraph.obj 
 .\ObjGOLYAMD64\edit.obj  .\ObjGOLYAMD64
\eval.obj  .\ObjGOLYAMD64\ex_cmds.obj  .\ObjGOLYAMD64\ex_cmds2.obj  
.\ObjGOLYAMD64\ex_docmd.obj  .\ObjGOLYAMD64\ex_eval.
obj  .\ObjGOLYAMD64\ex_getln.obj  .\ObjGOLYAMD64\fileio.obj  
.\ObjGOLYAMD64\fold.obj  .\ObjGOLYAMD64\getchar.obj  .\ObjG
OLYAMD64\hardcopy.obj  .\ObjGOLYAMD64\hashtab.obj  .\ObjGOLYAMD64\main.obj  
.\ObjGOLYAMD64\mark.obj  .\ObjGOLYAMD64\mbyt
e.obj  .\ObjGOLYAMD64\memfile.obj  .\ObjGOLYAMD64\memline.obj  
.\ObjGOLYAMD64\menu.obj  .\ObjGOLYAMD64\message.obj  .\Ob
jGOLYAMD64\misc1.obj  .\ObjGOLYAMD64\misc2.obj  .\ObjGOLYAMD64\move.obj  
.\ObjGOLYAMD64\normal.obj  .\ObjGOLYAMD64\ops.o
bj  .\ObjGOLYAMD64\option.obj  .\ObjGOLYAMD64\os_mswin.obj  
.\ObjGOLYAMD64\winclip.obj  .\ObjGOLYAMD64\os_win32.obj  .\O
bjGOLYAMD64\pathdef.obj  .\ObjGOLYAMD64\popupmnu.obj  
.\ObjGOLYAMD64\quickfix.obj  .\ObjGOLYAMD64\regexp.obj  .\ObjGOLYA
MD64\screen.obj  .\ObjGOLYAMD64\search.obj  .\ObjGOLYAMD64\sha256.obj  
.\ObjGOLYAMD64\spell.obj  .\ObjGOLYAMD64\syntax.o
bj  .\ObjGOLYAMD64\tag.obj  .\ObjGOLYAMD64\term.obj  .\ObjGOLYAMD64\ui.obj  
.\ObjGOLYAMD64\undo.obj  .\ObjGOLYAMD64\wind
ow.obj  .\ObjGOLYAMD64\vim.res .\ObjGOLYAMD64\dimm_i.obj 
.\ObjGOLYAMD64\glbl_ime.obj .\ObjGOLYAMD64\gui.obj  .\ObjGOLYAM
D64\gui_beval.obj  .\ObjGOLYAMD64\gui_w32.obj  .\ObjGOLYAMD64\os_w32exe.obj 
.\ObjGOLYAMD64\if_ole.obj.\ObjGOLYAMD64\
if_perl.obj .\ObjGOLYAMD64\if_perlsfio.obj .\ObjGOLYAMD64\if_python.obj  
.\ObjGOLYAMD64/if_cscope.obj .\ObjGOLYAMD64
/netbeans.obj  .\ObjGOLYAMD64/xpm_w32.obj .\ObjGOLYAMD64\version.obj 
oldnames.lib kernel32.lib advapi32.lib shell32.lib
gdi32.lib  comdlg32.lib ole32.lib uuid.lib /machine:AMD64 /nodefaultlib 
gdi32.lib version.lib   winspool.lib comctl32.li
b advapi32.lib shell32.lib  /machine:AMD64 /nodefaultlib libcmt.lib 
oleaut32.lib  user32.lib  /nodefaultlib:python27
.lib WSock32.lib xpm\x64\lib\libXpm.lib /PDB:gvim.pdb -debug
'/nologo' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: '' : return code '0x1'
Stop.
C:\htemp\vim\src

When I add the link in from of /nologo then I can compile successively.

It is possible to compile without copying the file Win32.mak and without having 
to add the link statement explicitly?

Regards,
Jorge

-- 
-- 
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.

compiling windows binary using cygwin fails

2013-05-11 Fir de Conversatie skeept 
I am trying to build windows binary using cygwin. The command line and the 
error I get is bellow.

 make -f Make_cyg.mak SHELL=bash CC=i686-pc-cygwin-gcc CXX=i686-pc-cygwin-g++ 
RC=windres ARCH=i686 CROSS_COMPILE=x86_64-w64-mingw32- USEDLL=no 
PYTHON=/cygdrive/c/Python27 PYTHON_VER=27 DYNAMIC_PYTHON=yes 
PERL=/cygdrive/c/htemp/Perl PERL_VER=516 DYNAMIC_PERL=yes GUI=yes gvim.exe

i686-pc-cygwin-gcc -c -O3 -fomit-frame-pointer -freg-struct-return 
-fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG  -DWINVER=0x0500 
-D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL 
-DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_PYTHON -DDYNAMIC_PYTHON 
-DDYNAMIC_PYTHON_DLL=\python27.dll\ -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV 
-DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG 
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -march=i686 -Iproto 
-I/cygdrive/c/htemp/Perl/lib/CORE -s  eval.c -o gobj/eval.o
eval.c: In function ‘modify_fname’:
eval.c:23845:16: error: ‘_MAX_PATH’ undeclared (first use in this function)
eval.c:23845:16: note: each undeclared identifier is reported only once for 
each function it appears in
Make_cyg.mak:634: recipe for target `gobj/eval.o' failed
make: *** [gobj/eval.o] Error 1

The same happens if I use Make_ming.mak instead of Make_cyg.mak.

I am not sure if something is wrong with my cygwin but I have compiled vim in 
my computer like this before.

Any ideas of what is going wrong?

Thanks,

Jorge

-- 
-- 
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: How to compile 64 bit with cygwin/mingw?

2013-02-08 Fir de Conversatie skeept 
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 using 
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=yes 
PERL=/cygdrive/c/Perl64 PERL_VER=516 DYNAMIC_PERL=yes -j5 GUI=yes

it also compiles fine using this command. 
However the resulting gvim has perl working fine but not python.
If I try just 
:py
I get
E471: Argument required


however if I try to actually do some work in python I get:
E448: Could not load library function Py_InitModule4
E263: Sorry, this command is disabled, the Python library could not be loaded.

I downloaded the lastest version of python available. 
Any idea why this is happening and how I can solve it?

Thanks again Ken!

-- 
-- 
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: How to compile 64 bit with cygwin/mingw?

2013-02-08 Fir de Conversatie skeept 
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 step fails:
x86_64-w64-mingw32-gcc -O3 -fomit-frame-pointer -freg-struct-return 
-fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG  -DWINVER=0x0500 
-D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL 
-DDYNAMIC_PERL_DLL=\perl516.dll\ -DFEAT_PYTHON -DDYNAMIC_GETTEXT 
-DDYNAMIC_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE 
-DFEAT_NETBEANS_INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -march=x86-64 -Iproto 
-I/cygdrive/c/Perl64/lib/CORE -s -mno-cygwin -o gvim.exe gobj/blowfish.o  
gobj/buffer.o  gobj/charset.o  gobj/diff.o  gobj/digraph.o  gobj/edit.o  
gobj/eval.o  gobj/ex_cmds.o  gobj/ex_cmds2.o  gobj/ex_docmd.o  gobj/ex_eval.o  
gobj/ex_getln.o  gobj/fileio.o  gobj/fold.o  gobj/getchar.o  gobj/hardcopy.o  
gobj/hashtab.o  gobj/main.o  gobj/mark.o  gobj/memfile.o  gobj/memline.o  
gobj/menu.o  gobj/message.o  gobj/misc1.o  gobj/misc2.o  gobj/move.o  
gobj/mbyte.o  gobj/normal.o  gobj/ops.o  gobj/option.o  gobj/os_win32.o  
gobj/os_mswin.o  gobj/pathdef.o  gobj/popupmnu.o  gobj/quickfix.o  
gobj/regexp.o  gobj/screen.o  gobj/search.o  gobj/sha256.o  gobj/spell.o  
gobj/syntax.o  gobj/tag.o  gobj/term.o  gobj/ui.o  gobj/undo.o  gobj/version.o  
gobj/vimrc.o  gobj/window.o  gobj/if_perl.o gobj/if_python.o gobj/if_cscope.o 
gobj/netbeans.o gobj/gui.o gobj/gui_w32.o gobj/gui_beval.o gobj/os_w32exe.o  
-luuid -lole32 /cygdrive/c/Python27_64/libs/python27.lib -lwsock32 -mwindows 
-lcomctl32 -lversion
gobj/if_python.o:if_python.c:(.text+0x7): undefined reference to 
`__imp__Py_NoneStruct'
gobj/if_python.o:if_python.c:(.text+0x1b9): undefined reference to 
`__imp_PyBool_Type'
gobj/if_python.o:if_python.c:(.text+0x1c6): undefined reference to 
`__imp__Py_TrueStruct'
gobj/if_python.o:if_python.c:(.text+0x203): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x233): undefined reference to 
`__imp_PyExc_AttributeError'
gobj/if_python.o:if_python.c:(.text+0x296): undefined reference to 
`__imp_PyBool_Type'
gobj/if_python.o:if_python.c:(.text+0x2a3): undefined reference to 
`__imp__Py_TrueStruct'
gobj/if_python.o:if_python.c:(.text+0x2e3): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x313): undefined reference to 
`__imp_PyExc_AttributeError'
gobj/if_python.o:if_python.c:(.text+0x483): undefined reference to 
`__imp_PyExc_KeyboardInterrupt'
gobj/if_python.o:if_python.c:(.text+0x8c4): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x8f3): undefined reference to 
`__imp_PyExc_AttributeError'
gobj/if_python.o:if_python.c:(.text+0xd50): undefined reference to 
`__imp_PyFloat_Type'
gobj/if_python.o:if_python.c:(.text+0xfa8): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1158): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1263): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1323): undefined reference to 
`__imp_PyExc_ValueError'
gobj/if_python.o:if_python.c:(.text+0x1393): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x1593): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1603): undefined reference to 
`__imp_PyExc_ValueError'
gobj/if_python.o:if_python.c:(.text+0x1903): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1943): undefined reference to 
`__imp_PyExc_ValueError'
gobj/if_python.o:if_python.c:(.text+0x1c08): undefined reference to 
`__imp__Py_NoneStruct'
gobj/if_python.o:if_python.c:(.text+0x1d5e): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x1dd3): undefined reference to 
`__imp_PyExc_ValueError'
gobj/if_python.o:if_python.c:(.text+0x1df5): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x1e37): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x1f11): undefined reference to 
`__imp__Py_NoneStruct'
gobj/if_python.o:if_python.c:(.text+0x24b1): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x25c4): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x26a1): undefined reference to 
`__imp_PyExc_IndexError'
gobj/if_python.o:if_python.c:(.text+0x2a67): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x2b56): undefined reference to 
`__imp__Py_NoneStruct'
gobj/if_python.o:if_python.c:(.text+0x2b83): undefined reference to 
`__imp_PyExc_TypeError'
gobj/if_python.o:if_python.c:(.text+0x2c3e): undefined reference to 
`__imp__Py_NoneStruct'

How to compile 64 bit with cygwin/mingw?

2013-02-07 Fir de Conversatie skeept 
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 then get the error:
/usr/lib/gcc/x86_64-w64-mingw32/4.5.3/../../../../x86_64-w64-mingw32/bin/ld: 
i386 architecture of input file `gobj/vimrc.o' is incompatible with i386:x86-64 
output

Searching for back for vimrc I see that it is compiled with
windres --preprocessor=x86_64-w64-mingw32-gcc -E -xc -DRC_INVOKED -DWIN32 
-DWINVER=0x0500 -D_WIN32_WINNT=0x0
500  -DHAVE_PATHDEF -DFEAT_BIG -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT 
-DFEAT_CSCOPE -DFEAT_NETBEANS_
INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME 
-DDYNAMIC_IME -DDYNAMIC_ICONV \
--input-format=rc --output-format=coff -i vim.rc -o gobjx86-64/vimrc.o

Please let me know if I am missing something here or if something can be done 
about this.

Regards,
Jorge

-- 
-- 
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] suppress warnings on Win32

2013-01-30 Fir de Conversatie skeept 
I have some warnings when compiling with visual studio 2012:

ex_cmds.c(4768) : warning C4267: '=' : conversion from 'size_t' to 'int', 
possible loss of data


if_perl.xs(1051) : warning C4244: '=' : conversion from 'IV' to 'int', possible 
loss of data
if_perl.xs(1094) : warning C4244: '=' : conversion from 'IV' to 'int', possible 
loss of data
if_perl.xs(1157) : warning C4244: '=' : conversion from 'IV' to 'int', possible 
loss of data
if_perl.xs(1158) : warning C4244: '=' : conversion from 'IV' to 'int', possible 
loss of data
if_perl.xs(1219) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data
if_perl.xs(1242) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data
if_perl.xs(1277) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data
if_perl.xs(1282) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data
if_perl.xs(1283) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data
if_perl.xs(1334) : warning C4244: '=' : conversion from 'IV' to 'long', 
possible loss of data


I think the perl warning have been there for a while, I don't remember the 
first one being there before this last batch of updates (may be wrong tough).

Regards

-- 
-- 
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: Small change to support Visual Studio 2012 Update 1

2012-12-06 Fir de Conversatie skeept 
Hi Raymond,

On Wednesday, December 5, 2012 2:01:26 PM UTC-5, Raymond Ko wrote:
 Hello all,
 
 Attached is a small change to support the newest NMAKE introduced by Visual 
 Studio 2012 Update 1. I have tested it and VIM seems to compile fine.


I updated visual studio yesterday and temporarily added MSVCVER=11.0 in the 
command line in order to be able to compile, would have worked with this patch.

How about Win32.Mak? Does compiling vim work without copying this file to the 
vim source dir? In my case I had to go to the old visual studio 2010 folder and 
copy that file, because somehow it wasn't present when I installed visual 
studio 2012 (ultimate).

Thanks!

-- 
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: Can't compile latest Vim using Make_cyg.mak

2012-11-15 Fir de Conversatie skeept 
On Thursday, November 15, 2012 2:42:32 AM UTC-5, Heptite wrote:
 gcc-3 -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce 
 -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG  -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 
 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\perl512.dll\ -DFEAT_PYTHON 
 -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\python27.dll\ -DFEAT_RUBY 
 -DDYNAMIC_RUBY -DDYNAMIC_RUBY_DLL=\msvcrt-ruby191.dll\ 
 -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV -DFEAT_MBYTE 
 -DFEAT_MBYTE_IME -DDYNAMIC_IME -DMSWINPS -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG 
 -DFEAT_XPM_W32 -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto 
 -I/cygdrive/c/strawberry/perl/lib/CORE 
 -I/cygdrive/c/Ruby192/include/ruby-1.9.1 
 -I/cygdrive/c/Ruby192/include/ruby-1.9.1/i386-mingw32 -s -mno-cygwin 
 -Ixpm/include -o gvim.exe gobj/blowfish.o  gobj/buffer.o  gobj/charset.o  
 gobj/diff.o  gobj/digraph.o  gobj/edit.o  gobj/eval.o  gobj/ex_cmds.o  
 gobj/ex_cmds2.o  gobj/ex_docmd.o  gobj/ex_eval.o  gobj/ex_getln.o  
 gobj/fileio.o  gobj/fold.o  gobj/getchar.o  gobj/hardcopy.o  gobj/hashtab.o  
 gobj/main.o  gobj/mark.o  gobj/memfile.o  gobj/memline.o  gobj/menu.o  
 gobj/message.o  gobj/misc1.o  gobj/misc2.o  gobj/move.o  gobj/mbyte.o  
 gobj/normal.o  gobj/ops.o  gobj/option.o  gobj/os_win32.o  gobj/os_mswin.o  
 gobj/pathdef.o  gobj/popupmnu.o  gobj/quickfix.o  gobj/regexp.o  
 gobj/screen.o  gobj/search.o  gobj/sha256.o  gobj/spell.o  gobj/syntax.o  
 gobj/tag.o  gobj/term.o  gobj/ui.o  gobj/undo.o  gobj/version.o  gobj/vimrc.o 
  gobj/window.o  gobj/if_perl.o gobj/if_python.o gobj/if_ruby.o 
 gobj/if_cscope.o gobj/netbeans.o gobj/xpm_w32.o gobj/gui.o gobj/gui_w32.o 
 gobj/gui_beval.o gobj/os_w32exe.o gobj/if_ole.o -L/lib/w32api 
 -L/usr/lib/mingw -L/usr/lib/w32api -I/usr/include/mingw -I/usr/include/w32api 
 -luuid -lole32 -lwsock32 -Lxpm/lib -Lxpm/x86/lib -lXpm -L/lib/w32api 
 -mwindows -lcomctl32 -lversion -loleaut32 -lstdc++
 
 gobj/eval.o:eval.c:(.text+0x70b7): undefined reference to `_pow'
 
 collect2: ld returned 1 exit status
 
 Make_cyg.mak:534: recipe for target `gvim.exe' failed
 
 make: *** [gvim.exe] Error 1
 
 
 
 -- 
 
  Having a non-smoking section in a restaurant
 
 is like having a non-peeing section in a pool.
 
 Christian J. Robinson hept...@gmail.com  http://christianrobinson.name/



I can't understand why it doesn't work. I can compile vim in cygwin in 32 bits, 
but don't know how to do it in 64 bits.
I have to change the name of the compiler tough.
See 
https://groups.google.com/d/msg/vim_use/80X4edvhEeo/u7oYDye-5oYJ
for what I usually when compiling vim in cygwin.

Regards,
Jorge

-- 
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

Compiling vim in windows 8 with visual studio 12

2012-11-09 Fir de Conversatie skeept 
Could anyone successfully compile vim in windows 8 with visual studio 12?

I just installed the system yesterday, and I was trying to compile vim but I am 
having issues.

These are the steps:
first setting up the variables:
call c:\Program Files (x86)\Microsoft Visual Studio 
11.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat

then 
nmake -f Make_mvc.mak CPU=AMD64 GUI=yes

this stops with the error:
Microsoft (R) Program Maintenance Utility Version 11.00.50727.1
Copyright (C) Microsoft Corporation.  All rights reserved.

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


I searched and found out that in windows 7 this file was under:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include\Win32.Mak

but with this in windows 8 I cannot find the file in the same folder (the 
folder doesn't exist anymore).

Any idea on how to solve this?

Thanks!

-- 
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: Compiling vim in windows 8 with visual studio 12

2012-11-09 Fir de Conversatie skeept 
On Friday, November 9, 2012 5:39:32 PM UTC-5, skeept wrote:
 Could anyone successfully compile vim in windows 8 with visual studio 12?
 
 I just installed the system yesterday, and I was trying to compile vim but I 
 am having issues.
 
 These are the steps:
 first setting up the variables:
 call c:\Program Files (x86)\Microsoft Visual Studio 
 11.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat
 
 then 
 nmake -f Make_mvc.mak CPU=AMD64 GUI=yes
 
 this stops with the error:
 Microsoft (R) Program Maintenance Utility Version 11.00.50727.1
 Copyright (C) Microsoft Corporation.  All rights reserved.
 
 Make_mvc.mak(236) : fatal error U1052: file 'Win32.mak' not found
 Stop.
 
 
 I searched and found out that in windows 7 this file was under:
 C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include\Win32.Mak
 
 but with this in windows 8 I cannot find the file in the same folder (the 
 folder doesn't exist anymore).
 
 Any idea on how to solve this?
 
 Thanks!

Copying the mentioned file from the old location to vim source fixes this, 
should have thought of that before!

Regards.

-- 
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

showing actually replacement when using the 'c' flag in subtitute?

2012-10-04 Fir de Conversatie skeept 
If I am doing a substitution:

:%s/\(a\|b\)\(c\|d\)/\2\1\gc

then the message that shows is something like
would you like to replace by '\2\1' ...?\

It would be nice to actually see what the new text would be (for more 
complicated substitutions of course).

Is there such an option that would allow me to do this right now?
If not could this be added to the todo list?


Thank you,
Jorge

-- 
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: Can't paste Unicode Delta symbol (Δ) into vim nor gVim

2012-09-13 Fir de Conversatie skeept 
On Thursday, September 13, 2012 3:56:56 PM UTC-4, Tony Mechelynck wrote:
 On 13/09/12 19:57, MC Andre wrote:
 
  I can copy and past the Unicode Delta symbol (οΏ½) in a normal Command 
  Prompt window.
 
 
 
  I can copy and past ASCII Roman alphabetic text in vim and gVim.
 
 
 
  But I can't paste the Unicode Delta symbol (οΏ½) into vim nor gVim.
 
 
 
  Specs:
 
 
 
  * gVim 7.3
 
  * Windows 7 Professional x64
 
 
 
 I just pasted it from your mail into my running gvim (7.3.661 Huge with 
 
 GTK2-GNOME2 GUI), and ga over it gives me:
 
 
 
 οΏ½ 916, Hex 0394, Octal 1624
 
 
 
 So the next question is: What is your 'encoding' set to? Type
 
 
 
   :verbose set encoding?
 
 
 
 and see what the answer is. If it is latin1 or cp1252, or indeed any 
 
 8-bit encoding other than a Greek one, the reason you can't paste the 
 
 delta sign is that you haven't set gvim to be able to represent it in 
 
 memory. In that case, see
 
 
 
   http://vim.wikia.com/wiki/Working_with_Unicode
 
 
 
 about how to set gvim to work in UTF-8 (which can represent anything 
 
 that any other encoding can represent) and remember that any change to 
 
 'encoding' must happen in your vimrc, before any editfile is loaded, 
 
 otherwise the files which _are_ already loaded at the time of the change 
 
 will become garbled.
 
 
 
 
 
 Best regards,
 
 Tony.
 
 -- 
 
 All things are possible, except skiing thru a revolving door.



On Thursday, September 13, 2012 3:56:56 PM UTC-4, Tony Mechelynck wrote:
 On 13/09/12 19:57, MC Andre wrote:
 
  I can copy and past the Unicode Delta symbol (οΏ½) in a normal Command 
  Prompt window.
 
 
 
  I can copy and past ASCII Roman alphabetic text in vim and gVim.
 
 
 
  But I can't paste the Unicode Delta symbol (οΏ½) into vim nor gVim.
 
 
 
  Specs:
 
 
 
  * gVim 7.3
 
  * Windows 7 Professional x64
 
 
 
 I just pasted it from your mail into my running gvim (7.3.661 Huge with 
 
 GTK2-GNOME2 GUI), and ga over it gives me:
 
 
 
 οΏ½ 916, Hex 0394, Octal 1624
 
 
 
 So the next question is: What is your 'encoding' set to? Type
 
 
 
   :verbose set encoding?
 
 
 
 and see what the answer is. If it is latin1 or cp1252, or indeed any 
 
 8-bit encoding other than a Greek one, the reason you can't paste the 
 
 delta sign is that you haven't set gvim to be able to represent it in 
 
 memory. In that case, see
 
 
 
   http://vim.wikia.com/wiki/Working_with_Unicode
 
 
 
 about how to set gvim to work in UTF-8 (which can represent anything 
 
 that any other encoding can represent) and remember that any change to 
 
 'encoding' must happen in your vimrc, before any editfile is loaded, 
 
 otherwise the files which _are_ already loaded at the time of the change 
 
 will become garbled.
 


You may also have to choose a font that supports these characters. 
In the font I am currently using type ctrl-k *a (ctrl-k followed by * followed 
by a) should show the greek letter alpha but instead it shows only a little 
square.

-- 
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: 64-bit support for Windows (Vista)

2012-09-05 Fir de Conversatie skeept 
On Tuesday, August 28, 2012 1:05:01 AM UTC-4, Sergey Khorev wrote:
  link /RELEASE /nologo /subsystem:windows /LTCG:STATUS
 
 ...
 
  advapi32.lib shell32.lib  /machine:i386 /no
 
 
 
 Ok, the problem is in /machine:i386 which should be AMD64 for x64
 
 builds. Either something is wrong with your environment or
 
 Make_mvc.mak failed to detect the target architecture properly.
 
 
 
 Can you check what commands below show before and after you source
 
 vcvarsx86_amd64.bat?
 
 set PROCESSOR_ARCHITECTURE
 
 set ASSEMBLY_ARCHITECTURE
 
 set CPU


This might be obvious but I just figured it out now. The easiest way of solving 
this issue is simply to pass the correct option in the command line.
In my case:

nmake -f Make_mvc.mak CPU=AMD64 other_options

-- 
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: 64-bit support for Windows (Vista)

2012-08-27 Fir de Conversatie skeept 
This is already a quite old thread but I can't find easily any instruction on 
how to compile vim for 64 bit windows. I am using windows 7.

I tried the following:

first I call
c:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\bin\x86_amd64\vcvarsx86_amd64.bat

to set up the vars to 64 bit.

Then I try to compile just with 
nmake -f Make_mvc.mak GUI=yes

and all the files seem to compile fine until it reaches the link step where the 
error is:

cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32   -DFEAT_CSCOPE 
-DFEAT_NETBEANS_INTG
  -DWINVER=0x0400 -D_WIN32_WINNT=0x0400  /Fo.\ObjG/ /Ox /GL -DNDEBUG  /Zl /MT 
-DFEAT_GUI_W32 -DDYNAMIC
_ICONV -DDYNAMIC_GETTEXT -DFEAT_BIG /Fd.\ObjG/ /Zi version.c
version.c
link /RELEASE /nologo /subsystem:windows /LTCG:STATUS -out:gvim.exe 
.\ObjG\blowfish.obj  .\Obj
G\buffer.obj  .\ObjG\charset.obj  .\ObjG\diff.obj  .\ObjG\digraph.obj  
.\ObjG\edit.obj  .\ObjG\eval.ob
j  .\ObjG\ex_cmds.obj  .\ObjG\ex_cmds2.obj  .\ObjG\ex_docmd.obj  
.\ObjG\ex_eval.obj  .\ObjG\ex_getln.o
bj  .\ObjG\fileio.obj  .\ObjG\fold.obj  .\ObjG\getchar.obj  .\ObjG\hardcopy.obj 
 .\ObjG\hashtab.obj  .
\ObjG\main.obj  .\ObjG\mark.obj  .\ObjG\mbyte.obj  .\ObjG\memfile.obj  
.\ObjG\memline.obj  .\ObjG\menu
.obj  .\ObjG\message.obj  .\ObjG\misc1.obj  .\ObjG\misc2.obj  .\ObjG\move.obj  
.\ObjG\normal.obj  .\Ob
jG\ops.obj  .\ObjG\option.obj  .\ObjG\os_mswin.obj  .\ObjG\os_win32.obj  
.\ObjG\pathdef.obj  .\ObjG\po
pupmnu.obj  .\ObjG\quickfix.obj  .\ObjG\regexp.obj  .\ObjG\screen.obj  
.\ObjG\search.obj  .\ObjG\sha25
6.obj  .\ObjG\spell.obj  .\ObjG\syntax.obj  .\ObjG\tag.obj  .\ObjG\term.obj  
.\ObjG\ui.obj  .\ObjG\und
o.obj  .\ObjG\window.obj  .\ObjG\vim.res .\ObjG\gui.obj  .\ObjG\gui_beval.obj  
.\ObjG\gui_w32.obj  .\O
bjG\os_w32exe.obj.\ObjG/if_cscope.obj .\ObjG/netbeans.obj   
.\ObjG\version.obj oldnames.li
b 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 /no
defaultlib libcmt.lib   user32.lib   WSock32.lib  /PDB:gvim.pdb -debug
.\ObjG\blowfish.obj : fatal error LNK1112: module machine type 'x64' conflicts 
with target machine typ
e 'X86'
NMAKE : fatal error U1077: 'c:\Program Files (x86)\Microsoft Visual Studio 
10.0\VC\BIN\x86_amd64\link
.EXE' : return code '0x458'
Stop.


Any ideas on how to compile this? 
I guess this would be  nice thing to have for the next release.

Thanks,

Jorge

-- 
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 for py[3] command to avoid print calls

2012-08-20 Fir de Conversatie skeept 
On Thursday, August 16, 2012 8:47:38 AM UTC-4, Maxim Philippov wrote:
 Hi, vim_dev!
 
 I'd like to offer a small patch for python interface, which allows to avoid 
 inserting print call for every expression in order to see result.
 
 Now:
 
 :py 2 + 2
 :py dir.__doc__
 
 After applying patch:
 
 :py 2 + 2
 4
 :py dir.__doc__
 dir([object]) - list of strings...
 
 So py/py3 commands are more REPL-like. See pyrepl.diff in attachment for 
 details.

I think this only makes sense if there is an option that allows to 
enable/disable it by default, say pythonverbose with the default value being 
disabled.

-- 
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

Problem linking with static lua

2012-04-05 Fir de Conversatie skeept 
I saw new patches today regarding lua so I decided to compile vim with it.

I compile lua with:

make linux
make install INSTALL_TOP=$lua_location

Then I configure linux with the following options:
--enable-luainterp=yes
--with-lua-prefix=$lua_location

configure runs fine and I can make vim all the way to the linking step at which 
point I get the error

/usr/bin/ld: cannot find -llua5.2

if I manually edit the linking command 
gcc   -L.  -rdynamic -Wl,-export-dynamic  -Wl,-E 
-Wl,-rpath,/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE   
-L/usr/local/lib -Wl,--as-needed ...

and replace -llua5.2 by -llua it compiles and runs fine.

-- 
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: Is it possible to ignore runtime/doc/tags in .hgignore?

2012-03-18 Fir de Conversatie skeept 

On Mar 18, 11:15 pm, Tony Mechelynck antoine.mechely...@gmail.com
wrote:

Hi Tony,

your answer makes a lot of sense, except that I don't run hg pull
directly, I run it in a script that
also tries to get updates for other programs and scripts so I don't
get an opportunity to choose if I want to
discard the changes.
I added the file to .hgignore, so I guess the only time I will have
problems in the future is when some change to
.hgignore occurs.

Best Regards,

Jorge.

-- 
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

Is it possible to ignore runtime/doc/tags in .hgignore?

2012-03-16 Fir de Conversatie skeept 
Hi,

I would like to know if it is possible to include
runtime/doc/tags in .hgignore?

after I build vim this file shows as modified in mercurial and then
when I try to pull again
I get some kind of error message regarding uncommited local changes.

Alternatively is there a mercurial command to always copy the remote
files irrespective of whatever
local changes I have?

Thanks.

-- 
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

Feature request: add optional argument to :jumps to allow replace of c-i

2012-02-15 Fir de Conversatie skeept 
Hi all,

I have remapped tab and now c-i does not work as expected.
I don't use the c-i command very often, but I do use it
occasionally.
I asked it there was a way of solving this in vim_use and it was
suggested that
I could do something like:

   :nnoremap tab c-w
   :nnoremap f4 c-i

I would prefer  to do something like `:ju -1` or `:ju 1` to move back
in the list.
Without argument it would just work like it does now.

Please consider implementing this if not to hard.

Thanks!

-- 
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: Feature request: add optional argument to :jumps to allow replace of c-i

2012-02-15 Fir de Conversatie skeept 
Thanks Christian,


On Feb 15, 2:01 pm, Christian Brabandt cbli...@256bit.org wrote:
 Hi skeept!

 On Mi, 15 Feb 2012, skeept wrote:









  Hi all,

  I have remapped tab and now c-i does not work as expected.
  I don't use the c-i command very often, but I do use it
  occasionally.
  I asked it there was a way of solving this in vim_use and it was
  suggested that
  I could do something like:

     :nnoremap tab c-w
     :nnoremap f4 c-i

  I would prefer  to do something like `:ju -1` or `:ju 1` to move back
  in the list.
  Without argument it would just work like it does now.

  Please consider implementing this if not to hard.

 I think implementing this wouldn't be too hard, but how about something
 like this:
 :command -count=1 Jump exe :norm! count\C-O

 regards,
 Christian

I will use your solution is suits my needs quite well.

Regards,
skeept

-- 
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: problem saving file (or other command mode)

2011-03-23 Fir de Conversatie skeept 


On Mar 22, 6:36 pm, Gregor Uhlenheuer kongo2...@googlemail.com
wrote:
 On 03/22/2011 09:28 PM, skeept wrote:





  Since a couple of days I have been having the following problem with
  vim:

  I use it normally and after a while I am unable to save the file
  using :wa
  Each time I press enter nothing happens and when I press other key
  other then enter (say space) the following
  shows up
  :waSNR92_parse_cmd_line()

  I searched in the vim source with grep and in my .vim folder but could
  not find this string.
  Any thoughts on how to proceed to try to diagnose what is causing
  this?
  I am using the latest vim version (143)

  Thanks.

 It's just a wild guess but it could be the vim-space plugin.

 If that's true you can find the project on 
 github:https://github.com/spiiph/vim-space

 Maybe you can then submit a bug report there (I am using that plugin
 just fine).

 Cheers,
 Gregor

Hi Gregor,

I think you might be right. I disabled the vim-space plugin since
yesterday the same didn't
happen again.

Cheers.

-- 
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

problem saving file (or other command mode)

2011-03-22 Fir de Conversatie skeept 
Since a couple of days I have been having the following problem with
vim:

I use it normally and after a while I am unable to save the file
using :wa
Each time I press enter nothing happens and when I press other key
other then enter (say space) the following
shows up
:waSNR92_parse_cmd_line()

I searched in the vim source with grep and in my .vim folder but could
not find this string.
Any thoughts on how to proceed to try to diagnose what is causing
this?
I am using the latest vim version (143)

Thanks.

-- 
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: Folding, highlighting and patch 274

2010-05-27 Fir de Conversatie skeept 
It also became very slow for me
with the only settings being

syntax on
set foldmethod=syntax

the file being edited is a large C file.

Best.

H Jorge

On May 26, 6:04 pm, Christian Brabandt cbli...@256bit.org wrote:
 Hi Frederic!

 On Mi, 26 Mai 2010, Frederic Hardy wrote:





  Since patch 274, my vim/gvim is very slow, specialy when i'm editing a  
  large php file with my custom syntax file.

  All my vim files (.vimrc, .gvimrc, .vim) are available here :  
 http://medias.mageekbox.net/vim.tgz.

  There is a large php file in the tar archive to illustrate my problem.
  Use my config files and try to modify the class name or remove the  
  abstract keyword at line 8 to see the problem (perhaps...).
  Then i do it, my CPU usage grown to 100% and vim is frozen until i do  
  not hit ctrl-c.

  I have the problem under FreeBSD 7.1 and FreeBSD 8.

  This is the result of the :version command in vim :

  VIM - Vi IMproved 7.2 (2008 Aug 9, compiled May 26 2010 12:01:44)
  Included patches: 1-6, 8-35, 37-48, 50-70, 73, 75-87, 90-92, 94-100,  
  102-137, 139-149, 151-171, 173-190, 192-193, 195-203, 206-211, 213-215,  
  217-218, 220-232, 234-246, 251-259, 261-3
  01, 303-319, 321-322, 324-335, 337-351, 353-361, 363, 366-371, 373,  
  375-376, 378-383, 385-387, 389-398, 401-402, 404-411
  Compiled by f...@witchblade
  Big version with GTK2 GUI.  Features included (+) or not (-):
  +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset  
  +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist  
  +cmdline_info +comments +cryptv +cscope
  +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 +menu +mksession  
  +modify_fname +mouse +mouseshape +mouse_dec
  -mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_sysmouse +mouse_xterm  
  +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra  
  -perl +postscript +printer -profile
  +python +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: cc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  
  -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0  
  -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0
  -I/usr/local/include/cairo -I/usr/local/include/pango-1.0  
  -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include  
  -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/u
  sr/local/include/pixman-1 -I/usr/local/include/freetype2  
  -I/usr/local/include  -O2 -pipe -march=pentium-m -fno-strict-aliasing  
  -march=pentium-m -D_FORTIFY_SOURCE=1  -I/usr/local/incl
  ude   -I/usr/local/include/python2.6 -D_THREAD_SAFE  
  -I/usr/local/lib/ruby/1.8/i386-freebsd8 -DRUBY_VERSION=18
  Linking: cc -L/usr/local/lib -L/usr/local/lib -R/usr/local/lib -L.  
  -rpath=/usr/lib:/usr/local/lib -pthread -rdynamic  -L/usr/local/lib -o  
  vim   -pthread -L/usr/local/lib -lgtk-x11-2
  .0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lXext  
  -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage  
  -lpangoft2-1.0 -lgio-2.0 -lXfixes -lcairo -lpa
  ngo-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0  
  -lgthread-2.0 -lglib-2.0 -lXt -pthread -ltermlib  
  -L/usr/local/lib/python2.6/config -lpython2.6 -lutil -Wl,--export-dynamic
    -Wl,-R -Wl,/usr/local/lib -L/usr/local/lib -lruby18 -lrt -lm  
  -L/usr/lib  -rpath=/usr/lib:/usr/local/lib -pthread

  I known that the patch 274 is ok and that vim is slow with syntax  
  folding, but it's very annoying and i want to be sure that the problem  
  is not in my config files or in my plug-in (but i have the problem with  
  gvim -U NONE -u NONE with no .vim directory in my home).

  vim was compiled from FreeBSD port /editors/vim.

 I can reproduce it with your provided syntax file and my debian vim
 7.2.330. I haven't looked into the syntax file in detail, but it seems
 to be the problem. Using your syntax php file and layout.php that you
 provided[1], this simple_vimrc script shows the problem:

 ,
 | profile start my_profile_php
 | fun Profile()
 |   syntax on
 |   e layer.php
 |   set fdm=syntax
 |   call feedkeys(:set synmaxcol=100\n,