Re: alt gr bad displayed in search or command line mode.

Even in insert mode, inserting backslash or others alt gr chars has regression. [image: Capture.PNG] Le samedi 23 avril 2022 à 12:38:42 UTC+2, Ni Va a écrit : > Hi, > > Since version 8.2 patch above 4804, it seems that when I type > /\ it displays /^\ > > It is the same i

alt gr bad displayed in search or command line mode.

Hi, Since version 8.2 patch above 4804, it seems that when I type /\ it displays /^\ It is the same in exe mode :foobar and for all alt gr chars. Thank you NV -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to.

Re: Libsodium error sodium.h

Thank you https://github.com/vim/vim/pull/9905 Le lundi 7 mars 2022 à 10:02:14 UTC+1, Ni Va a écrit : > Effectively sodium.h not found in C:\msys64\mingw32\include meanwhile i > follow §2.2 from installpc.txt. > > > > > > > > > *MSYS2 has its own git package

Re: [vim/vim] win32: Update libsodium implementation (PR #9905)

THANK YOU. Le lundi 7 mars 2022 à 16:17:18 UTC+1, Bram Moolenaar a écrit : > Closed #9905 via d8f8629 > > . > > — > Reply to this email directly, view it on GitHub >

Re: Libsodium error sodium.h

_VERSION=31 -DFEAT_PYTHON3 >> -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python311.dll\" -O3 >> -fomit-frame-pointer -freg-struct-return alloc.c -o gobji686/alloc.o >> >> In file included from alloc.c:14: >> vim.h:506:11: fatal error: sodium.h: No such file or dir

Re: Libsodium error sodium.h

m.h: No such file or directory 506 | # include | ^~ compilation terminated. mingw32-make: *** [Make_cyg_ming.mak:1184: gobji686/alloc.o] Error 1 Le dimanche 6 mars 2022 à 11:02:08 UTC+1, Ni Va a écrit : > Okay Thanks a lot Ken, > > Do i have to download you

Re: Libsodium error sodium.h

Okay Thanks a lot Ken, Do i have to download your fix on Make_cyg_ming.mak? Because I tried removing -I include directive and DYNAMIC_SODIUM_DLL, just leaving SODIUM=yes and got same error. Thank in advance. NV Le dimanche 6 mars 2022 à 07:46:10 UTC+1, ktakat...@gmail.com a écrit : > Hi, >

Libsodium error sodium.h

Hi, I encounter this error trying to link gvim with mingw32 make on Win10 Informations Interfaces c:/Ruby31 c:/Python310 Flags are: OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes LUA=./lua-5.4.4/src LUA_VER=54 PYTHON3=c:/Python310 DYNAMIC_PYTHON3=yes PYTHON3_VER=311 DYNAMIC_PYTHON3_DLL=pyt

Re: Mingw-make Building Vim.8.2.4398 causes error

Thank you ! Bram :) Le vendredi 18 février 2022 à 14:58:18 UTC+1, Bram Moolenaar a écrit : > > > Here are my flags > > > > FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes > LUA=./$LuaDir/src > > LUA_VER=54 \ > > PYTHON3=$Python3Dir DYNAMIC_PYTHON3=yes PYTHON3_VER=311 > > DYNAMIC_PY

Re: Mingw-make Building Vim.8.2.4398 causes error

^ mingw32-make: *** [Make_cyg_ming.mak:1274: gobji686/if_ole.o] Error 1 Le mercredi 16 février 2022 à 22:34:22 UTC+1, Ni Va a écrit : > Here is the error > > In file included from proto.h:210, > from vim.h:2244, &

Re: Mingw-make Building Vim.8.2.4398 causes error

Here is the error In file included from proto.h:210, from vim.h:2244, from if_ole.cpp:16: proto/usercmd.pro:3:76: error: expected ')' before 'compl' token 3 | char_u *set_context_in_user_cmdarg(char_u *cmd, char_u *arg, long argt, int compl, expand_T *xp, int

Mingw-make Building Vim.8.2.4398 causes error

Hi, Trying to build gvim under MSYS2 Win10 with make_ming.mak cause error. mingw-make error on attempt to build Vim.8.2.4398 gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 -DHAVE_PATHDEF -DFEAT_HUGE -DHAVE_STDINT_H -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_OLE

Re: 11. B) Building with Ruby support x64 pb

It seems to be C:\Ruby31-x64\include\ruby-3.1.0\x64-mingw-ucrt\ruby ... Le samedi 29 janvier 2022 à 21:27:38 UTC+1, Ni Va a écrit : > Hi, > > Trying to build last GVIM version with Ruby support in 64bits with mingw I > follow instructions as described in installPC.t

11. B) Building with Ruby support x64 pb

Hi, Trying to build last GVIM version with Ruby support in 64bits with mingw I follow instructions as described in installPC.txt 11.B) but encounter error of A) config.h. [image: Capture.PNG] Surprised by appearence of i386... Thank you have idea NiVa = CONFIG = Last Git Clone vim 8.2 pat

Re: [vim/vim] Conflict with vim-plug in Windows (Issue #9580)

Thank you. Le vendredi 21 janvier 2022 à 11:43:34 UTC+1, Bram Moolenaar a écrit : > Closed #9580 . > > — > Reply to this email directly, view it on GitHub > . > Triage notifications on the go with Gi

Re: Patch 8.2.4163

[image: Capture.PNG] confirmed conflict. NiVa Le jeudi 20 janvier 2022 à 23:30:31 UTC+1, Dominique Pelle a écrit : > On Thu, Jan 20, 2022 at 8:39 PM Bram Moolenaar wrote: > > > Patch 8.2.4163 > > Problem: No error for omitting function name after autoload prefix. > > Solution: Check for missing f

Re: [vim/vim] Conflict with vim-plug (Issue #9580)

Conflict confirmed with vimPlug, [ Windows 10, build ming gvim 8.2 patch 4163 [image: Capture.PNG] Le vendredi 21 janvier 2022 à 01:29:50 UTC+1, xvim64 a écrit : > Steps to reproduce > > run gvim.exe > Expected behaviour > > Load vim-plug without conflict > Version of Vim > > 8.2.4167 > Env

Re: vim startup init legacy vim versus vim9script broken ?

ok fixed in 8.2 patch 4076. Le jeudi 13 janvier 2022 à 14:47:29 UTC+1, Ni Va a écrit : > Hi, > > Sorry of this but, > is legacy vimscript or autoload broken since version gvim 8.2 path 4073 ? > > It seems or like legacy vimscript autoload is interpreted by vim9 checker >

vim startup init legacy vim versus vim9script broken ?

Hi, Sorry of this but, is legacy vimscript or autoload broken since version gvim 8.2 path 4073 ? It seems or like legacy vimscript autoload is interpreted by vim9 checker / compiler, isn't it ? Thank you for advise NiVa [image: Capture.PNG] -- -- You received this message from the "vim_d

Patch > 8.2.4073 broke old vimscript | new vim9script

Hi, Since 8.2.4073, I got this kind of below errors at gvim 8.2.4074 startup x86 under Win10. As if the legacy vimscript were checked or compiled in connection with vim9. Only found in $MYVIMRC this eventually related link to vimscript that cause errors. Thank you for your advise. NiVa comma

Re: [vim/vim] Vim9: cannot call imported function from mapping (Issue #9485)

This has changed since 8.2.4019. https://github.com/vim/vim/commit/d5f400c607182db6d4fbe2964471d796277f67e8 [image: Capture.PNG] Le vendredi 7 janvier 2022 à 04:29:46 UTC+1, Shane-XB-Qian a écrit : > yea, cannot import var from another vim9 script fs too -since yesterday > update/patch. > > —

Re: [vim/vim] Vim9: cannot call imported function from mapping (Issue #9485)

Confirmed too. import func from vim9script broken. Le vendredi 7 janvier 2022 à 04:29:46 UTC+1, Shane-XB-Qian a écrit : > yea, cannot import var from another vim9 script fs too -since yesterday > update/patch. > > — > Reply to this email directly, view it on GitHub >

Re: Gvim v8.2.3860 MSYS2 Build fails

Thank you Bram. Merry Christmas. Le mardi 21 décembre 2021 à 10:41:10 UTC+1, Bram Moolenaar a écrit : > > > Got this error trying to build Gvim above version : > > > > > > *Error* > > In file included from vim.h:434, > > from if_ole.cpp:16: > > termdefs.h:127:16: warning: unnecessary parenthese

Gvim v8.2.3860 MSYS2 Build fails

Hi All, Got this error trying to build Gvim above version : *Error* In file included from vim.h:434, from if_ole.cpp:16: termdefs.h:127:16: warning: unnecessary parentheses in declaration of 'term_strings' [-Wparentheses] 127 | extern char_u *(term_strings[]);// current t

MSYS2 Build Gvim x86 fails cause of vim9.h since 8.2.3857

Hi, Under Win10 trying to build gvim x86 fails with Make_ming under MSYS2 since 8.2.3857. *# Build Command* cd $sourcePath/vim/src make -f Make_ming.mak clean FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes LUA=./$LuaDir/src LUA_VER=54 PYTHON3=c:/Python310 DYNAMIC_PYTHON3=yes PYTHON

Gvim 8.2.3564 drag-n-drop feature broken ?

Hi, Maybe is my distribution but it seems that dropping files and dirs are no longer possible with GVim Buildx868.2.3564 on windows 10. Meanwhile I have `has('drop_file') that returns 1 and tried a starting GVIM without loading plugins with -u NONE. Even with a test without $MYVIMRC. Thanks

Issue when launching gvim build with MSYS2

Hi All, Following src/INSTALLpc.txt section MSYS Build and draft written by K.Takata, gvim 8.2.2509 seems to be well built under MSYS2 32 bits on Windows 10. On lauching GVim it fails on this issue:libgcc_s_dw2-1.dll missing, when I add this in gvim binary direcctory, it fails too on exception

Compilation issue since 8.2.2014-2017 under MSYS2

Instruction to build under MSYS2 Windows 10: FLAGS="OLE=yes GUI=yes XPM=no DIRECTx=yes DYNAMIC_LUA=yes LUA=./lua-5.3.5/src LUA_VER=53 PYTHON3=/c/Python38-32 DYNAMIC_PYTHON3=yes PYTHON3_VER=38 RUBY=C:/Ruby27 DYNAMIC_RUBY=yes RUBY_VER=27 RUBY_API_VER_LONG=2.7.0 TERMINAL=yes EVENT_LOOP=yes ST

Gvim with Lua 54 support gives error compilation

Hi, Trying to build gvim Vim.8.2.551 version under windows 10 / MSYS2 with *Lua 54 support* gives this error: > *if_lua.c:438:1: error: static declaration of 'luaL_typeerror' follows > non-static declaration* > * 438 | luaL_typeerror(lua_State *L, int narg, const char *tname)* > * | ^~~~

How about make text blinking for 8.2 version

Hi, If anyone find useful to got some informations blinking in buffer... It can be possible to do it in vimscript or C native code I think. Thank you NiVa -- -- 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

Re: netrw echoes message even if disable

Not a problem yet. Found in my own files' explorer( see joined gif) that a method used 'e .' without silent!. Thank you NiVa Le lundi 14 octobre 2019 20:18:25 UTC+2, Christian Brabandt a écrit : > > > On So, 13 Okt 2019, Ni Va wrote: > > > Hi, > >

netrw echoes message even if disable

Hi, Even with loaded plugin status to disable netrw, it echoes 'is a directory'. This in my _vimrc as it is advised, and it echoes 'is a directory'... ??? let g:loaded_netrw = 1 let g:loaded_netrwPlugin = 1 How can we disable plugin and echoing. Thank you NiVa -- -- You received this m

windows filename regex recognition

Hi, Here is a kind of filename in fat chars that I would like to recognize: * $FOOBBBAR_Ffbar_f_oobar_(2019-07-29) - Copie.zed.lnk* 232.0 KiB 2019 Thank you -- -- You received this message from the "vim_dev" maillist. Do not top-post!

Re: Vim.8.1.2102 - 32 bits on windows SegFault

Fixed since 8.1.2105. Thank you ! -- -- 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 Googl

Re: Vim.8.1.2102 - 32 bits on windows SegFault

gt; Hi, > > 2019/9/30 Mon 20:55:28 UTC+9 Ni Va wrote: >> >> Found that this command call system('which msvcrt-ruby260.dll') causes >> segfault under windows, which does not exist. >> Surprised that it causes segfault. >> >> Thank you. >> >

Re: Vim.8.1.2102 - 32 bits on windows SegFault

Found that this command call system('which msvcrt-ruby260.dll') causes segfault under windows, which does not exist. Surprised that it causes segfault. Thank you. Le lundi 30 septembre 2019 13:28:36 UTC+2, Christian Brabandt a écrit : > > > On Mo, 30 Sep 2019, Ni

Vim.8.1.2102 - 32 bits on windows SegFault

Hi, Since same compilation under windows 10 MSYS2 32bits to build , I got a seg fault on gvim launch. Sorry but gdb didn't tell me exact source. Thank you in advance. This is my build command : > make -f Make_ming.mak OLE=yes DEBUG=yes GUI=yes XPM=no DIRECTx=yes > DYNAMIC_LUA=yes LUA=./lua-

Re: Gvim 8.1 32bits crash on winOS 7 64bits

It's always on same machine and repeatable systematically. How can I launch gvim differently (with -NONE) or enable a debugger to get more infos ? Le jeudi 19 septembre 2019 17:11:07 UTC+2, Christian Brabandt a écrit : > > Can you reproduce the crash? > > Am 19.09.2019 um 15

Gvim 8.1 32bits crash on winOS 7 64bits

Hi, Here is an output of gvim crash on windows seven 64bits. Gvim 8.1 is build under MSYS with Make_ming.mak with 1-2056 patches. Signature du problème : Nom d’événement de problème: APPCRASH Nom de l’application: gvim.exe Version de l’application: 8.1.282.0 Horodatage de l’application:

Re: E484 after GVIM update

Le jeudi 23 mai 2019 08:03:20 UTC+2, Ken Takata a écrit : > Hi, > > 2019/5/23 Thu 9:36:27 UTC+9 Ken Takata wrote: > > That's too bad. > > Unfortunately, I cannot repoduce this yet. > > Does this simple case work? > > > > gvim --clean > > :echo system('dir') > > > > Does the problem occur onl

Re: E484 after GVIM update

Le jeudi 16 mai 2019 09:04:54 UTC+2, Ken Takata a écrit : > Hi, > > 2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote: > > Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit : > > > Hi, > > > > > > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote: > > >

Re: E484 after GVIM update

Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit : > Hi, > > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote: > > Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a écrit : > > > On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wrote: > > > > On Tuesd

Re: E484 after GVIM update

Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a écrit : > On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wrote: > > On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote: > > > Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > > > > Le mardi 30 avril

Re: Build error on v8.1.1210 : expected ')' before 'compl' token

Hi and thanks a lot Ken. I thought that msys2 and make ming, was less heavy than msvc. I prefer using compiler more strict. It seems that no much People is using msys2 and ming to build vim regarding up to 20 patchs to get some reply. Thank you Ken NiVa Le lun. 29 avr. 2019 à 20:20, a écrit :

Re: Build gvim x86 with Ruby support v2.6 with mingw32-make fails on conflict rb_int2big_stub

Le mardi 8 janvier 2019 15:58:05 UTC+1, Ni Va a écrit : > Hi, > > Following Pont 12. from src/installpc.txt, it seems mingw32-make build gvim > 8.1.702 with Ruby support v2.6 with fails on conflict rb_int2big_stub. > > > > > :: Enable Ruby scripting > :

Re: Build Vim with Python 3 only support with mingw32

Le mercredi 9 janvier 2019 10:48:48 UTC+1, ktakat...@gmail.com a écrit : > Hi Bram, > > 2019/1/9 Wed 17:45:23 UTC+9 Ni Va wrote: > > Le mercredi 9 janvier 2019 05:03:50 UTC+1, ktakat...@gmail.com a écrit : > > > Hi, > > > > > > 2019/1/8

Re: Build Vim with Python 3 only support with mingw32

Le mercredi 9 janvier 2019 05:03:50 UTC+1, ktakat...@gmail.com a écrit : > Hi, > > 2019/1/8 Tue 21:35:24 UTC+9 Ni Va wrote: > > Hi, > > > > Is it possible to build Vim with Python 3 support only, with mingw32 (i686) > > and not downloading msys2 but last release

Build gvim x86 with Ruby support v2.6 with mingw32-make fails on conflict rb_int2big_stub

Hi, Following Pont 12. from src/installpc.txt, it seems mingw32-make build gvim 8.1.702 with Ruby support v2.6 with fails on conflict rb_int2big_stub. :: Enable Ruby scripting :: set DYNAMIC_RUBY=yes set RUBY_VER=26 set RUBY_API_VER_LONG=2.6.0 set RUBY=C:/ThirdPart/Ruby%RUBY_VER% gcc -c -

Build Vim with Python 3 only support with mingw32

Hi, Is it possible to build Vim with Python 3 support only, with mingw32 (i686) and not downloading msys2 but last release from https://www.python.org/downloads/release/python-372/ ? According that it is an alternative to the advise from installPC.txt " When using msys2 and link with Python3

Re: Build Vim with mingw32-make and Ruby under Windows

Le mercredi 28 novembre 2018 14:43:19 UTC+1, Ni Va a écrit : > Le mercredi 28 novembre 2018 00:05:48 UTC+1, Ken Takata a écrit : > > Hi, > > > > 2018/11/28 Wed 0:33:03 UTC+9 Ni Va wrote: > > > Le mardi 27 novembre 2018 10:39:05 UTC+1, Ken Takata a écrit : > >

Re: Build Vim with mingw32-make and Ruby under Windows

Le mercredi 28 novembre 2018 00:05:48 UTC+1, Ken Takata a écrit : > Hi, > > 2018/11/28 Wed 0:33:03 UTC+9 Ni Va wrote: > > Le mardi 27 novembre 2018 10:39:05 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/11/27 Tue 18:34:10 UTC+9 Ni Va wrote: >

Re: Build Vim with mingw32-make and Ruby under Windows

Le mercredi 28 novembre 2018 00:05:48 UTC+1, Ken Takata a écrit : > Hi, > > 2018/11/28 Wed 0:33:03 UTC+9 Ni Va wrote: > > Le mardi 27 novembre 2018 10:39:05 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/11/27 Tue 18:34:10 UTC+9 Ni Va wrote: >

Re: Build Vim with mingw32-make and Ruby under Windows

Le mardi 27 novembre 2018 10:39:05 UTC+1, Ken Takata a écrit : > Hi, > > 2018/11/27 Tue 18:34:10 UTC+9 Ni Va wrote: > > Le mardi 27 novembre 2018 10:17:55 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/11/27 Tue 17:52:07 UTC+9 Ni Va wrote: >

Re: Build Vim with mingw32-make and Ruby under Windows

Le mardi 27 novembre 2018 10:17:55 UTC+1, Ken Takata a écrit : > Hi, > > 2018/11/27 Tue 17:52:07 UTC+9 Ni Va wrote: > > Hi all, > > > > > > Under Windows 10, during build of vim with mingw32-make and Ruby an error > > occurs : > > if_ruby.c

Build Vim with mingw32-make and Ruby under Windows

Hi all, Under Windows 10, during build of vim with mingw32-make and Ruby an error occurs : if_ruby.c:126:18: fatal error: ruby.h: No such file or directory compilation terminated. mingw32-make: *** [gobjx86-64/if_ruby.o] Error 1 Don't understand because I follow "help 12. Building with Rub

Re: Compile Err with Ruby : MSC version unmatch: _MSC_VER: 1912 is expected.

Le vendredi 3 août 2018 05:46:34 UTC+2, Ken Takata a écrit : > Hi, > > 2018/8/3 Fri 8:10:19 UTC+9 Ni Va wrote: > > if_ruby.obj : error LNK2001: symbole externe non résolu _rb_intern > > It seems that Vim 8.1.0232 causes the issue. > I wrote a patch for this: > http

Re: Compile Err with Ruby : MSC version unmatch: _MSC_VER: 1912 is expected.

Le jeudi 2 août 2018 16:59:50 UTC+2, Ni Va a écrit : > Le jeudi 2 août 2018 15:37:43 UTC+2, Ken Takata a écrit : > > Hi, > > > > 2018/8/2 Thu 20:44:34 UTC+9 Ni Va wrote: > > > Hi, > > > > > > Trying to compile last vim 8.1.233 x86 source, it fails

Re: Compile Err with Ruby : MSC version unmatch: _MSC_VER: 1912 is expected.

Le jeudi 2 août 2018 15:37:43 UTC+2, Ken Takata a écrit : > Hi, > > 2018/8/2 Thu 20:44:34 UTC+9 Ni Va wrote: > > Hi, > > > > Trying to compile last vim 8.1.233 x86 source, it fails on ruby config.h > > > > > > This is the issue: > > &

Re: Compile Err with Ruby : MSC version unmatch: _MSC_VER: 1912 is expected.

Le jeudi 2 août 2018 15:37:43 UTC+2, Ken Takata a écrit : > Hi, > > 2018/8/2 Thu 20:44:34 UTC+9 Ni Va wrote: > > Hi, > > > > Trying to compile last vim 8.1.233 x86 source, it fails on ruby config.h > > > > > > This is the issue: > > &

Compile Err with Ruby : MSC version unmatch: _MSC_VER: 1912 is expected.

Hi, Trying to compile last vim 8.1.233 x86 source, it fails on ruby config.h This is the issue: C:\ThirdParty\Ruby25-x86\include\ruby-2.5.0\i386-mswin32_140\ruby/config.h(4): fatal error C1189: #error: MSC version unmatch: _MSC_VER: 1912 is expected. NMAKE : fatal error U1077: '"C:\Program F

Re: Lua 5.4 32bits support

Le samedi 26 mai 2018 11:49:37 UTC+2, Kazunobu Kuriyama a écrit : > On Sat, May 26, 2018 at 5:10 AM Ni Va wrote: > > Le jeudi 24 mai 2018 21:13:35 UTC+2, Ni Va a écrit : > > > Le jeudi 24 mai 2018 15:21:34 UTC+2, Kazunobu Kuriyama a écrit : > > > > On Wed, May 23

Re: Lua 5.4 32bits support

Le jeudi 24 mai 2018 15:21:34 UTC+2, Kazunobu Kuriyama a écrit : > On Wed, May 23, 2018 at 5:56 PM Ni Va wrote: > > Hi, > > > > On Windows 10, > > > > 1. After download and build lua 5.4 current work I got a the lua.5.4.0.dll 32 > bits and rename i

Re: feature to differentiate 32 from 64 bits build version

Le mercredi 23 mai 2018 15:14:51 UTC+2, Ken Takata a écrit : > Hi, > > 2018/5/23 Wed 21:29:43 UTC+9 Ni Va wrote: > > I build both 32 and 64 bits version of gvim but always 1 is returned when > > from 32bits or 64bits I do : > > > > echo has('num64'

Re: feature to differentiate 32 from 64 bits build version

Le mercredi 23 mai 2018 14:29:43 UTC+2, Ni Va a écrit : > Hi, > > > I build both 32 and 64 bits version of gvim but always 1 is returned when > from 32bits or 64bits I do : > > echo has('num64') > echo has('win32') > echo has('win64'

feature to differentiate 32 from 64 bits build version

Hi, I build both 32 and 64 bits version of gvim but always 1 is returned when from 32bits or 64bits I do : echo has('num64') echo has('win32') echo has('win64') What the feature to differentiate the two built 32/64bits Thank you NiVa -- -- You received this message from the "vim_dev" maill

Lua 5.4 32bits support

Hi, On Windows 10, 1. After download and build lua 5.4 current work I got a the lua.5.4.0.dll 32 bits and rename it to lua54.dll guidelines : https://blog.spreendigital.de/2015/01/16/how-to-compile-lua-5-3-0-for-windows/ 2. From gvim 32 bits 8.1.020 lua print('hell') says E448: Could not

Re: Vim 8.1 is released!

Le vendredi 18 mai 2018 10:15:49 UTC+2, Tony Mechelynck a écrit : > On Fri, May 18, 2018 at 8:51 AM, Christian Brabandt > wrote: > > > > On Do, 17 Mai 2018, Bram Moolenaar wrote: > > > >> Announcing: Vim (Vi IMproved) version 8.1 > > > > Congratulation. > > > > Best, > > Christian > > After mov

Re: [vim/vim] add environ() (#2875)

Le lundi 7 mai 2018 22:17:06 UTC+2, Ni Va a écrit : > Le lundi 7 mai 2018 21:55:57 UTC+2, Bram Moolenaar a écrit : > > Ken Takata wrote: > > > > > > > > > This might be used for a workaround for the following todo item: > > > > > > > &

Re: [vim/vim] add environ() (#2875)

Le lundi 7 mai 2018 22:17:06 UTC+2, Ni Va a écrit : > Le lundi 7 mai 2018 21:55:57 UTC+2, Bram Moolenaar a écrit : > > Ken Takata wrote: > > > > > > > > > This might be used for a workaround for the following todo item: > > > > > > > &

Re: [vim/vim] add environ() (#2875)

Le lundi 7 mai 2018 21:55:57 UTC+2, Bram Moolenaar a écrit : > Ken Takata wrote: > > > > > This might be used for a workaround for the following todo item: > > > > > > > Can't recognize the $ProgramFiles(x86) environment variable. Recognize it > > > > specifically? First try with the paren

Re: How about a release?

These icons for example. 2018-04-18 22:16 GMT+02:00 Bram Moolenaar : > > Christian wrote: > > > On Do, 08 Mär 2018, Bram Moolenaar wrote: > > > > > I'm thinking of creating the 8.1 release. The main new feature is the > > > terminal window, with the debugger plugin. And lots of smaller > > > ad

How to avoidcrash for vim build with dynamic python36.dll feature

Hi, This is an extract of gvim.exe 8.0.1655 64bits ver Under Windows. ON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DDYNAMIC_PYTHON3_DLL=\"python36.dll\" and _vimrc content set pythonthreehome=c:/ThirdParty/Python36 Both if pythonthreehome is not set or the dire

Re: How about a release?

Le dimanche 18 mars 2018 12:24:38 UTC+1, Justin M. Keyes a écrit : > 2018-03-11 16:04 GMT+01:00 Bram Moolenaar : > > > > Justin M. Keyes wrote: > > > >> 2018-03-08 18:05 GMT+01:00 Bram Moolenaar : > >> > > >> > I'm thinking of creating the 8.1 release. The main new feature is the > >> > terminal w

Re: How about a release?

Le jeudi 8 mars 2018 18:05:36 UTC+1, Bram Moolenaar a écrit : > I'm thinking of creating the 8.1 release. The main new feature is the > terminal window, with the debugger plugin. And lots of smaller > additions and plenty of bug fixes. > > Is there is something important that should still be inc

Re: Optimize s:StarSetf(ft)

Le jeudi 15 mars 2018 09:58:11 UTC+1, Christian Brabandt a écrit : > On Do, 15 Mär 2018, Ni Va wrote: > > > > > Hi, > > > > According to profile report log, this func take many time just when I open > > $MYVIMRC. > > > > > > FUNCTIO

Re: Optimize s:StarSetf(ft)

/GL -DND EBUG /Zl /MT -DFEAT_OLE -DFEAT_MBYTE -DFEAT_GUI_W32 -DFEAT_DIRECTX -DDYNAMIC_DIRECTX -DFE -- More -- 2018-03-15 9:58 GMT+01:00 Christian Brabandt : > > On Do, 15 Mär 2018, Ni Va wrote: > > > > > Hi, > > > > According to profile report log, this f

Optimize s:StarSetf(ft)

Hi, According to profile report log, this func take many time just when I open $MYVIMRC. FUNCTIONS SORTED ON TOTAL TIME count total (s) self (s) function 1 4.823772 0.44 3_StarSetf() 1 2.487757 0.268725 17_SynSet() 1 2.209328 0.714291 14_LoadFTPlugin() 8

Re: diff.c :windo diffthis takes infinite time loop

admin account need elevation rights 2018-02-16 23:27 GMT+01:00 Christian Brabandt : > > On Fr, 16 Feb 2018, Ni Va wrote: > > > Le vendredi 16 février 2018 20:43:33 UTC+1, Dominique Pelle a écrit : > > > Ni Va wrote: > > > > > > > Can you test these o

Re: diff.c :windo diffthis takes infinite time loop

Le vendredi 16 février 2018 20:43:33 UTC+1, Dominique Pelle a écrit : > Ni Va wrote: > > > Can you test these ones please Dominique. > > Thank you in advance. > > Nicolas > > I diffed the 2 files in your tar file with: > > $ vim -u NONE -o localConf.xml

Re: syntax for EOF ruby/python/other lang in vimscript

Le dimanche 11 février 2018 00:49:31 UTC+1, Ni Va a écrit : > Le dimanche 11 février 2018 00:40:23 UTC+1, ZyX a écrit : > > 2018-02-11 1:58 GMT+03:00 Ni Va : > > > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : > > >> On Sat, Feb 10, 2018 at 7:29

Re: syntax for EOF ruby/python/other lang in vimscript

Le dimanche 11 février 2018 00:40:23 UTC+1, ZyX a écrit : > 2018-02-11 1:58 GMT+03:00 Ni Va : > > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : > >> On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula' via vim_use > >> wrote: > &

Re: syntax for EOF ruby/python/other lang in vimscript

Le dimanche 11 février 2018 00:01:30 UTC+1, ZyX a écrit : > 2018-02-11 1:58 GMT+03:00 Ni Va : > > Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : > >> On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula' via vim_use > >> wrote: > &

Re: syntax for EOF ruby/python/other lang in vimscript

Le samedi 10 février 2018 21:17:16 UTC+1, Tony Mechelynck a écrit : > On Sat, Feb 10, 2018 at 7:29 PM, 'Andy Wokula' via vim_use > wrote: > > Am 10.02.2018 um 17:40 schrieb Ni Va: > >> > >> Hi, > >> > >> Like :h ruby says, I use this kin

Re: vimball, vundle vimplug compatibility

Ok it's a good reason I understand well and just see :RmVimball that is able to locate and remove LargeFile.vba I just installed. Without be pro or cons of existing or newer plugin manager, git linked to or not, just wonder why not to welcome all or no one. Was just a thought around that. Thanks

Re: vimball, vundle vimplug compatibility

Hi Marc and thank you, I'd thought that runtime dir into https://github.com/vim/vim.git should be distributed up to date as compiled binary. For xml yes, I'm starting to deal with ruby nokogiri xml lib. I think it is fast but if you can advise on faster lib I will be glad. Just I wondered only o

vimball, vundle vimplug compatibility

Hi, Got a recent need to read Large Xml file, I think Large.vba from Charles E Campbell is the best plugin :http://www.drchip.org/astronaut/vim/index.html#LARGEFILE Then just wonder why vimball is integrated within vim distro and not others plugin's managers like vimplug : https://github.com/j

Re: [vim/vim] Optimize DirectX rendering (#2560)

Le mercredi 31 janvier 2018 20:52:29 UTC+1, Bram Moolenaar a écrit : > Closed #2560 via a338adc. > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub Thank you !! -- -- You received this message from the "vim_dev" mailli

Re: py3 print crash vim 8.0.1428

Le lundi 22 janvier 2018 00:33:49 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/22 Mon 3:27:56 UTC+9 Ni Va wrote: > > Le dimanche 21 janvier 2018 15:47:15 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/1/21 Sun 23:40:20 UTC+9 Ni Va wrote: > >

Re: py3 print crash vim 8.0.1428

Le lundi 22 janvier 2018 00:33:49 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/22 Mon 3:27:56 UTC+9 Ni Va wrote: > > Le dimanche 21 janvier 2018 15:47:15 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/1/21 Sun 23:40:20 UTC+9 Ni Va wrote: > >

Re: py3 print crash vim 8.0.1428

Le dimanche 21 janvier 2018 15:47:15 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/21 Sun 23:40:20 UTC+9 Ni Va wrote: > > Le vendredi 19 janvier 2018 12:06:22 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/1/19 Fri 19:49:18 UTC+9 Ni Va

Re: py3 print crash vim 8.0.1428

Le vendredi 19 janvier 2018 12:06:22 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/19 Fri 19:49:18 UTC+9 Ni Va wrote: > > 1. I delete registry entry > > > > > > 2. in _vimrc > > > > > > " Python > > > > let $pythonhome= &

Re: py3 print crash vim 8.0.1428

Le vendredi 19 janvier 2018 12:12:11 UTC+1, Ni Va a écrit : > Le vendredi 19 janvier 2018 12:06:22 UTC+1, Ken Takata a écrit : > > Hi, > > > > 2018/1/19 Fri 19:49:18 UTC+9 Ni Va wrote: > > > 1. I delete registry entry > > > > > > > > > 2.

Re: py3 print crash vim 8.0.1428

Le vendredi 19 janvier 2018 12:06:22 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/19 Fri 19:49:18 UTC+9 Ni Va wrote: > > 1. I delete registry entry > > > > > > 2. in _vimrc > > > > > > " Python > > > > let $pythonhome= &

Re: py3 print crash vim 8.0.1428

; OK Distri is now standalone. Thank you ! 2018-01-19 11:32 GMT+01:00 Ken Takata : > Hi, > > 2018/1/19 Fri 19:19:09 UTC+9 Ni Va wrote: > > Le vendredi 19 janvier 2018 11:14:22 UTC+1, Ken Takata a écrit : > > > Hi, > > > > > > 2018/1/19 Fri 18:54:35 UT

Re: [vim/vim] Optimize DirectX rendering (#2560)

Le jeudi 18 janvier 2018 14:46:41 UTC+1, K.Takata a écrit : > As reported in the following thread, Vim 8.0.1343 becomes slower on some > > environments (when using some kind of commands like :ver, :dig, ...): > > https://groups.google.com/d/topic/vim_dev/2AaZMN1T6K8/discussion > > This PR optimi

Re: py3 print crash vim 8.0.1428

Le vendredi 19 janvier 2018 11:14:22 UTC+1, Ken Takata a écrit : > Hi, > > 2018/1/19 Fri 18:54:35 UTC+9 Ni Va wrote: > > Hi, > > > > > > On Seven Machine, tests : > > 1. py3 print('hell') crash vim. > > 1. py print('hell'

py3 print crash vim 8.0.1428

Hi, On Seven Machine, tests : 1. py3 print('hell') crash vim. 1. py print('hell') print hell. - echo has('python3') returns 1 - put=$path returns : c:\thirdPartTools\python36 c:\thirdPartTools\python27 - echo system('where python36.dll') returns c:\thirdPartTools\python36\python36.dll

pythonthreedll test crash gvim

Hi, As said in help for pythonthreedll, I set pythonthreedll=python37.dll same name as DYNAMIC_PYTHON3_DLL default at compiled time. I put its path into $path in $MYVIMRC 1/ ok then, once gvim is compiled, I broke python37 distro path.(c:\thirdPartTools\python37) :echo system("where python3

Re: E370 Could not load lib : gvim 64bits and lua/ruby/python dlls.

Le vendredi 5 janvier 2018 14:32:36 UTC+1, Ni Va a écrit : > It's OK, after relaunch gvim, it echoes 1. > > > > Le 5 janv. 2018 13:59, "Ni Va" a écrit : > Le vendredi 5 janvier 2018 13:30:22 UTC+1, Ni Va a écrit : > > > This is it! 

Re: E370 Could not load lib : gvim 64bits and lua/ruby/python dlls.

It's OK, after relaunch gvim, it echoes 1. Le 5 janv. 2018 13:59, "Ni Va" a écrit : > Le vendredi 5 janvier 2018 13:30:22 UTC+1, Ni Va a écrit : > > This is it! > > > > > > Without space around '=', > > without '"' comm

  1   2   >