command -nargs=1 -complete=custom,TestComplete T echo "<args>" function! TestComplete(A, C, P) abort return a:C.a:C->split('[ =]')->join() endfunction
when typing ':T=n' will have T=nT n
command -nargs=1 -complete=custom,TestComplete T echo "<args>" function! TestComplete(A, C, P) abort return a:C->split('[ =]')->join() endfunction
won't have any completion message when typing ':T=abc'
Output T=abc in the second case.
9.1.2114
GVim
Windows 11
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I am confused, shouldn't arguments be separated by spaces?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
So do I am appalled when I found that the first demonstration can work.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Well, for me it doesn't do anything, unless I type a space, so this: :T=n<tab> does not return anything, but this does: :T=n <tab>. Also for your second example.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Sorry I forget to tell you these setting to see the triggered things in time:
set wildmode=noselect:lastused,full set wildmenu wildoptions=pum,fuzzy wildcharm=<Tab> pumheight=12 augroup CmdComplete au! autocmd CmdlineChanged : call wildtrigger() augroup END
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Oh that's because it was filtered by vim. Sorry.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()