Re: E122 Def Function Vim9 already exists due to reentrancy autocommand side effect
Hum, considering this autocommand below,
I notice that it calls imported def function UnderLineHeaders() only on
the first entering file.h, not the others.
Don"t understand why ?
Thank you for help
Nicolas
--
* _vimrc: *
import autoload
'./vimfiles/plugged/foobarhelper.vim/autoload/foobarhelper.vim' as *that*
autocmd BufEnter *.cpp,*.hpp,*.h,*.c call *that*.UnderLineHeaders()
:autocmd
--- Autocommands ---
.. some other stuff
*BufEnter*
*.cpp call *that*.UnderLineHeaders()
*.hpp call *that*.UnderLineHeaders()
*.h call *that*.UnderLineHeaders() > > >> >>> works
only on first entering *.h buffer.
*.c call *that*.UnderLineHeaders()
*_autoload/myhelper/myhelper.vim: *
*export def UnderLineHeaders*(): void
echomsg 'UnderLineHeaders called for buffer ' .. expand("%:p")
some stuff
if !exists('*g:OpeningHeader')
* def g:OpeningHeader*(): void
some other stuff
*enddef*
*enddef*
Le vendredi 14 octobre 2022 à 22:34:07 UTC+2, N V a écrit :
> Solved by this prevent conditionnal test
>
> if !exists('*MyFunction') fun MyFunction ... endfun endif as described
> https://stackoverflow.com/questions/31663750/function-already-exists-vim
>
> Le vendredi 14 octobre 2022 à 22:25:29 UTC+2, N V a écrit :
>
>> Hi,
>>
>> I got reentrancy side effect with a bufenter autocommand on header
>> considering these feature.
>>
>>
>>- First def func1 is processing current buffer (cpp, h) to add
>>text_prop on header file and underline them. => works Fin
>>- Inside this func1 declare func2 to search and open underlined
>>header double cliked.
>>
>>
>> The vim9script that do the job :
>> *export def* UnderLineHeaders(): void
>>
>> var *headers*: dict = {}
>> .. some stuff
>> .. some stuff
>>
>>
>> *def* *g:OpeningHeader*(): void
>> .. some stuff
>> .. some stuff
>> *enddef*
>>
>> nnoremap <2-Leftmouse> :call *g:OpeningHeader*()
>> *enddef*
>>
>>
>>
>> The error I got when double clik on header :
>> Error detected while processing function OpeningHeader[21]..BufEnter
>> Autocommands for "*.h"..function nvhelper#UnderLineHeaders:
>> line 28:
>> *E122: *Function OpeningHeader *already exists, add ! *to replace it
>>
>>
>>
>> How can I force the g:OpeningHeader def func ?
>> Thank you
>> Nicolas
>>
>>
>> *The complete code *
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *export def UnderLineHeaders(): void var patterns: dict = {
>> 'header': '\w\+\.h' } var headers: dict = {} var list_of_line:
>> list = getline(1, '$') var lineno: number = 1 var res: string =
>> '' # identify headers' lines for line in list_of_lineres =
>> matchstr(line, patterns.header)if res != "" headers[lineno] = res
>> endiflineno = lineno + 1 endfor # some declarations before adding
>> text prop call prop_type_delete('header') hi Underlined_Header
>> ctermbg=NONE ctermfg=NONE cterm=UNDERLINE guibg=NONEguifg=NONE
>> gui=UNDERLINE call prop_type_add('header', {'highlight':
>> 'Underlined_Header'}) # add prop on headers var col: number = -1 for key
>> in keys(headers)lineno = key->str2nr()col = stridx(getline(lineno),
>> headers[key]) + 1call prop_add(lineno, col, {'length':
>> headers[key]->len(), 'type': 'header'}) endfor def g:OpeningHeader():
>> voidvar curlnum: number = getcurpos()[1]var key: string =
>> getcurpos()[1]->string()if has_key(headers, key) var searchedfile:
>> string = headers[getcurpos()[1]->string()] echomsg 'File to search for
>> is ' .. searchedfile var currentpath: list =
>> expand("%:p:h")->split('\\') var idxfolder: number = 1 var
>> maxfolders: number = currentpath->len() var foundedfile: string = ''
>> while idxfolder < maxfoldersfoundedfile = globpath(
>> currentpath[ : -1 * idxfolder ]->join('\'
Re: E122 Def Function Vim9 already exists due to reentrancy autocommand side effect
Hum, seems to be not fixed, I got this error
* _vimrc: *
autocmd BufEnter *.cpp,*.hpp,*.h,*.c call that.UnderLineHeaders()
*_autoload/myhelper/myhelper.vim: *
*export def UnderLineHeaders*(): void
echomsg 'UnderLineHeaders called for buffer ' .. expand("%:p")
some stuff
if !exists('*g:OpeningHeader')# not enough to prevent the error above
* def g:OpeningHeader*(): void
some other stuff
*enddef*
*enddef*
How to prevent
Le vendredi 14 octobre 2022 à 22:34:07 UTC+2, N V a écrit :
> Solved by this prevent conditionnal test
>
> if !exists('*MyFunction') fun MyFunction ... endfun endif as described
> https://stackoverflow.com/questions/31663750/function-already-exists-vim
>
> Le vendredi 14 octobre 2022 à 22:25:29 UTC+2, N V a écrit :
>
>> Hi,
>>
>> I got reentrancy side effect with a bufenter autocommand on header
>> considering these feature.
>>
>>
>>- First def func1 is processing current buffer (cpp, h) to add
>>text_prop on header file and underline them. => works Fin
>>- Inside this func1 declare func2 to search and open underlined
>>header double cliked.
>>
>>
>> The vim9script that do the job :
>> *export def* UnderLineHeaders(): void
>>
>> var *headers*: dict = {}
>> .. some stuff
>> .. some stuff
>>
>>
>> *def* *g:OpeningHeader*(): void
>> .. some stuff
>> .. some stuff
>> *enddef*
>>
>> nnoremap <2-Leftmouse> :call *g:OpeningHeader*()
>> *enddef*
>>
>>
>>
>> The error I got when double clik on header :
>> Error detected while processing function OpeningHeader[21]..BufEnter
>> Autocommands for "*.h"..function nvhelper#UnderLineHeaders:
>> line 28:
>> *E122: *Function OpeningHeader *already exists, add ! *to replace it
>>
>>
>>
>> How can I force the g:OpeningHeader def func ?
>> Thank you
>> Nicolas
>>
>>
>> *The complete code *
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *export def UnderLineHeaders(): void var patterns: dict = {
>> 'header': '\w\+\.h' } var headers: dict = {} var list_of_line:
>> list = getline(1, '$') var lineno: number = 1 var res: string =
>> '' # identify headers' lines for line in list_of_lineres =
>> matchstr(line, patterns.header)if res != "" headers[lineno] = res
>> endiflineno = lineno + 1 endfor # some declarations before adding
>> text prop call prop_type_delete('header') hi Underlined_Header
>> ctermbg=NONE ctermfg=NONE cterm=UNDERLINE guibg=NONEguifg=NONE
>> gui=UNDERLINE call prop_type_add('header', {'highlight':
>> 'Underlined_Header'}) # add prop on headers var col: number = -1 for key
>> in keys(headers)lineno = key->str2nr()col = stridx(getline(lineno),
>> headers[key]) + 1call prop_add(lineno, col, {'length':
>> headers[key]->len(), 'type': 'header'}) endfor def g:OpeningHeader():
>> voidvar curlnum: number = getcurpos()[1]var key: string =
>> getcurpos()[1]->string()if has_key(headers, key) var searchedfile:
>> string = headers[getcurpos()[1]->string()] echomsg 'File to search for
>> is ' .. searchedfile var currentpath: list =
>> expand("%:p:h")->split('\\') var idxfolder: number = 1 var
>> maxfolders: number = currentpath->len() var foundedfile: string = ''
>> while idxfolder < maxfoldersfoundedfile = globpath(
>> currentpath[ : -1 * idxfolder ]->join('\'), "**/" .. searchedfile )
>> if foundedfile != '' breakendifidxfolder += 1
>> endwhile echomsg foundedfile exe 'e ' .. foundedfileelse
>> echomsg 'Sorry no File to search for.'endif enddef # add double
>> clickable feature => opening header nnoremap <2-Leftmouse> :call
>> g:OpeningHeader()enddef*
>>
>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/b0f9a9c9-7f78-4c9b-82d6-71fe67a52801n%40googlegroups.com.
Re: E122 Def Function Vim9 already exists due to reentrancy autocommand side effect
Solved by this prevent conditionnal test
if !exists('*MyFunction') fun MyFunction ... endfun endif as
described
https://stackoverflow.com/questions/31663750/function-already-exists-vim
Le vendredi 14 octobre 2022 à 22:25:29 UTC+2, N V a écrit :
> Hi,
>
> I got reentrancy side effect with a bufenter autocommand on header
> considering these feature.
>
>
>- First def func1 is processing current buffer (cpp, h) to add
>text_prop on header file and underline them. => works Fin
>- Inside this func1 declare func2 to search and open underlined
>header double cliked.
>
>
> The vim9script that do the job :
> *export def* UnderLineHeaders(): void
>
> var *headers*: dict = {}
> .. some stuff
> .. some stuff
>
>
> *def* *g:OpeningHeader*(): void
> .. some stuff
> .. some stuff
> *enddef*
>
> nnoremap <2-Leftmouse> :call *g:OpeningHeader*()
> *enddef*
>
>
>
> The error I got when double clik on header :
> Error detected while processing function OpeningHeader[21]..BufEnter
> Autocommands for "*.h"..function nvhelper#UnderLineHeaders:
> line 28:
> *E122: *Function OpeningHeader *already exists, add ! *to replace it
>
>
>
> How can I force the g:OpeningHeader def func ?
> Thank you
> Nicolas
>
>
> *The complete code *
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *export def UnderLineHeaders(): void var patterns: dict = {
> 'header': '\w\+\.h' } var headers: dict = {} var list_of_line:
> list = getline(1, '$') var lineno: number = 1 var res: string =
> '' # identify headers' lines for line in list_of_lineres =
> matchstr(line, patterns.header)if res != "" headers[lineno] = res
> endiflineno = lineno + 1 endfor # some declarations before adding
> text prop call prop_type_delete('header') hi Underlined_Header
> ctermbg=NONE ctermfg=NONE cterm=UNDERLINE guibg=NONEguifg=NONE
> gui=UNDERLINE call prop_type_add('header', {'highlight':
> 'Underlined_Header'}) # add prop on headers var col: number = -1 for key
> in keys(headers)lineno = key->str2nr()col = stridx(getline(lineno),
> headers[key]) + 1call prop_add(lineno, col, {'length':
> headers[key]->len(), 'type': 'header'}) endfor def g:OpeningHeader():
> voidvar curlnum: number = getcurpos()[1]var key: string =
> getcurpos()[1]->string()if has_key(headers, key) var searchedfile:
> string = headers[getcurpos()[1]->string()] echomsg 'File to search for
> is ' .. searchedfile var currentpath: list =
> expand("%:p:h")->split('\\') var idxfolder: number = 1 var
> maxfolders: number = currentpath->len() var foundedfile: string = ''
> while idxfolder < maxfoldersfoundedfile = globpath(
> currentpath[ : -1 * idxfolder ]->join('\'), "**/" .. searchedfile )
> if foundedfile != '' breakendifidxfolder += 1
> endwhile echomsg foundedfile exe 'e ' .. foundedfileelse
> echomsg 'Sorry no File to search for.'endif enddef # add double
> clickable feature => opening header nnoremap <2-Leftmouse> :call
> g:OpeningHeader()enddef*
>
>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/d9c2d713-3ac5-4977-878f-65419f29ef49n%40googlegroups.com.
E122 Def Function Vim9 already exists due to reentrancy autocommand side effect
Hi,
I got reentrancy side effect with a bufenter autocommand on header
considering these feature.
- First def func1 is processing current buffer (cpp, h) to add text_prop
on header file and underline them. => works Fin
- Inside this func1 declare func2 to search and open underlined
header double cliked.
The vim9script that do the job :
*export def* UnderLineHeaders(): void
var *headers*: dict = {}
.. some stuff
.. some stuff
*def* *g:OpeningHeader*(): void
.. some stuff
.. some stuff
*enddef*
nnoremap <2-Leftmouse> :call *g:OpeningHeader*()
*enddef*
The error I got when double clik on header :
Error detected while processing function OpeningHeader[21]..BufEnter
Autocommands for "*.h"..function nvhelper#UnderLineHeaders:
line 28:
*E122: *Function OpeningHeader *already exists, add ! *to replace it
How can I force the g:OpeningHeader def func ?
Thank you
Nicolas
*The complete code *
*export def UnderLineHeaders(): void var patterns: dict = {
'header': '\w\+\.h' } var headers: dict = {} var list_of_line:
list = getline(1, '$') var lineno: number = 1 var res: string =
'' # identify headers' lines for line in list_of_lineres =
matchstr(line, patterns.header)if res != "" headers[lineno] = res
endiflineno = lineno + 1 endfor # some declarations before adding
text prop call prop_type_delete('header') hi Underlined_Header
ctermbg=NONE ctermfg=NONE cterm=UNDERLINE guibg=NONEguifg=NONE
gui=UNDERLINE call prop_type_add('header', {'highlight':
'Underlined_Header'}) # add prop on headers var col: number = -1 for key
in keys(headers)lineno = key->str2nr()col = stridx(getline(lineno),
headers[key]) + 1call prop_add(lineno, col, {'length':
headers[key]->len(), 'type': 'header'}) endfor def g:OpeningHeader():
voidvar curlnum: number = getcurpos()[1]var key: string =
getcurpos()[1]->string()if has_key(headers, key) var searchedfile:
string = headers[getcurpos()[1]->string()] echomsg 'File to search for
is ' .. searchedfile var currentpath: list =
expand("%:p:h")->split('\\') var idxfolder: number = 1 var
maxfolders: number = currentpath->len() var foundedfile: string = ''
while idxfolder < maxfoldersfoundedfile = globpath(
currentpath[ : -1 * idxfolder ]->join('\'), "**/" .. searchedfile )
if foundedfile != '' breakendifidxfolder += 1
endwhile echomsg foundedfile exe 'e ' .. foundedfileelse
echomsg 'Sorry no File to search for.'endif enddef # add double
clickable feature => opening header nnoremap <2-Leftmouse> :call
g:OpeningHeader()enddef*
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/264f2b7f-3f8d-453a-a38b-5b20e5c45023n%40googlegroups.com.
Getting reentrancy side effect with autocmd.
Hi,
I got reentrancy side effect with a bufenter autocommand on header
considering these feature.
- First def func1 is processing current buffer (cpp, h) to add text_prop
on header file and underline them. => works Fin
- Inside this func1 declare func2 to search and open underlined
header double cliked.
The vim9script that do the job :
*export def* UnderLineHeaders(): void
var *headers*: dict = {}
.. some stuff
.. some stuff
*def* *g:OpeningHeader*(): void
.. some stuff
.. some stuff
*enddef*
nnoremap <2-Leftmouse> :call *g:OpeningHeader*()
*enddef*
The error I got when double clik on header :
Error detected while processing function OpeningHeader[21]..BufEnter
Autocommands for "*.h"..function nvhelper#UnderLineHeaders:
line 28:
E122: Function OpeningHeader already exists, add ! to replace it
How can I force the g:OpeningHeader def func ?
Thank you
Nicolas
The complete code
export def UnderLineHeaders(): void
var patterns: dict = { 'header': '\w\+\.h' }
var headers: dict = {}
var list_of_line: list = getline(1, '$')
var lineno: number = 1
var res: string = ''
# identify headers' lines
for line in list_of_line
res = matchstr(line, patterns.header)
if res != ""
headers[lineno] = res
endif
lineno = lineno + 1
endfor
# some declarations before adding text prop
call prop_type_delete('header')
hi Underlined_Headerctermbg=NONE ctermfg=NONE cterm=UNDERLINE
guibg=NONEguifg=NONE gui=UNDERLINE
call prop_type_add('header', {'highlight': 'Underlined_Header'})
# add prop on headers
var col: number = -1
for key in keys(headers)
lineno = key->str2nr()
col = stridx(getline(lineno), headers[key]) + 1
call prop_add(lineno, col, {'length': headers[key]->len(), 'type':
'header'})
endfor
def g:OpeningHeader(): void
var curlnum: number = getcurpos()[1]
var key: string = getcurpos()[1]->string()
if has_key(headers, key)
var searchedfile: string = headers[getcurpos()[1]->string()]
echomsg 'File to search for is ' .. searchedfile
var currentpath: list = expand("%:p:h")->split('\\')
var idxfolder: number = 1
var maxfolders: number = currentpath->len()
var foundedfile: string = ''
while idxfolder < maxfolders
foundedfile = globpath( currentpath[ : -1 * idxfolder ]->join('\'),
"**/" .. searchedfile )
if foundedfile != ''
break
endif
idxfolder += 1
endwhile
echomsg foundedfile
exe 'e ' .. foundedfile
else
echomsg 'Sorry no File to search for.'
endif
enddef
# add double clickable feature => opening header
nnoremap <2-Leftmouse> :call g:OpeningHeader()
enddef
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/3ecb6d5d-8bc1-44a0-9e9e-e798549c1695n%40googlegroups.com.
Re: Gutentags plugin autoload command not recognized by Vim9
Confirmed that scriptnames output returns vimfiles/plugged/vim-gutentags/plugin/gutentags.vim and autoload/gutentags.vim And E117: Unknown function: gutentag#setup_gutentags is output on the call from $VIMRUNTIME. Sumup: i noticed since vim9 that it is not convenaient way to have to open and source manually autoload part of existing vimscripts. Not convenient. Nicolas Le vendredi 14 octobre 2022 à 10:23:16 UTC+2, cbl...@256bit.org a écrit : > > On Fr, 14 Okt 2022, N V wrote: > > > Hi, > > > > Using Vim9 64bits build on Win10 patch 0744, > > with some plugins installed from vimplug, as gutentags > > https://github.com/ludovicchabant/vim-gutentags which has some command > in $vim/vimfiles/plugged/vim-gutentags/autoload/gutentags.vim such as > Gutentags Update. > > > > Why this command :GutentagsUpdate is not known by Vim ? > > > > E492: Not an editor command : GutentagsUpdate > > It looks like this command is defined in an autoload script (and only > inside the function gutentags#setup_gutentags()), so it is only > available, once that function has been called (and the autoload script > has been sourced). > > Check the output of :sriptnames if it is read and possibly just call > gutentags#setup_gutentags() before calling that command. > > > Best, > Christian > -- > Eitelkeit ist der Wunsch, bei dem, was man tut, gesehen zu werden. > -- Heide Simonis > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ea126f2f-6fb9-445b-a321-e25a61249f92n%40googlegroups.com.
Re: windo diffthis starting on certain column of lines
Thought it was possible and easily to do or adapt 'sorting particular column' but for Dirdiff. As this. https://stackoverflow.com/questions/1355004/how-to-sort-numeric-and-literal-columns-in-vim/1355023#1355023 Thank you Nicolas Le vendredi 7 octobre 2022 à 11:14:25 UTC+2, cbl...@256bit.org a écrit : > > On Fr, 07 Okt 2022, N V wrote: > > > Hi, > > > > I have to compare two files' content with 'windo diffthis'. > > The begin of lines of these files are not significant and have to > ignore/exclude it from 0 to n column. > > > > > > I would like to know if there is option to Automate this with windo > diffthis. > > Not automatically, you would need to manually prepare the files (e.g. > delete columns you want to be ignored). Once you know the commands, you > can of course put that into a :windo command > > > Best, > Christian > -- > Ein Mensch ist so alt wie seine Ansichten. > -- Gerhard Kocher > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/fb201c52-b5b4-4387-b837-403ccfcee5a8n%40googlegroups.com.
Gutentags plugin autoload command not recognized by Vim9
Hi, Using Vim9 64bits build on Win10 patch 0744, with some plugins installed from vimplug, as gutentags https://github.com/ludovicchabant/vim-gutentags which has some command in $vim/vimfiles/plugged/vim-gutentags/autoload/gutentags.vim such as Gutentags Update. Why this command :GutentagsUpdate is not known by Vim ? E492: Not an editor command : GutentagsUpdate Thanks 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 more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d01058f4-7c8e-4624-a2db-3da06bb8526dn%40googlegroups.com.
windo diffthis starting on certain column of lines
Hi, I have to compare two files' content with 'windo diffthis'. The begin of lines of these files are not significant and have to ignore/exclude it from 0 to n column. I would like to know if there is option to Automate this with windo diffthis. Thank you Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/48ac1ceb-6ad4-4343-acd5-ea8e4a311caan%40googlegroups.com.
Re: vim-plug commands (PlugUpdate, PlugInstall) broken due to vim9 patch or $HOME
Sorry, git client was missing. My $HOME is empty string. My $VIM is 'good/parhto/Vim' dir. Le samedi 1 octobre 2022 à 20:20:12 UTC+2, xigb...@gmail.com a écrit : > I currently use Vim9 and vim-plug is working fine. > > I'm beta-testing switching completely to vim9script at > https://github.com/igbanam/dotfiles/pull/16. > > Where would you need $HOME/vimfile? > > I'm thinking if that breaks, expanding $HOME may help? > > Let me know. > > > - Igbanam. > > > > On Fri, 30 Sept 2022, 19:50 N V, wrote: > >> Hi, >> >> It's been several months that I switched to vim9script and the fact is >> that historical use of vim-plug is broken. >> https://github.com/junegunn/vim-plug >> >> No more command from this plugin are recognized. >> >> >> It sounds like some patch cause issue or $HOME that is effectively void >> in my configuration does not return good path for startup : $HOME/vimfile >> returns -9223372036854775808. >> >> >> I saw recent post on $HOME without seeing a workaround or solution. >> >> 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 more information, visit http://www.vim.org/maillist.php >> >> --- >> You received this message because you are subscribed to the Google Groups >> "vim_use" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to vim_use+u...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vim_use/7b4b407b-f155-4eac-b6ea-22271b9b750fn%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vim_use/7b4b407b-f155-4eac-b6ea-22271b9b750fn%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/9342a5cb-f043-47dd-a38b-e8436c6a9d6bn%40googlegroups.com.
vim-plug commands (PlugUpdate, PlugInstall) broken due to vim9 patch or $HOME
Hi, It's been several months that I switched to vim9script and the fact is that historical use of vim-plug is broken. https://github.com/junegunn/vim-plug No more command from this plugin are recognized. It sounds like some patch cause issue or $HOME that is effectively void in my configuration does not return good path for startup : $HOME/vimfile returns -9223372036854775808. I saw recent post on $HOME without seeing a workaround or solution. 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 more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/7b4b407b-f155-4eac-b6ea-22271b9b750fn%40googlegroups.com.
Re: Announce: LitREPL plugin for literate programming
Hi Sergei, Do you know codi.vim ? https://github.com/metakirby5/codi.vim What's the main difference with your plugin ? Thank you Nicolas Le jeudi 25 août 2022 à 13:43:07 UTC+2, grr...@gmail.com a écrit : > Hello. I'm glad to announce a (yet another) plugin for literate > programming, for now in Python. Briefly, it aims to get a Jupyter-notebook > look-and-feel while editing Markdown or Latex documents in Vim. > > https://github.com/grwlf/litrepl.vim > > The plugin detects code/result blocks, pipes their content through the > persistently running interpreter and pastes the result back into the file. > Python and IPython are currently supported, other languages don't seem to > be a problem. > > Currently, the plugin comes with an application of nearly 500 lines of > code and takes less than 100 lines of code itself at the cost of being > dependent on Posix APIs like pipes or shell utils. > > The project is less than a month old, some troubles are possible. Brave > testers are welcome, as well as comments. > > BR, > Sergei > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/bc99067a-71d0-44b3-bc8e-72bb5af21893n%40googlegroups.com.
Re: vim9 exported functions not recognized by ctags
For extended powershell script, displaying functions with tagbar see this:
https://github.com/preservim/tagbar/issues/830
If it can help.
Have a good Day.
Nicolas
Le vendredi 12 août 2022 à 16:19:16 UTC+2, N V a écrit :
> And YES It Is !! :)
>
> Windows configuration of *vim9script ctags* extension
>
>
> *1/ In your $MYVIMRC ~_vimrc (here vim9script) just put these lines :*
>
> g:tagbar_type_vim = {
>kinds: [
>
> \ 'a:autocommand groups:1',
> \ 'c:commands:0:0',
> \ 'e:exported defs',
> \ 'f:functions',
> \ 'g:global variables',
> \ 'K:constants',
>
> \ 'm:maps:1:0',
> \ 'n:vimball filenames',
> \ 'v:variables:1:0',
> \ ],
> }
>
> *2/ In your $vimruntime ~ vim90 folder where there is ctags.exe v5.9 just
> add file in folder .ctags.d/vim.ctags*
>
> --kinddef-vim=e,export,Vim 9 exported defs
> --kinddef-vim=g,global,Vim 9 global variables
> --kinddef-vim=K,const,Vim 9 constants
> --regex-vim=/^\s*export\s+def\s+([^(]+)/\1/e,export/
> --regex-vim=/^\s*(g:\w+)\b/\1/g,global/
> --regex-vim=/^(\s*export\s+)?const\s+(\w+)/\2/K,const/
> --regex-vim=/^(\s*export\s+)?final\s+(\w+)/\2/K,const/
>
>
>
>
> and see the light : all exported defs vim9script functions are now
> displayed ! :) :)
> [image: Capture.PNG]
>
>
>
> THANK YOU Life !!
> Hope this help someone.
> Nicolas
> Le jeudi 11 août 2022 à 19:55:48 UTC+2, Lifepillar a écrit :
>
>> On 2022-08-11, N V wrote:
>> > So I put it in *somewhereOvertherainbow\*Vim\vim90\.ctags.d
>>
>> If you put Ctags configuration there, does `ctags --list-kinds=vim`
>> still use it?
>>
>> > But it seems to not runnning well : does not displays vim9 exported
>> > functions
>>
>> I'm afraid I can't help you with Windows-specific configuration, as I'm
>> not using Windows.
>>
>> Life.
>>
>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/7e50faf3-93dc-42e9-9cf8-1149ee1106d0n%40googlegroups.com.
Re: vim9 exported functions not recognized by ctags
- Considering the help here https://docs.ctags.io/en/latest/man/ctags.1.html#ctags-1 It does not work for me with .ctags.d in $HOMEPATH * 2.1.14 FILES * *tags The default tag file created by ctags. * *TAGS The default tag file created by etags. * *$XDG_CONFIG_HOME/ctags/*.ctags, or $HOME/.config/ctags/*.ctags if * *$XDG_CONFIG_HOME is not defined (on other than MS Windows) * *$HOME/.ctags.d/*.ctags * *$HOMEDRIVE$HOMEPATH/ctags.d/*.ctags (on MS Windows only) * *.ctags.d/*.ctags ctags.d/*.ctags * - It works only if i change to directory embedding .ctags.d before launch ctags.exe --list-kinds=vim *Results* : *somewhereOverTheRainbow\Vim\vim90>dir .ctags.d Répertoire de somewhereOverTheRainbow\Vim\vim90\.ctags.d12/08/2022 05:30 .12/08/2022 05:30 ..12/08/2022 04:24 337 vim.ctags 1 fichier(s) 337 octets 2 Rép(s) 135 332 417 536 octets libressomewhereOverTheRainbow\Vim\vim90>ctags --list-kinds=vima autocommand groupsc user-defined commandsf function definitionsm mapsv variable definitionsn vimball filenameC constant definitionse Vim 9 exported defsg Vim 9 global variablesK Vim 9 constantssomewhereOverTheRainbow\Vim\vim90>cd ..somewhereOverTheRainbow\Vim>.\vim90\ctags.exe --list-kinds=vima autocommand groupsc user-defined commandsf function definitionsm mapsv variable definitionsn vimball filenameC constant definitions* Or maybe I have to add to in Vim the folder that contains .ctags.d Le jeudi 11 août 2022 à 19:55:48 UTC+2, Lifepillar a écrit : > On 2022-08-11, N V wrote: > > So I put it in *somewhereOvertherainbow\*Vim\vim90\.ctags.d > > If you put Ctags configuration there, does `ctags --list-kinds=vim` > still use it? > > > But it seems to not runnning well : does not displays vim9 exported > > functions > > I'm afraid I can't help you with Windows-specific configuration, as I'm > not using Windows. > > Life. > > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/3cb510b6-c4ab-4d6e-b710-54264272d065n%40googlegroups.com.
Re: vim9 exported functions not recognized by ctags
Don't worry neither afraid. It will be solved soon.. Le jeu. 11 août 2022 à 19:55, Lifepillar a écrit : > On 2022-08-11, N V wrote: > > So I put it in *somewhereOvertherainbow\*Vim\vim90\.ctags.d > > If you put Ctags configuration there, does `ctags --list-kinds=vim` > still use it? > > > But it seems to not runnning well : does not displays vim9 exported > > functions > > I'm afraid I can't help you with Windows-specific configuration, as I'm > not using Windows. > > Life. > > -- > -- > 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 this message because you are subscribed to a topic in the > Google Groups "vim_use" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vim_use/hp4KeIsDlFU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > vim_use+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vim_use/td3fqm%24i13%241%40ciao.gmane.io > . > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAOKxv4Em6aj%2BZ9r2eFxUurLZ3bXvaOh7mj9N%2BtrhNqxxjbQ0rw%40mail.gmail.com.
Re: New version of vim unsolicitedly sourcing defaults.vim?
Hi Tim, Bram, In a "gradient minimalist" mode of vim, devoid of plugins, it might be interesting to have a file that contains the necessary facilities by default. In particular facilities, features allowing you to switch from this minimalist Vim mode to a more extensive mode including personal plugins and other functions... As long as the defaults.vim file is in the same folder as $MYVIMRC, is the defaults.vim file sourced on Vim startup? I personally need this functionnality : in Vim minimalist "*degraded*"mode :*defaults.vim* is the only in $vimso facilities *it *is embedding are sourced in Vim extended"*operational*" mode :*both **defaults.vim* *and **_vimrc *are in $vim,so facilities *_vimrc *is embedding are sourced. Is it possible Bram ? Thank you Nicolas Le mercredi 10 août 2022 à 15:21:50 UTC+2, Tim Chase a écrit : > On Wed, Aug 10, 2022 at 11:07:55AM +0100, Bram Moolenaar wrote: > >Tim Chase wrote: > >> Yep, as Yegappan found, this bug is tracking the issue at hand: > >> > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251420 > >> > >> I've got a FreeBSD Bugzilla account and will follow up there. > [snip] > > An alternative would be to check if ~/.vimrc exists, and only load > > defaults.vim then. Then it's closer to what Vim normally does (but then > > the overrides may still confuse the user). > > That's one of the solutions I proposed in that bug-tracking URL, > though it's complicated because it's not just a .vimrc but according > to docs, but it sounds like ~/.vim/vimrc or ~/_vimrc or ~/.exrc or > ~/_exrc or $MYVIMRC or $VIMINIT or $VIM or $EXINIT might also prevent > defaults.vim from loading. And I'm not 100% certain that list is > complete. > > So it sounds like it would require a big chained if-statement testing > filereadable() on all of those sources and only sourcing defaults.vim > if *none* of them exist. > > -tim > > > > > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/ec8e2445-8da6-47bb-b30c-ce6fe8c861e8n%40googlegroups.com.
vim9 exported functions not recognized by ctags
Hi, Exported functions in New vim9 are not found by exubérant ctags, universal ctags and not displayed by tagbar plugin https://github.com/preservim/tagbar Is there a work around. Thank you Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/a69f1be9-66e6-41ab-a2dc-1f51747f896an%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
stay that, inside $MYVIMRC opened buffer, I have to source it at less one
time manually.
Maby side effect of these autocmd
# autowrite autosource
autocmd! CursorHold$MYVIMRC w! $MYVIMRC
autocmd! BufWritePost $MYVIMRC source $MYVIMRC
Le jeudi 4 août 2022 à 10:25:45 UTC+2, N V a écrit :
> ok it succeed, was the name of script.
>
> Le jeudi 4 août 2022 à 10:07:55 UTC+2, Maxim Kim a écrit :
>
>> Why don't you use `import autoload 'nv-helper.vim' as that` ?
>>
>> PS, have you ever considered :h hl-CurSearch instead?
>> It doesn't blink but you can set up a different color for a current
>> search under cursor
>> [image: Screenshot 2022-08-04 150726.png]
>>
>> четверг, 4 августа 2022 г. в 14:32:45 UTC+7, niva...@gmail.com:
>>
>>> Thank you Maxim, this is what i've done yesterday.
>>>
>>> But it does not solve two problems :
>>>
>>>1. first when I open $MYVIMRC and search for a word as 'import' it
>>>does not call imported that.HLNExt func, I HAVE TO SOURCE $MYVIMRC
>>> ANOTEHR
>>>TIME
>>>2. then, when I search forward for import it blinks the word
>>>occurence searched where cursor is on, then searching backwards with N
>>> it
>>>seems to work until I attempt to search forward one more time and the
>>>blinking feature does not appear anymore.
>>>
>>>
>>> You can see it :
>>> https://drive.google.com/file/d/1q0hn3h4u05jpClaiAC_kn8DMnYrRymE9/view?usp=sharing
>>>
>>> Le jeudi 4 août 2022 à 06:52:50 UTC+2, Maxim Kim a écrit :
>>>
>>>> *> nnoremap n n*that.HLNext(80)
>>>>
>>>> remove to see messages, also `:` is not needed.
>>>>
>>>> Also in the gif you are importing with the full path, not sure if it
>>>> matters.
>>>>
>>>> среда, 3 августа 2022 г. в 20:31:47 UTC+7, niva...@gmail.com:
>>>>
>>>>> Thank you Bram,
>>>>>
>>>>>- I added as described.
>>>>>- Can you just look at this gif that shows that I have to source
>>>>>$MYVIMRC to take account an import vim9script, then the function that
>>>>> blink
>>>>>the searched work is working.
>>>>>
>>>>>
>>>>>
>>>>> https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/view?usp=sharing
>>>>>
>>>>> Le mercredi 3 août 2022 à 12:05:05 UTC+2, N V a écrit :
>>>>>
>>>>>> Import is now successfull, what is now wrong is overloading mapping
>>>>>> as intended by D.Conway
>>>>>> https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
>>>>>> as this :
>>>>>>
>>>>>> # Imported Functions {{{
>>>>>> import autoload 'nvhelper.vim' as that
>>>>>> # nnoremap that.HLNext(80) # CALL
>>>>>> SUCCESS
>>>>>> *nnoremap n n:* that.HLNext(80) #
>>>>>> FAILS GOTO NEXT
>>>>>> nnoremap N N: that.HLNext(80)
>>>>>>
>>>>>>
>>>>>>
>>>>>> It seems to goto one time to item searched but don't do next jump.
>>>>>> Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>>>>>>
>>>>>>>
>>>>>>> > Would import vim9 script as that. It seems to work when I directly
>>>>>>> call
>>>>>>> > that.foobar.
>>>>>>> >
>>>>>>> > But how to map the same call in a nnoremapping ?
>>>>>>> > Thank you
>>>>>>> > NV
>>>>>>> >
>>>>>>> >
>>>>>>> > # Imported Functions {{{
>>>>>>> > import './vimfiles/autoload/nvhelper.vim' as that
>>>>>>> > nnoremap n n:call that.HLNext(80)
>>>>>>> > nnoremap N N:call that.HLNext(80)
>>>>>>>
>>>>>>> Use ":help import-legacy" and then go up a few lines.
>>>>>>>
>>>>>>> --
>>>>>>> The term "free software" is defined by Richard M. Stallman as
>>>>>>> being software that isn't necessarily for free. Confusing?
>>>>>>> Let's call it "Stallman software" then!
>>>>>>> -- Bram Moolenaar
>>>>>>>
>>>>>>> /// Bram Moolenaar -- br...@moolenaar.net --
>>>>>>> http://www.Moolenaar.net \\\
>>>>>>> /// \\\
>>>>>>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
>>>>>>> ///
>>>>>>> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>>>>>>>
>>>>>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/a6abb55a-201b-4f51-a706-912b5b8e07f0n%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
ok it succeed, was the name of script.
Le jeudi 4 août 2022 à 10:07:55 UTC+2, Maxim Kim a écrit :
> Why don't you use `import autoload 'nv-helper.vim' as that` ?
>
> PS, have you ever considered :h hl-CurSearch instead?
> It doesn't blink but you can set up a different color for a current search
> under cursor
> [image: Screenshot 2022-08-04 150726.png]
>
> четверг, 4 августа 2022 г. в 14:32:45 UTC+7, niva...@gmail.com:
>
>> Thank you Maxim, this is what i've done yesterday.
>>
>> But it does not solve two problems :
>>
>>1. first when I open $MYVIMRC and search for a word as 'import' it
>>does not call imported that.HLNExt func, I HAVE TO SOURCE $MYVIMRC
>> ANOTEHR
>>TIME
>>2. then, when I search forward for import it blinks the word
>>occurence searched where cursor is on, then searching backwards with N it
>>seems to work until I attempt to search forward one more time and the
>>blinking feature does not appear anymore.
>>
>>
>> You can see it :
>> https://drive.google.com/file/d/1q0hn3h4u05jpClaiAC_kn8DMnYrRymE9/view?usp=sharing
>>
>> Le jeudi 4 août 2022 à 06:52:50 UTC+2, Maxim Kim a écrit :
>>
>>> *> nnoremap n n*that.HLNext(80)
>>>
>>> remove to see messages, also `:` is not needed.
>>>
>>> Also in the gif you are importing with the full path, not sure if it
>>> matters.
>>>
>>> среда, 3 августа 2022 г. в 20:31:47 UTC+7, niva...@gmail.com:
>>>
>>>> Thank you Bram,
>>>>
>>>>- I added as described.
>>>>- Can you just look at this gif that shows that I have to source
>>>>$MYVIMRC to take account an import vim9script, then the function that
>>>> blink
>>>>the searched work is working.
>>>>
>>>>
>>>>
>>>> https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/view?usp=sharing
>>>>
>>>> Le mercredi 3 août 2022 à 12:05:05 UTC+2, N V a écrit :
>>>>
>>>>> Import is now successfull, what is now wrong is overloading mapping as
>>>>> intended by D.Conway
>>>>> https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
>>>>> as this :
>>>>>
>>>>> # Imported Functions {{{
>>>>> import autoload 'nvhelper.vim' as that
>>>>> # nnoremap that.HLNext(80) # CALL
>>>>> SUCCESS
>>>>> *nnoremap n n:* that.HLNext(80) # FAILS
>>>>> GOTO NEXT
>>>>> nnoremap N N: that.HLNext(80)
>>>>>
>>>>>
>>>>>
>>>>> It seems to goto one time to item searched but don't do next jump.
>>>>> Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>>>>>
>>>>>>
>>>>>> > Would import vim9 script as that. It seems to work when I directly
>>>>>> call
>>>>>> > that.foobar.
>>>>>> >
>>>>>> > But how to map the same call in a nnoremapping ?
>>>>>> > Thank you
>>>>>> > NV
>>>>>> >
>>>>>> >
>>>>>> > # Imported Functions {{{
>>>>>> > import './vimfiles/autoload/nvhelper.vim' as that
>>>>>> > nnoremap n n:call that.HLNext(80)
>>>>>> > nnoremap N N:call that.HLNext(80)
>>>>>>
>>>>>> Use ":help import-legacy" and then go up a few lines.
>>>>>>
>>>>>> --
>>>>>> The term "free software" is defined by Richard M. Stallman as
>>>>>> being software that isn't necessarily for free. Confusing?
>>>>>> Let's call it "Stallman software" then!
>>>>>> -- Bram Moolenaar
>>>>>>
>>>>>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net
>>>>>> \\\
>>>>>> /// \\\
>>>>>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
>>>>>> ///
>>>>>> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>>>>>>
>>>>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/331d80d8-43dc-4a0e-aa6a-81a4ec693554n%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
Oh ok thank you Maxim.it solved blinking in forward backward.
But I have always to source $MYVIMRC twice, when I am within it.
Le jeudi 4 août 2022 à 10:11:17 UTC+2, Maxim Kim a écrit :
> Also please note that space between n and might be something
> you don't want.
> Basically your n mapping does `n` then `` (which is cursor right)
> and then your scriptcmd...
>
> четверг, 4 августа 2022 г. в 14:32:45 UTC+7, niva...@gmail.com:
>
>> Thank you Maxim, this is what i've done yesterday.
>
>
>> But it does not solve two problems :
>>
>>1. first when I open $MYVIMRC and search for a word as 'import' it
>>does not call imported that.HLNExt func, I HAVE TO SOURCE $MYVIMRC
>> ANOTEHR
>>TIME
>>2. then, when I search forward for import it blinks the word
>>occurence searched where cursor is on, then searching backwards with N it
>>seems to work until I attempt to search forward one more time and the
>>blinking feature does not appear anymore.
>>
>>
>> You can see it :
>> https://drive.google.com/file/d/1q0hn3h4u05jpClaiAC_kn8DMnYrRymE9/view?usp=sharing
>>
>> Le jeudi 4 août 2022 à 06:52:50 UTC+2, Maxim Kim a écrit :
>>
>>> *> nnoremap n n*that.HLNext(80)
>>>
>>> remove to see messages, also `:` is not needed.
>>>
>>> Also in the gif you are importing with the full path, not sure if it
>>> matters.
>>>
>>> среда, 3 августа 2022 г. в 20:31:47 UTC+7, niva...@gmail.com:
>>>
>>>> Thank you Bram,
>>>>
>>>>- I added as described.
>>>>- Can you just look at this gif that shows that I have to source
>>>> $MYVIMRC to take account an import vim9script, then the function that
>>>> blink
>>>>the searched work is working.
>>>>
>>>>
>>>>
>>>> https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/view?usp=sharing
>>>>
>>>> Le mercredi 3 août 2022 à 12:05:05 UTC+2, N V a écrit :
>>>>
>>>>> Import is now successfull, what is now wrong is overloading mapping as
>>>>> intended by D.Conway
>>>>> https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
>>>>> as this :
>>>>>
>>>>> # Imported Functions {{{
>>>>> import autoload 'nvhelper.vim' as that
>>>>> # nnoremap that.HLNext(80) # CALL
>>>>> SUCCESS
>>>>> *nnoremap n n:* that.HLNext(80) # FAILS
>>>>> GOTO NEXT
>>>>> nnoremap N N: that.HLNext(80)
>>>>>
>>>>>
>>>>>
>>>>> It seems to goto one time to item searched but don't do next jump.
>>>>> Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>>>>>
>>>>>>
>>>>>> > Would import vim9 script as that. It seems to work when I directly
>>>>>> call
>>>>>> > that.foobar.
>>>>>> >
>>>>>> > But how to map the same call in a nnoremapping ?
>>>>>> > Thank you
>>>>>> > NV
>>>>>> >
>>>>>> >
>>>>>> > # Imported Functions {{{
>>>>>> > import './vimfiles/autoload/nvhelper.vim' as that
>>>>>> > nnoremap n n:call that.HLNext(80)
>>>>>> > nnoremap N N:call that.HLNext(80)
>>>>>>
>>>>>> Use ":help import-legacy" and then go up a few lines.
>>>>>>
>>>>>> --
>>>>>> The term "free software" is defined by Richard M. Stallman as
>>>>>> being software that isn't necessarily for free. Confusing?
>>>>>> Let's call it "Stallman software" then!
>>>>>> -- Bram Moolenaar
>>>>>>
>>>>>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net
>>>>>> \\\
>>>>>> /// \\\
>>>>>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
>>>>>> ///
>>>>>> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>>>>>>
>>>>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/7161a65a-da6f-4209-b38b-c3a8f49a1f8cn%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
Thank you Maxim, this is what i've done yesterday.
But it does not solve two problems :
1. first when I open $MYVIMRC and search for a word as 'import' it does
not call imported that.HLNExt func, I HAVE TO SOURCE $MYVIMRC ANOTEHR TIME
2. then, when I search forward for import it blinks the word occurence
searched where cursor is on, then searching backwards with N it seems to
work until I attempt to search forward one more time and the blinking
feature does not appear anymore.
You can see it :
https://drive.google.com/file/d/1q0hn3h4u05jpClaiAC_kn8DMnYrRymE9/view?usp=sharing
Le jeudi 4 août 2022 à 06:52:50 UTC+2, Maxim Kim a écrit :
> *> nnoremap n n*that.HLNext(80)
>
> remove to see messages, also `:` is not needed.
>
> Also in the gif you are importing with the full path, not sure if it
> matters.
>
> среда, 3 августа 2022 г. в 20:31:47 UTC+7, niva...@gmail.com:
>
>> Thank you Bram,
>>
>>- I added as described.
>>- Can you just look at this gif that shows that I have to source
>>$MYVIMRC to take account an import vim9script, then the function that
>> blink
>>the searched work is working.
>>
>>
>>
>> https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/view?usp=sharing
>>
>> Le mercredi 3 août 2022 à 12:05:05 UTC+2, N V a écrit :
>>
>>> Import is now successfull, what is now wrong is overloading mapping as
>>> intended by D.Conway https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
>>> as this :
>>>
>>> # Imported Functions {{{
>>> import autoload 'nvhelper.vim' as that
>>> # nnoremap that.HLNext(80) # CALL SUCCESS
>>> *nnoremap n n:* that.HLNext(80) # FAILS
>>> GOTO NEXT
>>> nnoremap N N: that.HLNext(80)
>>>
>>>
>>>
>>> It seems to goto one time to item searched but don't do next jump.
>>> Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>>>
>>>>
>>>> > Would import vim9 script as that. It seems to work when I directly
>>>> call
>>>> > that.foobar.
>>>> >
>>>> > But how to map the same call in a nnoremapping ?
>>>> > Thank you
>>>> > NV
>>>> >
>>>> >
>>>> > # Imported Functions {{{
>>>> > import './vimfiles/autoload/nvhelper.vim' as that
>>>> > nnoremap n n:call that.HLNext(80)
>>>> > nnoremap N N:call that.HLNext(80)
>>>>
>>>> Use ":help import-legacy" and then go up a few lines.
>>>>
>>>> --
>>>> The term "free software" is defined by Richard M. Stallman as
>>>> being software that isn't necessarily for free. Confusing?
>>>> Let's call it "Stallman software" then!
>>>> -- Bram Moolenaar
>>>>
>>>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net
>>>> \\\
>>>> /// \\\
>>>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
>>>> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>>>>
>>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/2a722b43-5888-4482-9669-2fc612b6feban%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
Thank you Bram,
- I added as described.
- Can you just look at this gif that shows that I have to source
$MYVIMRC to take account an import vim9script, then the function that blink
the searched work is working.
https://drive.google.com/file/d/1l4l_7M14eHjEG_cgwCpkm6NFX_QIWYCj/view?usp=sharing
Le mercredi 3 août 2022 à 12:05:05 UTC+2, N V a écrit :
> Import is now successfull, what is now wrong is overloading mapping as
> intended by D.Conway https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
> as this :
>
> # Imported Functions {{{
> import autoload 'nvhelper.vim' as that
> # nnoremap that.HLNext(80) # CALL SUCCESS
> *nnoremap n n:* that.HLNext(80) # FAILS
> GOTO NEXT
> nnoremap N N: that.HLNext(80)
>
>
>
> It seems to goto one time to item searched but don't do next jump.
> Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>
>>
>> > Would import vim9 script as that. It seems to work when I directly call
>> > that.foobar.
>> >
>> > But how to map the same call in a nnoremapping ?
>> > Thank you
>> > NV
>> >
>> >
>> > # Imported Functions {{{
>> > import './vimfiles/autoload/nvhelper.vim' as that
>> > nnoremap n n:call that.HLNext(80)
>> > nnoremap N N:call that.HLNext(80)
>>
>> Use ":help import-legacy" and then go up a few lines.
>>
>> --
>> The term "free software" is defined by Richard M. Stallman as
>> being software that isn't necessarily for free. Confusing?
>> Let's call it "Stallman software" then!
>> -- Bram Moolenaar
>>
>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net
>> \\\
>> /// \\\
>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
>> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>>
>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/08c8000c-994f-47f5-8d42-a4f3b7a12ba4n%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
Import is now successfull, what is now wrong is overloading mapping as
intended by D.Conway https://www.youtube.com/watch?v=aHm36-na4-4#t6m36s
as this :
# Imported Functions {{{
import autoload 'nvhelper.vim' as that
# nnoremap that.HLNext(80) # CALL SUCCESS
*nnoremap n n:* that.HLNext(80) # FAILS GOTO
NEXT
nnoremap N N: that.HLNext(80)
It seems to goto one time to item searched but don't do next jump.
Le mercredi 3 août 2022 à 11:51:49 UTC+2, Bram Moolenaar a écrit :
>
> > Would import vim9 script as that. It seems to work when I directly call
> > that.foobar.
> >
> > But how to map the same call in a nnoremapping ?
> > Thank you
> > NV
> >
> >
> > # Imported Functions {{{
> > import './vimfiles/autoload/nvhelper.vim' as that
> > nnoremap n n:call that.HLNext(80)
> > nnoremap N N:call that.HLNext(80)
>
> Use ":help import-legacy" and then go up a few lines.
>
> --
> The term "free software" is defined by Richard M. Stallman as
> being software that isn't necessarily for free. Confusing?
> Let's call it "Stallman software" then!
> -- Bram Moolenaar
>
> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\
> /// \\\
> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/b94575fe-7ddf-43d6-9bcc-b7e073c8ecf5n%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
import autoload 'nvhelper.vim' as that
# nnoremap that.HLNext(80) # SUCCESS
nnoremap n n: that.HLNext(80) # FAILS
nnoremap N n: that.HLNext(80)
Le mercredi 3 août 2022 à 10:57:25 UTC+2, N V a écrit :
> # Imported Functions {{{
> import autoload 'nvhelper.vim' as that SUCEED
> call that.HLNext(80)
> SUCEED
> map foo :call that.HLNext(80) FAILS
> var FooFunc = that.HLNext
> map foo :call FooFunc(80) FAILS
>
> Le mercredi 3 août 2022 à 10:44:51 UTC+2, N V a écrit :
>
>> Hi,
>>
>> Would import vim9 script as that. It seems to work when I directly call
>> that.foobar.
>>
>> But how to map the same call in a nnoremapping ?
>> Thank you
>> NV
>>
>>
>> # Imported Functions {{{
>> import './vimfiles/autoload/nvhelper.vim' as that
>> nnoremap n n:call that.HLNext(80)
>> nnoremap N N:call that.HLNext(80)
>>
>>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/30fc4361-6e4f-4d6d-a78a-3c491213570bn%40googlegroups.com.
Re: Import vim9 script as that and map that.func fails
# Imported Functions {{{
import autoload 'nvhelper.vim' as that SUCEED
call that.HLNext(80)
SUCEED
map foo :call that.HLNext(80) FAILS
var FooFunc = that.HLNext
map foo :call FooFunc(80) FAILS
Le mercredi 3 août 2022 à 10:44:51 UTC+2, N V a écrit :
> Hi,
>
> Would import vim9 script as that. It seems to work when I directly call
> that.foobar.
>
> But how to map the same call in a nnoremapping ?
> Thank you
> NV
>
>
> # Imported Functions {{{
> import './vimfiles/autoload/nvhelper.vim' as that
> nnoremap n n:call that.HLNext(80)
> nnoremap N N:call that.HLNext(80)
>
>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/d78c563d-5af8-4eb0-b2de-b92da5506470n%40googlegroups.com.
Import vim9 script as that and map that.func fails
Hi,
Would import vim9 script as that. It seems to work when I directly call
that.foobar.
But how to map the same call in a nnoremapping ?
Thank you
NV
# Imported Functions {{{
import './vimfiles/autoload/nvhelper.vim' as that
nnoremap n n:call that.HLNext(80)
nnoremap N N:call that.HLNext(80)
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/d5cadea4-2989-4e8c-b90a-5f742074a992n%40googlegroups.com.
Re: Jump tag definition does not work with CTRL-] but works with CTRL-leftmouseclick
myiskeyword=!-~,^*,^|,^",192-255 it seems that affects mapping considering this https://stackoverflow.com/questions/34018825/jump-to-tag-ctrl-stopped-working. Any idea ? Thank you Le lundi 1 août 2022 à 21:52:36 UTC+2, N V a écrit : > Hi, > > As mentionned in this pull request, > https://github.com/vim/vim/issues/7749 > > Jump tag definition does not work with CTRL-] but works with > CTRL-leftmouseclick. > On azerty keyboard ver of gvim x64 9.0.0132 on windows 10. > > Thank you for help > Nicolas > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/6959af53-7adb-421d-8c50-32cba5417f57n%40googlegroups.com.
Jump tag definition does not work with CTRL-] but works with CTRL-leftmouseclick
Hi, As mentionned in this pull request, https://github.com/vim/vim/issues/7749 Jump tag definition does not work with CTRL-] but works with CTRL-leftmouseclick. On azerty keyboard ver of gvim x64 9.0.0132 on windows 10. Thank you for help Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/0af08755-7c8e-46db-9c83-8484acc5af6an%40googlegroups.com.
Re: vim9 _vimrc compatibility with vim8 plugin
Yes, taking into account these behaviors by default, it does not prevent that I note as an interference when I affect in my _vim9rc a global variable put in interface of the script legacy gutentags. This global variable, actually a list of strings, in the legacy script is retrieved by a get(g:, nomVar) in a variable with the same name. Then it is tested at line 44 of gutentags plugin that missunderstood the type. It seems that this worked in legacy script but as soon as it is assigned in a vim9 script like my _vim9rc it alters the initial operation. While it shouldn't in the sense that a global remains a global whether swapped between a vim9 or a vim8 script legacy Le vendredi 22 juillet 2022 à 21:54:57 UTC+2, Bram Moolenaar a écrit : > > > It's like when setting a global variable from _vim9rc, it *affects > > vim8 *script same global variable. > > In Vim9 script variables are script-local by default, prefixing g: is > required to access global variables. > > In legacy script variables are global by default, prefixing s: is > required to access script-local variables. > > > -- > hundred-and-one symptoms of being an internet addict: > 94. Now admit it... How many of you have made "modem noises" into > the phone just to see if it was possible? :-) > > /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\ > /// \\\ > \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/c55bd9aa-7157-4734-bede-405b50c90349n%40googlegroups.com.
Re: vim9 _vimrc compatibility with vim8 plugin
It's like when setting a global variable from _vim9rc, it *affects vim8 *script same global variable. Le vendredi 22 juillet 2022 à 10:54:33 UTC+2, N V a écrit : > Hi, > > Encoutering this error as i attempt to use gutentag *vim8 *plugin and > have $MYVIMRC in *vim9script*. > > > > > > *Error detected while processing > foo:\barfoo\Vim\vimfiles\plugged\vim-gutentags\plugin\gutentags.vim:line > 44:E745: Using a List as a NumberE16: Invalid range" foo:\barfoo > \Vim\vimfiles\plugged\vim-gutentags\plugin\gutentags.vim" 120L, 4588B* > *--* > > *In _vimrc I set a global var *gutentags_add_default_project_roots in > _vimrc vim9script that seems to have side effect to > *vimfiles\plugged\vim-gutentags\plugin\gutentags.vim > line 44.* > > > any idea ?thanks NV > > ** > > > *[image: Capture.PNG]* > > *[image: Capture1.PNG]* > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/c40e7531-3652-45f5-b695-6d5674d9843fn%40googlegroups.com.
Re: How to set mapleader in vim9 script
Thanks a lot.
Le ven. 22 juil. 2022 à 13:05, Bram Moolenaar a écrit :
>
> > Encountering error when I set either *let mapleader =','* or *mapleader
> =
> > ','* inside a vim9 script, how in vim9 script we can set mapleader ?
> >
> > Help seems not to detail changes against vim9 script evol.
>
> g:mapleader = ','
>
> I'll update the help to also mention the Vim9 syntax.
>
> --
> From "know your smileys":
> C=}>;*{)) Drunk, devilish chef with a toupee in an updraft,
>a mustache, and a double chin
>
> /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net
> \\\
> ///
> \\\
> \\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> ///
> \\\help me help AIDS victims -- http://ICCF-Holland.org
> ///
>
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/CAOKxv4H2UH%2BhiYdtsDqE8g9LgwfBUatAj0f3kOwyWvYTwSOOGA%40mail.gmail.com.
How to set mapleader in vim9 script
Hi, Encountering error when I set either *let mapleader =','* or *mapleader = ','* inside a vim9 script, how in vim9 script we can set mapleader ? Help seems not to detail changes against vim9 script evol. [image: Capture.PNG] 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 more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/a4c2eba7-6fb6-4574-bdd8-b400ef21e610n%40googlegroups.com.
How to map f+ combination to def function ?
Hi,
I just want to map f+ or f- to increase or decrease guifont size,
what's the best way to do this ?
def AugmentGuifontSize(): void
var size = >split(':')[1]->strpart(1,3)
echomsg size
enddef
impossible ?? nnoremap f+ :call AugmentGuifontSize()
--
--
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 this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_use/463fcdff-af8a-408e-8d8d-2cec2185628an%40googlegroups.com.
Re: on docx extension opened; getting zip#Browse error message on unzip try
ok so, using 7z standalone .dll is it possible to specify 7z.dll in state of executable ? Le lundi 4 juillet 2022 à 10:03:08 UTC+2, Eike Rathke a écrit : > Hi N, > > On Sunday, 2022-07-03 23:09:46 -0700, N V wrote: > > > It's surprising to get this kind of error message of embedded zipplugin > > while it tried to unzip docx Microsoft Word Document. > > [...] > > but think it could be better if not automatically zipPlugin tried to > unzip > > inappropriate files. > > .docx documents *are* zip containers. > > Eike > > -- > OpenPGP/GnuPG encrypted mail preferred in all private communication. > GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 > 2D3A > Use LibreOffice! https://www.libreoffice.org/ > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/38a3b063-6cc0-49f4-988d-b811dd35af73n%40googlegroups.com.
on docx extension opened; getting zip#Browse error message on unzip try
Hi, It's surprising to get this kind of error message of embedded zipplugin while it tried to unzip docx Microsoft Word Document. "H:\foobar.docx" [RO][noeol][converted][unix] 113L, 41429B ***error*** (zip#Browse) unzip not available on your system I put this *workaround* : g:loaded_zipPlugin = true but think it could be better if not automatically zipPlugin tried to unzip inappropriate files. Thank you Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/f9853bce-aa6e-42ff-8017-fa53872b0e5bn%40googlegroups.com.
Re: Update Runtime/doc/channel.txt -- why LSP section disappeae
Sorry certainly i got 'Eyes Wide Shut'. Le dimanche 26 juin 2022 à 17:54:14 UTC+2, Bram Moolenaar a écrit : > > > Don't understand why an entire section which told about LSP has > disappeared > > in runtime/doc/channel.txt line 1557 after this > > update > https://github.com/vim/vim/commit/8a3b805c6c9cae341d560df9c3567ebbe42a7404 > > ? > > As the PR mentions, this section was a duplicate. The same text is > found near the end of the file. > > -- > The goal of science is to build better mousetraps. > The goal of nature is to build better mice. > > /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net \\\ > /// \\\ > \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/bfde758d-853b-4961-b384-e148f722a201n%40googlegroups.com.
Update Runtime/doc/channel.txt -- why LSP section disappeared
Don't understand why an entire section which told about LSP has disappeared in runtime/doc/channel.txt line 1557 after this update https://github.com/vim/vim/commit/8a3b805c6c9cae341d560df9c3567ebbe42a7404 ? Thank for your explanation Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/d154a586-9cd1-4046-9c3f-0f97d95409d4n%40googlegroups.com.
Update Runtime/doc/channel.txt -- why LSP section disappeae
Hi Bram, Don't understand why an entire section which told about LSP has disappeared in runtime/doc/channel.txt line 1557 after this update https://github.com/vim/vim/commit/8a3b805c6c9cae341d560df9c3567ebbe42a7404 ? Thank for your explanation Nicolas -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/9625a1c6-35a7-49aa-a1f2-06b81f01f34an%40googlegroups.com.
Ctrl+F or B broken since 8.2 patch 5157 in gui windows
Hi See title. Thanks 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 more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/5dd73ecf-f034-4146-aac5-1c76a8329c18n%40googlegroups.com.
Re: default colorscheme highlights in red the : char in signature g:Func defined vim9script
Thanks à lot for our eyes Bram, it is fixed since 6ba83ba9ee292f68aa0b218b3eef42db31c0b632 I wish you à Good Day NV Le dimanche 12 juin 2022 à 09:18:25 UTC+2, N V a écrit : > 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. >> >> 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 g:Func defined >>> > vim9script function. >>> > >>> > Just updated the vimrc_example.vim in vim9script, it displays the red >>> : >>> > char. >>> > >>> > It's disturbing for eyes. ߘŠ >>> >>> I noticed it too, and it looks like it's highlighting an error, even >>> though it is just fine. It probably happens because there is no "call" >>> before the function name. >>> >>> I can fix it by dropping "vimCommand" from the contains list of the "syn >>> match vimFunc" line in the vim.vim syntax file. But it probably has >>> side effects. >>> >>> -- >>> Q: Why does /dev/null accept only integers? >>> A: You can't sink a float. >>> >>> /// Bram Moolenaar -- br...@moolenaar.net -- http://www.Moolenaar.net >>> \\\ >>> /// \\\ >>> \\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ /// >>> \\\ help me help AIDS victims -- http://ICCF-Holland.org /// >>> >> -- -- 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 this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/0f60abaf-e8f5-4389-9acc-1906dcf7e97cn%40googlegroups.com.
