Re: default colorscheme highlights in red the : char in signature g:Func defined vim9script

Strange thing, it seems that solarized thème applied, thé error red : char disappear. https://github.com/lifepillar/vim-solarized8.git Le samedi 11 juin 2022 à 21:29:24 UTC+2, Ni Va a écrit : > Yes it's highlighting error. Thought it was due to sacredforest > colorscheme but no. &

Re: default colorscheme highlights in red the : char in signature g:Func defined vim9script

Yes it's highlighting error. Thought it was due to sacredforest colorscheme but no. Yes it seems to be a fix on vim syntax focused on Func declarative signature.  Le samedi 11 juin 2022 à 19:53:57 UTC+2, Bram Moolenaar a écrit : > > > default colorscheme highlights in red the : char of

default colorscheme highlights in red the : char in signature g:Func defined vim9script

Hi, default colorscheme highlights in red the : char of g:Func defined vim9script function. Just updated the vimrc_example.vim in vim9script, it displays the red : char. It's disturbing for eyes.  Nicolas [image: Capture.PNG] -- -- You received this message from the "vim_use" maillist.

Re: Profiling startuptime > menu.vim take 500ms

[image: Capture.PNG] Le mercredi 1 juin 2022 à 14:50:35 UTC+2, Ni Va a écrit : > Hi Bram, Chris, > > Sometimes I use the menu, hélas :) > > I tried set langmenu=none in first line of $MYVIMRC but it seems to get > same long time. > > If you have time to look at, this i

Re: Profiling startuptime > menu.vim take 500ms

Hi Bram, Chris, Sometimes I use the menu, hélas :) I tried set langmenu=none in first line of $MYVIMRC but it seems to get same long time. If you have time to look at, this is my purified standalone distro under win10 :

Re: Json inline format

Sorry Marc to answer quite times after.. I have solved my need by pure VimL autocommand and vim9 func. autocmd BufEnter *.json g:FormatJson() def g:FormatJson() # {{{ if ( line('$') == 1 ) # when json is not expanded silent! :%s/\("\w\+":\)\({\|\("[^"]\+"\(}*,\)\)\)/\1 \2/g

Re: Lua vim indentation

, pattern) local x=line:match(pattern) if x~=nil then return ownsplit(x, '=') end end Le mercredi 18 mai 2022 à 09:00:28 UTC+2, Ni Va a écrit : > Hi, > > DON'T HAPPENING to get correct vim lua indentation, is someone can help me > ? > >

Lua vim indentation

Hi, DON'T HAPPENING to get correct vim lua indentation, is someone can help me ? function trace(t) -- {{{ setmetatable(t,{__index={s="", f=true}}) local s, f = t[1] or t.s, t[2] or t.f -- force if dbgmode then if f then print ( os.date('%Y-%m-%d

vim9script syntax file how to deal with s:cpo_save

hi, after migrating vim to vim9script syntax file, this one embbeded these kind of lines code : *vim9scriptif exists("b:current_syntax") finishendifs:cpo_save = cpo* so i encounter these error now : "foobar.log" [converted] 12550L, 1485333B Error detected while processing BufRead

Re: Json inline format

Thank you Paul, I don't want third part. N Le samedi 7 mai 2022 à 18:56:56 UTC+2, Paul a écrit : > json_pp, or: perl -MJSON -0e 'print to_json decode_json(<>),{pretty=>1}' > > Use {pretty=>1,canonical=>1} if you want sorted keys. > > On Sat, May 07, 2022 at 04:01:

Json inline format

Hi, How can i format inline json file to multines without python tool ? Thank you -- -- You received this message from the "vim_use" 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

Re: alt gr chars bad displayed on search or command mode !

Even in insert mode, inserting backslash or others alt gr chars has regression. [image: Capture.PNG] Le samedi 23 avril 2022 à 12:31:16 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 chars bad displayed on search or command 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_use" maillist. Do not top-post! Type your reply below the text you are replying to.

Re: Embed langage print when sourcing vim9script

Thank you Bram! Maybe it's because I forgot to say I have an autocommand. I am surprised to see out of print('LuaXmlParser') when I source this vim9script. Thank you again Bram. NV # Syntax / Filetype - Helper {{{ def g:SwitchFtHelper(arg: string): void if (arg == 'leave') au!

Re: global command

Hum. Thank you Stan !  Le sam. 9 avr. 2022 à 11:25, Stan Brown a écrit : > On 2022-04-09 01:27, Ni Va wrote: > > How to not moving cursor when executing global command ? > > > > g/^EOF/call add(g:ends, line('.')) > > I don't know of any way within the g comman

global command

Hi, How to not moving cursor when executing global command ? g/^EOF/call add(g:ends, line('.')) Thank you -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Embed langage print when sourcing vim9script

Hi, Is it normal to get print of embed langage when I source vim9script ? Thank you NV def g:SwitchFtHelper(): void # Syntax / Filetype - Helper {{{ if ( !exists('g:cachebufnr') ) g:cachebufnr = bufnr('%') g:cacheft = StampedEcho( 'Cached filetype is ' .. g:cacheft .. ' and

searching for highlight color of vimLuaRegion

Hi, Got a vim9script as this and searching for embeded lua region highlight color ? def g:foobar(): void lua << EOF print('Lua Code') EOF Thank you NV -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For

loosing context and fails on second luafile luatemplate

Hi, According to luafile help I tried to execute luafile example3.lua from https://github.com/manoelcampos/xml2lua It succeded on first try "~\source\xml2lua-master\example3.lua" [unix] 37L, 1054B xml2lua v1.5-2 Manual print 1 table: 011B1040 2 table: 011B15B8 Recursive print tag

sumup some noremap exe command

Hi All, Is there a way to reduce, simplify and sumpup *those kind of* noremap *command?* Avoiding *:exe *(due to concatenate luafile + path) nnoremap lua :*exe* 'luafile ' .. expand('%:p') Avoiding *double :exe ... * command ? nnoremap lua *:exe* 'cd ' .. expand('%:p:h')* :exe* 'luafile '

Sodium xchacha20 cryptmethod vim sample

Hi, I have built vim 8.2 4663 x86 on win10 with +sodium/dyn and just want to apply it as crypt méthod, Is there a sample script ? I have libsodium-23.dll in & rtp. Thank you. NV -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text

Re: Large file - Opening n head lines

Thank you all of you. Le jeu. 17 mars 2022 à 19:24, Ni Va a écrit : > Thank you Steve i think you sum up the more efficient way. Thank you. > Nicolas.  > > Le jeu. 17 mars 2022 à 11:38, Steve Litt a > écrit : > >> Ni Va said on Thu, 17 Mar 2022 01:41:08 -

Re: Large file - Opening n head lines

Thank you Steve i think you sum up the more efficient way. Thank you. Nicolas.  Le jeu. 17 mars 2022 à 11:38, Steve Litt a écrit : > Ni Va said on Thu, 17 Mar 2022 01:41:08 -0700 (PDT) > > >Hi All, > > > >Is it possible to open a Large File Vim but just only few beginn

Re: Large file - Opening n head lines

Thank you Charles. Many years i use your largefile.vim. Thank you Charles.  Le jeu. 17 mars 2022 à 18:50, Charles Campbell a écrit : > Stan Brown wrote: > > On 2022-03-17 02:55, Lifepillar wrote: > >> On 2022-03-17, Ni Va wrote: > >>> Is it possible to open a La

Re: Large file - Opening n head lines

ifepillar wrote: > >> On 2022-03-17, Ni Va wrote: > >>> Is it possible to open a Large File Vim but just only few beginning > lines > >>> of it, edit one of these 50 first lines and then save and quit ? > >> I don't think that is possible with Vim

Large file - Opening n head lines

Hi All, Is it possible to open a Large File Vim but just only few beginning lines of it, edit one of these 50 first lines and then save and quit ? Thank you NV -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to.

Re: Out_cb callback handler in vim9

Thank you Yegappan ! Nota:probably missunderstood this with porting the legacy vimscript function that has argslist. Fu foo(...) a0[i] Endfu Le dim. 27 févr. 2022 à 15:08, Yegappan Lakshmanan a écrit : > Hi, > > On Sun, Feb 27, 2022 at 4:27 AM Ni Va wrote: > > > >

Out_cb callback handler in vim9

Hi All, In §9 of channel help is mentionned the legacy vimscript out_cb handler. " let job = job_start(command, {"out_cb": "MyHandler"}) The function will be called with the channel and a message. You would define it like this: > func MyHandler(channel, msg) " I tried this def

Re: vim9 script : how to port legacy argue

OK Thank you Le dim. 30 janv. 2022 à 18:45, bfrg a écrit : > Ni Va, > > This is explained under ':help vim9-variable-arguments'. Example: > > vim9script > def Test(...args: list) > for i in args > echo i > endfor > enddef > command -nargs=+ Tes

vim9 script : how to port legacy argue

HI, According argue used in legacy vimscript *Legacy caller* command! -nargs=? Foobar call foobar#bar#foo() *Called legacy func*. function! foobar#bar#foo (...) abort Thank! NV -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below

Re: vim9 script lambda

: > > Ni Va wrote: > > > Using this simple vim9script imported from $MYVIMRC, I encounter a > lambda > > error that I don't happen to find the origin. > > [image: Capture.PNG] > > The code you included does not have a lambda definition. You can > probab

Re: vim9 script lambda

This is a link of simple test. https://github.com/niva-xx/Zip Le dimanche 16 janvier 2022 à 16:53:16 UTC+1, Bram Moolenaar a écrit : > > Ni Va wrote: > > > Using this simple vim9script imported from $MYVIMRC, I encounter a > lambda > > error that I don't happen to fin

vim9 script lambda

Hi, Using this simple vim9script imported from $MYVIMRC, I encounter a lambda error that I don't happen to find the origin. [image: Capture.PNG] Config Win10 Gvim 8.2.4103 *Code* com! -nargs=1 -bang -complete=dir Zip call MainHelper.ZipUpDir( '') export def ZipUpDir(path: string) #{{{

Re: Pasting some yank line is slow

Hum, maybe using coc.vim with LSP clangd, it seems to be slow not on cpp but on cs file. Le samedi 15 janvier 2022 à 10:53:16 UTC+1, Ni Va a écrit : > Thank you and best wishes Mr Chase. > > > > 1) seeing mapping, it's an ocean because of vimplug and plugins > installe

Re: mix of vim9 and legacy vimscript

re you aware, that you > do not need my plugin just to be able to use Patient Diff mode? This is > all configurable by Vim using the 'diffopt' setting switch nowadays. > > Thanks, > Chris > > On Fr, 14 Jan 2022, Ni Va wrote: > > > It seems this kind of joke in red bol

Re: Pasting some yank line is slow

janvier 2022 à 16:36:25 UTC+1, Tim Chase a écrit : > On 2022-01-14 01:04, Ni Va wrote: > > I encounter a recent problem pasting some yank things (lines or > > sentences' part). > > > > don't see why because my updatetime is et to 300 and redrawtime is > > set to 5

Re: mix of vim9 and legacy vimscript

ng!' ) call s:Warn( ' not found in path, aborting ' ) return endtry Meanwhile this fix, script still often gives an *error E97 cannot create diffs* when I launch *:EnhancedDiff patience* [image: Capture.PNG][image: Capture1.PNG] Le vendredi 14 janvier 2022 à 10:00:21 UTC+1, Ni

Pasting some yank line is slow

Hi, I encounter a recent problem pasting some yank things (lines or sentences' part). don't see why because my updatetime is et to 300 and redrawtime is set to 500. Thank you. NiVA -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text

mix of vim9 and legacy vimscript

Hi Bram, Christian, Hi All, I wish to use and port some part of plugin made by Christian few years ago in order to improve dirdiff with patience algorithm. https://github.com/chrisbra/vim-diff-enhanced In vim9 help §2 it is written; *Vim9 script and legacy Vim script can be mixed. There

Re: setting clipboard register by vim9cmd or noremapping

Sorry solved as this : nnoremap cp:vim9cmd @* = expand('%:p') or from vim command line : :vim9cmd @* = expand('%:p') Le mercredi 12 janvier 2022 à 14:18:09 UTC+1, Ni Va a écrit : > Hi, > > Just would like to set clipboard register value to path of my current >

setting clipboard register by vim9cmd or noremapping

Hi, Just would like to set clipboard register value to path of my current opened file. but it seems to fail trying these : :vim9cmd @"* = expand('%:p') or in $MYVIMRC nnoremap cp:vim9cmd @"* = expand('%:p') -- -- You received this message from the "vim_use" maillist. Do

Re: vim9 Benchmark

Oh. Okay, i will look at. Thank you ! Le lun. 10 janv. 2022 à 14:55, a écrit : > > Maybe interesting for benchmark > > https://github.com/tjdevries/vim9jit > > > > If learning Rust isn't the whole purpose of the project, you might want to > look at Raku, specifically "grammars". It can be a

Re: vim9 Benchmark

I'm not a neovim user, nor am I learning rust :) I just wanted confirmation that vim9 vimnew wasn't that far behind LuaJit. And it's a good news for 2022 and futur! :) Best wishes for Vim9 and Bram too. NiVa Le lundi 10 janvier 2022 à 16:49:50 UTC+1, Dominique Pelle a écrit : > On Mon, Jan

Re: vim9 Benchmark

Maybe interesting for benchmark https://github.com/tjdevries/vim9jit Le mardi 21 décembre 2021 à 10:14:47 UTC+1, Ni Va a écrit : > Understood. > Thank you Bram. > > Le mardi 21 décembre 2021 à 10:13:09 UTC+1, Bram Moolenaar a écrit : > >> >> > Do you know i

Re: vim9 | how to force legacy vimscript execution

Similar issue: a port of interestingwords in vim9script https://github.com/niva-xx/vim9-interestingwords Le jeudi 23 décembre 2021 à 18:49:40 UTC+1, Ni Va a écrit : > resolved by porting just plugin part of this plugin in vim9script > > https://github.com/niva-xx/vim9tagbar.git > &

Re: vim9 | how to force legacy vimscript execution

resolved by porting just plugin part of this plugin in vim9script https://github.com/niva-xx/vim9tagbar.git Le jeudi 23 décembre 2021 à 15:00:22 UTC+1, Ni Va a écrit : > It seems that the problem is in interaction between vim9script | vimscript > through vimrun launch command. >

Re: vim9 | how to force legacy vimscript execution

as *TagBar* which is written in *vimscript legacy*. Le jeudi 23 décembre 2021 à 13:55:53 UTC+1, Ni Va a écrit : > Hum, I got a doubt on my used version of gvim x86 build mingw under Win10. > It seems to be daily updated as described: > > > > > > > > > > &g

Re: vim9 | how to force legacy vimscript execution

+vertsplit+cmdline_info +keymap +quickfix +virtualedit+comments +lambda +reltime +visual* Le jeudi 23 décembre 2021 à 13:47:17 UTC+1, antoine.m...@gmail.com a écrit : > On Thu, Dec 23, 2021 at 1:33 PM Ni Va wrote: > > > > Hi

Re: vim9 | how to force legacy vimscript execution

17: E10: \ should be followed by /, ? or & line 18: E10: \ should be followed by /, ? or & line 19: E10: \ should be followed by /, ? or & Le jeudi 23 décembre 2021 à 13:23:06 UTC+1, antoine.m...@gmail.com a écrit : > On Thu, Dec 23, 2021 at 10:55 AM Ni Va wrote: > > &g

vim9 | how to force legacy vimscript execution

Hi, I am currently using this legacy vimscript https://github.com/tweekmonster/startuptime.vim. It is managed by Plug.vim plugins' manager in my vim9script _vimrc. It appears startuptime.vim warns on some script code such as : *echomsg 'Tagbar: Vim versions lower than 7.0.167 have a

Re: vim9 Benchmark

Understood. Thank you Bram. Le mardi 21 décembre 2021 à 10:13:09 UTC+1, Bram Moolenaar a écrit : > > > Do you know if the stats displayed in https://github.com/brammool/vim9 > are > > updated ? > > I have not touched them for a long time. I expect Vim9 might be a bit > slower now, with the

vim9 Benchmark

Hi All, Do you know if the stats displayed in https://github.com/brammool/vim9 are updated ? Thank you NiVa -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: how to disable autocmd and augroup from plugin / autoload

I have coded this instead to remove all autocommands of the group echomsg "EnhancedDiffLayout_autocmd disabled" augroup difflayout autocmd! augroup END Le lundi 6 décembre 2021 à 13:36:41 UTC+1, Ni Va a écrit : > Hi, > > I the plugin directory vim9script

how to disable autocmd and augroup from plugin / autoload

Hi, I the plugin directory vim9script of a plugin of mine, i would like to toggle autocmd. In *plugin part*, I got this augroup foobar/*plugin*/foobar.vim augroup difflayout au! autocmd CursorHold *.tmp call EnhancedDiffLayout() augroup END meanwhile in the following *autoload

vim dirdiff autocmd bufenter disturb existence of b:currentDiff

Hi, Using Vim DirDiff plugin I have made this vim9 func to set layout and go to next diff. def g:ManageDirDiff() if ( == 'dirdiff' ) echomsg 'Manage dirdiff' if < 200 set columns=999 set lines=999 endif resize 4 windo if | setl nofoldenable | endif exec ':1,2 windo vertical

vim9 range windo question

Hi, I have switched my _vimrc in vim9script for a while. Using dirdiff I would like to resize top left window width half of screen columns. How can I execute correctly this kind of commands in vim9script ? exec '1windo vertical resize ' .. ( / 2 ) 1,2windo setl nofoldenable | norm ]c

DirDiff | how to vertical resize buffer 2 from buffer 3

Hi, Using dirdiff plugin, I would like from dirdiff buffer to resize the width of top left buffer which is too small. How without changing cursor from dirdiff bottom buffer I can change the width ? I have tried this without any success : exec 'vertical resize ' .. ( / 2) .. ' buffer 2'

Re: TagBar 2.7 and ctags 5.9 exception closed GVim win32 x86 8.2.3558

execute 'set pythonthreehome=' .. py3extenspath execute 'set pythonthreedll=' .. py3dllpath->fnamemodify(':p:gs?\\?/?') endif endif 3. Testing Py3 v3.11 interface nnoremap :exec 'py3 import sys' :exec 'py3 print(''python3 hell working'')' Le mardi 2 novembre 2021 à 14:39:04 UTC+1, Ni Va a écrit

Re: Python 311 call fails

execute 'set pythonthreehome=' .. py3extenspath execute 'set pythonthreedll=' .. py3dllpath->fnamemodify(':p:gs?\\?/?') endif endif 3. Testing Py3 v3.11 interface nnoremap :exec 'py3 import sys' :exec 'py3 print(''python3 hell working'')' Le mercredi 27 octobre 2021 à 15:58:42 UTC+2, Ni Va a é

Re: Python 311 call fails

odify(':p:gs?\\?/?')* * endif* * endif* Le mardi 2 novembre 2021 à 16:12:38 UTC+1, Ni Va a écrit : > Fixed > > Solved / Fixed : > > 1. Copied python311.dll, python3.dll, vcruntime140.dll in your distro > path expand('$vim/extensions/python/x86') > > 2. Put this in your _vim

Re: Python 311 call fails

odify(':p:gs?\\?/?')* * endif* * endif* Le mardi 2 novembre 2021 à 16:12:38 UTC+1, Ni Va a écrit : > Fixed > > Solved / Fixed : > > 1. Copied python311.dll, python3.dll, vcruntime140.dll in your distro > path expand('$vim/extensions/python/x86') > > 2. Put this in your _vim

Re: Python 311 call fails

à 15:58:42 UTC+2, Ni Va a écrit : > Hi, > > Got this error on pyhton3 print('foo') > E370: Could not load library python311.dll: Le module spcifi est > introuvable. > E263: Sorry, this command is disabled, the Python library could not be > loaded. > > This is my con

Re: TagBar 2.7 and ctags 5.9 exception closed GVim win32 x86 8.2.3558

on311.dll"')->split('\n')* * execute 'set pythonthreedll=' .. pythonthree_homes[1]->fnamemodify(':p:gs?\\?/?')* * endif* * endif* 3. Testing Py3 v3.11 interface *nnoremap :exec 'py3 import sys' :exec 'py3 print(''python3 hell working'')'* Le mardi 2 novembre 2021 à 14:39

Re: TagBar 2.7 and ctags 5.9 exception closed GVim win32 x86 8.2.3558

Tagbar plugin is executing python3 command that is closing GVim. See autoload/Tagbar.vim -> s:run_system(cmd, version) Version of python not integrated yet : 3.11.0 Le samedi 23 octobre 2021 à 13:07:02 UTC+2, Ni Va a écrit : > Hi, > > I daily use Gvim reading source code or other

Python 311 call fails

Hi, Got this error on pyhton3 print('foo') E370: Could not load library python311.dll: Le module spcifi est introuvable. E263: Sorry, this command is disabled, the Python library could not be loaded. This is my configuration 1) redir @a | echomsg system('where python311.dll') | redir END |

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

TagBar 2.7 and ctags 5.9 exception closed GVim win32 x86 8.2.3558

Hi, I daily use Gvim reading source code or other with TagBar plugin under Win10 OS under GVim 32bits x86 8.2.3558 build with ming under MSYS2. It appears that TagBarToogle it works perfectly on my physical laptop Win10 64bits meanwhile an exception seems closing Gvim under Virtual MAchine

Re: opening utf-16 fileencoded ucs-2 Little Endian

hum, now it's log UCS16 that is bad displayed. Le lun. 4 oct. 2021 à 18:02, Ni Va a écrit : > this is better : set fencs=ucs-bom,utf-8,utf16le,latin9 > > > Le lun. 4 oct. 2021 à 18:02, Ni Va a écrit : > >> it's now my vimrc bad displayed with this fencs : set >>

Re: opening utf-16 fileencoded ucs-2 Little Endian

this is better : set fencs=ucs-bom,utf-8,utf16le,latin9 Le lun. 4 oct. 2021 à 18:02, Ni Va a écrit : > it's now my vimrc bad displayed with this fencs : set > fencs=ucs-bom,utf16le,utf-8,latin9 > > > Le lun. 4 oct. 2021 à 13:39, Ni Va a écrit : > >> Hum I see Jürgen.

Re: opening utf-16 fileencoded ucs-2 Little Endian

it's now my vimrc bad displayed with this fencs : set fencs=ucs-bom,utf16le,utf-8,latin9 Le lun. 4 oct. 2021 à 13:39, Ni Va a écrit : > Hum I see Jürgen. Thank you. > > Le lun. 4 oct. 2021 à 13:24, 'Jürgen Krämer' via vim_use < > vim_use@googlegroups.com> a écrit : > &

Re: opening utf-16 fileencoded ucs-2 Little Endian

Hum I see Jürgen. Thank you. Le lun. 4 oct. 2021 à 13:24, 'Jürgen Krämer' via vim_use < vim_use@googlegroups.com> a écrit : > Hi, > > Christian Brabandt schrieb am 04.10.2021 um 12:44: > > > > On Mo, 04 Okt 2021, Ni Va wrote: > > > >> No error m

Re: opening utf-16 fileencoded ucs-2 Little Endian

Ok it works perfectly. Thank you Christian. Nicolas Le lun. 4 oct. 2021 à 12:44, Christian Brabandt a écrit : > > On Mo, 04 Okt 2021, Ni Va wrote: > > > No error message but I don't happen to read the file. > > And you did use ':e! ++enc=utf16le' for the already

Re: opening utf-16 fileencoded ucs-2 Little Endian

Hi Christian, No error message but I don't happen to read the file. [image: Capture.PNG] Here is an example file joined. Thank you. Nicolas Le lun. 4 oct. 2021 à 11:25, Christian Brabandt a écrit : > > On Fr, 01 Okt 2021, Ni Va wrote: > > > Already tested, no more r

Re: opening utf-16 fileencoded ucs-2 Little Endian

Already tested, no more result. Le ven. 1 oct. 2021 à 20:18, Christian Brabandt a écrit : > Sorry only on a phone, but you can use :e ++enc=utf16le filename or > similar > > Am 01.10.2021 um 17:38 schrieb Ni Va : > > Hi All, > > > Got NLOG facility which encode in

opening utf-16 fileencoded ucs-2 Little Endian

Hi All, Got NLOG facility which encode in unicode a logfile that i am unable to open in vim whereas configuration I made. This screenshot show the properly encoding format sawn by notepad++ (first taskbar with ucs) and the result in Vim with preconfiguration in vimrc [image: Capture.PNG] --

Re: Error in Ruby code embedded in vim9script

Ok, Can I code legacy function in a vim9script just for this case and keep all rest with def function ? Thank you Bram Le jeudi 3 juin 2021 à 21:56:57 UTC+2, Bram Moolenaar a écrit : > > Ni Va wrote: > > > This is in my _vimrc > > nnoremap :exe '!start '.expand('$vimru

Re: Error in Ruby code embedded in vim9script

Yes. This is in my _vimrc nnoremap :exe '!start '.expand('$vimruntime/gvim.exe').' -c "call readxml\#mainruby()"' Under this dir vimfiles\plugged\readxml\autoload this code is in a script called readxml.vim vim9script # MIT License. Copyright (c) 2021 June 02 Niva. # Ruby code

Error in Ruby code embedded in vim9script

Hi all, I got an error using Ruby code embedded in vim9script, seems something has changed in vim9script in this case. Like it understand $ as begin of a range no ? Thank you Error detected while compiling command line..function readxml#mainruby[1]..131_rubyCaller: line8: E1050: Colon

Re: Error Building Vim x86 32bit under MSYS2 Win10: error: ‘_UI64_MAX’

for building 32-bit Vim, otherwise select "MSYS2 MinGW 64-Bit" )." Le lundi 31 mai 2021 à 13:48:52 UTC+2, Ni Va a écrit : > Hi, > > Reading instructions in src/installPC.txt in order to build Vim x86 under > MSYS2 it appears this error : > > $ make -f Make_

Error Building Vim x86 32bit under MSYS2 Win10: error: ‘_UI64_MAX’

Hi, Reading instructions in src/installPC.txt in order to build Vim x86 under MSYS2 it appears this error : $ make -f Make_ming.mak gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF -DFEAT_HUGE -DHAVE_STDINT_H -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H

Re: Build Vim Error MSys2 Environment

Thank you. Le dimanche 30 mai 2021 à 14:02:39 UTC+2, Bram Moolenaar a écrit : > > > I encounter an error trying build Vim under Win10 OS and Msys2 with gcc > and > > make -f Make_ming.mak as is : > > > > > > > > gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 > >

Build Vim Error MSys2 Environment

Hi, I encounter an error trying build Vim under Win10 OS and Msys2 with gcc and make -f Make_ming.mak as is : gcc -c -I. -Iproto -DWIN32 -DWINVER=0x0600 -D_WIN32_WINNT=0x0600 -DHAVE_PATHDEF -DFEAT_HUGE -DHAVE_STDINT_H -DMS_WIN64 -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_OLE

Re: vim9script job function handler not recognized

' .. string(@z) enddef jobid = job_start(archive_cmd, { out_cb: Out_cb, exit_cb: Exit_cb, mode: 'raw', timeout: 3 } ) echomsg 'jobid: ' .. string(jobid) " Le vendredi 19 mars 2021 à 20:13:46 UTC+1, Bram Moolenaar a écrit : > > Ni Va wrote: > > > I got not recognized

vim9script job function handler not recognized

Hi, I got not recognized function handler starting a job in vim9script. *"* *Error detected while processing function 24_ZipUpDir:* *line 60:* *E700: Unknown function: MyHandlerCallback * " And this is the vim9script: " vim9script var jobid: job var options: dict # Job Part

Netrw pb opening directory

Hi, Some difficulties to open this kind of dir under Windows 10 gvim 8.2 2489 :e d:\Work\FOO\BAR-FOO\2-\ Sources\1-\ C++\ C\#\ Think it comes from expand func. Thank you NiVa -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are

Re: sorting lines by two first virtual column

Oh so Sorry. Windows 10. Le sam. 30 janv. 2021 à 17:25, a écrit : > > > > > I would like to sort lines by order ascendant by the alphabetical value > of > > the two first columns. > > > > Are you on Windoes, or an *nix? > > (The example file would be more useful if the input was not in order.)

Re: sorting lines by two first virtual column

I have done that kind of sort from within Vim : sort /^.\{8}\zs.\{15}\ze/ r But it ignores stamped date hour and not two first columns >> then do the same job. Le samedi 30 janvier 2021 à 19:27:41 UTC+1, rwmit...@gmail.com a écrit : > The input isn't it order. The lines ending in BAR should

sorting lines by two first virtual column

Hi, I would like to sort lines by order ascendant by the alphabetical value of the two first columns. 2021/01/13 15:05:52.417 FOO 2021/01/13 15:05:52.417 FOO 2021/01/13 15:05:52.417 FOO 2021/01/13 15:06:05.151 FOO 2021/01/13 15:06:05.151 FOO 2021/01/13 15:06:05.151 FOO 2021/01/13

Re: vim9script: dump file content to list of list question !

8:34:34 UTC+1, jottka...@googlemail.com a écrit : > > Hi, > > Ni Va schrieb am 15.01.2021 um 14:38: > > > > I got this kind of classical logfile : > > > > 2021/01/14 07:42:22.588 InformationFoo dbg > > 2021/01/14 07:42:22.588 InformationBar dbg > >

vim9script: dump file content to list of list question !

Hi, I got this kind of classical logfile : 2021/01/14 07:42:22.588 Information Foo dbg 2021/01/14 07:42:22.588 Information Bar dbg 2021/01/14 07:42:22.588 InformationFoobar dbg 2021/01/14 07:42:22.588 InformationBarbar dbg .. . and would like to add all lines' informations split

Fast Dump file content into array or dict

Hi, I got this kind of classical logfile : 2021/01/14 07:42:22.588 Information Foo dbg 2021/01/14 07:42:22.588 Information Bar dbg 2021/01/14 07:42:22.588 InformationFoobar dbg 2021/01/14 07:42:22.588 InformationBarbar dbg .. . and would like to add all lines' informations split

vim9script syntax indent/comment recognition

Hi all, It seems when I open a well formed vim9script that no recognition is working to: 1. indent def function and block corpus of function 2. new line of comment precedeed by # char at beginning of line. best wishes to all. NiVa -- -- You received this message from the "vim_use"

Re: Vim8.2.2154 html filetype detection cause error incompatiblity with vim9script

https://github.com/niva-xx/vim-sequence-diagram/blob/master/sample/CaptureOut.PNG Le lundi 21 décembre 2020 à 15:14:51 UTC+1, Ni Va a écrit : > Solved by migrating this plugin from vimscript to vim9script (adding > feature to auto open file in web browser on windows). > niva-xx/vim

Re: Vim8.2.2154 html filetype detection cause error incompatiblity with vim9script

ndi 21 décembre 2020 à 10:03:15 UTC+1, Ni Va a écrit : > In screeshot the only commented line I got grepping au Filetype html in > all my distribution. > > Le lun. 21 déc. 2020 à 09:48, Ni Va a écrit : > >> Hi Bram, >> >> >>- The only line I got grepping i

Re: vim9script _vimrc COMPATIBILITY with autocommand

So it's not possible to have in the same Vim distro: _vimrc in vim9script filetype.vim with autocommand in vimscript ? Le vendredi 18 décembre 2020 à 12:40:49 UTC+1, Bram Moolenaar a écrit : > > > > Using this plugin GitHub - xavierchow/vim-sequence-diagram: A Vim plugin > > for previewing

Vim8.2.2154 html filetype detection cause error incompatiblity with vim9script

Hi, When opening *html *file in new buffer while my _vimrc is written in vim9script, this message appears: Messages maintainer: Bram Moolenaar "~\Desktop\filetype.vim.html" 2315L, 216123B Error detected while processing BufRead Autocommands for "*.html"..function dist#ft#FThtml[13]..FileType

vim9script _vimrc COMPATIBILITY with autocommand

Hi, Using this plugin GitHub - xavierchow/vim-sequence-diagram: A Vim plugin for previewing sequence diagram in a browser . Using Vim8.2.2154 32bits under win7 with _vimrc written in vim9script, the plugin aims to output html. But at

Re: Vim9 dict key notation old fashion depreciated

Replacing by This seems good: \ networks: { *['' .. string(currnetwork) ]*: foo.undercursor.variable } Le dimanche 6 décembre 2020 à 19:27:47 UTC+1, Ni Va a écrit : > Is this notation below in red unavailable since recent Vim commits (upper > to 8.2.2194) ? > > s

Re: Vim9 dict key notation old fashion depreciated

Is this notation below in red unavailable since recent Vim commits (upper to 8.2.2194) ? s:higherInfos[apiFileLocation] = \{ blockname: \ { totalnetworks: totalnetworks, \ blocknumber: blocknumber, \ networks: { *string(currnetwork)*: foo.undercursor.variable } \}

Re: Vim9 dict key notation old fashion depreciated

part. Nota: Sorry for the Pull Request I'm newbee and a simple Vim user Le vendredi 4 décembre 2020 à 10:10:52 UTC+1, cbl...@256bit.org a écrit : > > On Fr, 04 Dez 2020, Ni Va wrote: > > > Why Benchmark does not compare Vim9 to cython instead of python ? > > Because nobod

  1   2   3   4   5   6   >