Feature: Add support for function-based completion in 'complete' option #17065

girishji · 2025-04-06T08:25:19Z

This change adds two new values to the 'complete' ('cpt') option:

f – invokes the function specified by the 'completefunc' option
f{func} – invokes a specific function {func} (can be a string or Funcref)

These new flags extend keyword completion behavior (e.g., via <C-N> / <C-P>) by allowing function-based sources to participate in standard keyword completion.

Key behaviors:

Multiple f{func} values can be specified, and all will be called in order.
Functions should follow the interface defined in :help complete-functions.
When using f{func}, escaping is required for spaces (with \) and commas (with \\) in Funcref names.
If a function sets 'refresh' to 'always', it will be re-invoked on every change to the input text. Otherwise, Vim will attempt to reuse and filter existing matches as the input changes, which matches the default behavior of other completion sources.
Matches are inserted at the keyword boundary for consistency with other completion methods.
If finding matches is time-consuming, complete_check() can be used to maintain responsiveness.
Completion matches are gathered in the sequence defined by the 'cpt' option, preserving source priority.

This feature increases flexibility of standard completion mechanism and may reduce the need for external completion plugins for many users.

Examples:

Complete matches from LSP client. Notice the use of refresh: always and function().

set cpt+=ffunction("g:LspCompletor"\\,\ [5]). # maxitems = 5

def! g:LspCompletor(maxitems: number, findstart: number, base: string): any
    if findstart == 1
        return g:LspOmniFunc(findstart, base)
    endif
    return {words: g:LspOmniFunc(findstart, base)->slice(0, maxitems), refresh: 'always'}
enddef
autocmd VimEnter * g:LspOptionsSet({ autoComplete: false, omniComplete: true })

Complete matches from :iabbrev.

set cpt+=fAbbrevCompletor

def! g:AbbrevCompletor(findstart: number, base: string): any
    if findstart > 0
        var prefix = getline('.')->strpart(0, col('.') - 1)->matchstr('\S\+$')
        if prefix->empty()
            return -2
        endif
        return col('.') - prefix->len() - 1
    endif
    var lines = execute('ia', 'silent!')
    if lines =~? gettext('No abbreviation found')
        return v:none  # Suppresses warning message
    endif
    var items = []
    for line in lines->split("\n")
        var m = line->matchlist('\v^i\s+\zs(\S+)\s+(.*)$')
        if m->len() > 2 && m[1]->stridx(base) == 0
            items->add({ word: m[1], info: m[2], dup: 1 })
        endif
    endfor
    return items->empty() ? v:none :
        items->sort((v1, v2) => v1.word < v2.word ? -1 : v1.word ==# v2.word ? 0 : 1)
enddef

Auto-completion:

Vim's standard completion frequently checks for user input while searching for new matches. It is responsive irrespective of file size. This makes it well-suited for smooth auto-completion. You can try with above examples:

set cot=menuone,popup,noselect inf

autocmd TextChangedI * InsComplete()

def InsComplete()
    if getcharstr(1) == '' && getline('.')->strpart(0, col('.') - 1) =~ '\k$'
        SkipTextChangedIEvent()
        feedkeys("\<c-n>", "n")
    endif
enddef

inoremap <silent> <c-e> <c-r>=<SID>SkipTextChangedIEvent()<cr><c-e>

def SkipTextChangedIEvent(): string
    set eventignore+=TextChangedI  # Suppress next event caused by <c-e> (or <c-n> when no matches found)
    timer_start(1, (_) => {
        set eventignore-=TextChangedI
    })
    return ''
enddef

# Optional
inoremap <silent><expr> <tab> pumvisible() ? "\<c-n>" : "\<tab>"
inoremap <silent><expr> <s-tab> pumvisible() ? "\<c-p>" : "\<s-tab>"

This change adds two new values to the `'complete'` (`'cpt'`) option: - `f` – invokes the function specified by the `'completefunc'` option - `f{func}` – invokes a specific function `{func}` (can be a string or `Funcref`) These new flags extend keyword completion behavior (e.g., via `<C-N>` / `<C-P>`) by allowing function-based sources to participate in standard keyword completion. Key behaviors: - Multiple `f{func}` values can be specified, and all will be called in order. - Functions should follow the interface defined in `:help complete-functions`. - When using `f{func}`, escaping is required for spaces (with `\`) and commas (with `\\`) in `Funcref` names. - If a function sets `'refresh'` to `'always'`, it will be re-invoked on every change to the input text. Otherwise, Vim will attempt to reuse and filter existing matches as the input changes, which matches the default behavior of other completion sources. - Matches are inserted at the keyword boundary for consistency with other completion methods. - If finding matches is time-consuming, `complete_check()` can be used to maintain responsiveness. - Completion matches are gathered in the sequence defined by the `'cpt'` option, preserving source priority. This feature increases flexibility of standard completion mechanism and may reduce the need for external completion plugins for many users. M runtime/doc/insert.txt M runtime/doc/options.txt M src/insexpand.c M src/optionstr.c M src/testdir/test_ins_complete.vim M src/testdir/test_options.vim

M src/insexpand.c

chrisbra · 2025-04-07T18:19:15Z

Thanks, that sounds like a very interesting enhancement. @glepnir what's your thought about this?

M src/insexpand.c

M runtime/doc/options.txt M src/insexpand.c

M src/insexpand.c

glepnir · 2025-04-08T05:57:26Z

related.#9005 , adding omnifunc to cpt may be better ? extra flags may add burden. Use the existing omniufunc to extend keyword completion. And neovim can also benefit from it.

Also this is in our todo

-   Add a flag to 'complete' to be able to do omni completion with CTRL-N (and
    mix it with other kinds of completion).

girishji · 2025-04-08T06:41:08Z

What is this MacOS failure about: https://github.com/vim/vim/actions/runs/14326056546/job/40151616766?pr=17065 ?

glepnir · 2025-04-08T07:16:37Z

random failed i have rerun job

chrisbra · 2025-04-09T17:36:41Z

I think it is fine to use this for the 'complete' option. But how does this handle the return values? From :h complete-functions

 Negative return values:
     -2   To cancel silently and stay in completion mode.
     -3   To cancel silently and leave completion mode.
     Another negative value: completion starts at the cursor column

If there are several f{func} defined, I would expect that at least for the -3 case no other completion function is called?

girishji · 2025-04-09T21:10:44Z

I think it is fine to use this for the 'complete' option. But how does this handle the return values? From :h complete-functions
 Negative return values:
     -2   To cancel silently and stay in completion mode.
     -3   To cancel silently and leave completion mode.
     Another negative value: completion starts at the cursor column
If there are several f{func} defined, I would expect that at least for the -3 case no other completion function is called?

Great question. The behavior follows the documentation: a return value of -2 from the function will cause it to be invoked again during the same session (when the leader changes). A return value of -3 will cause the function to be ignored for the remainder of the session. A negative return value from one function will not affect the behavior of other completion sources. Please review the test Test_cpt_func_refresh_always_fail() in the file test_ins_complete.vim for further clarification.

In the minimal case—when the 'complete' (cpt) option contains only a single function and no other sources—the behavior aligns with what is described in the documentation.

M runtime/doc/options.txt

…nction M runtime/doc/options.txt M src/insexpand.c M src/optionstr.c M src/testdir/test_ins_complete.vim M src/testdir/test_options.vim

runtime/doc/options.txt

src/optionstr.c

Co-authored-by: Christian Brabandt <cb@256bit.org>

M src/optionstr.c

Copilot

Copilot reviewed 3 out of 6 changed files in this pull request and generated 1 comment.

Files not reviewed (3)

runtime/doc/insert.txt: Language not supported
runtime/doc/options.txt: Language not supported
src/testdir/test_options.vim: Language not supported

Comments suppressed due to low confidence (1)

src/optionstr.c:1589

[nitpick] The token validation distinguishes between tokens that may have additional characters (e.g. 'f') and those that cannot (e.g. 'o'), but this behavior is not self-documenting. Consider adding a comment to clarify the intent behind the use of different allowed token sets.

if (vim_strchr((char_u *)".wbuksid]tUfo", *buffer) == NULL)

src/optionstr.c

src/insexpand.c

Co-authored-by: Christian Brabandt <cb@256bit.org>

Removed static variable, and code associated with it. Easier to read now. However, function name is not visible inside callback during debugging. M src/insexpand.c

runtime/doc/options.txt

Co-authored-by: zeertzjq <zeertzjq@outlook.com>

src/insexpand.c

src/optionstr.c

To increase coverage M src/testdir/test_ins_complete.vim M src/testdir/test_options.vim

Co-authored-by: glepnir <glephunter@gmail.com>

chrisbra · 2025-04-14T19:54:49Z

thanks

girishji · 2025-04-15T04:27:03Z

thank you!

chrisbra · 2025-04-15T05:45:15Z

Coverity complains:

   static void
6425cpt_compl_refresh(void)
6426{
6427#ifdef FEAT_COMPL_FUNC
6428    char_u      *cpt;
6429    char_u      *p;
       1. var_decl: Declaring variable cb without initializer.
6430    callback_T  *cb;
6431
6432    // Make the completion list linear (non-cyclic)
6433    ins_compl_make_linear();
6434    // Make a copy of 'cpt' in case the buffer gets wiped out
6435    cpt = vim_strsave(curbuf->b_p_cpt);
6436
6437    cpt_value_idx = 0;
       2. Condition *p, taking true branch.
6438    for (p = cpt; *p; cpt_value_idx++)
6439    {
       3. Condition *p == 44, taking true branch.
       5. Condition *p == 44, taking true branch.
       7. Condition *p == 44, taking false branch.
       8. Condition *p == 32, taking true branch.
       10. Condition *p == 44, taking false branch.
       11. Condition *p == 32, taking false branch.
6440        while (*p == ',' || *p == ' ') // Skip delimiters
       4. Jumping back to the beginning of the loop.
       6. Jumping back to the beginning of the loop.
       9. Jumping back to the beginning of the loop.
6441            p++;
6442
       12. Condition cpt_func_refresh_always[cpt_value_idx], taking true branch.
6443        if (cpt_func_refresh_always[cpt_value_idx])
6444        {
       13. Condition *p == 111, taking false branch.
6445            if (*p == 'o')
6446                cb = &curbuf->b_ofu_cb;
       14. Condition *p == 102, taking false branch.
6447            else if (*p == 'f')
6448                cb = (*(p + 1) != ',' && *(p + 1) != NUL)
6449                    ? get_cpt_func_callback(p + 1) : &curbuf->b_cfu_cb;
      
CID 1646489: (#1 of 1): Uninitialized pointer read (UNINIT)
15. uninit_use: Using uninitialized value cb.
6450            if (cb)
6451            {
6452                compl_curr_match = remove_old_matches();
6453                get_cpt_func_completion_matches(cb);
6454            }
6455        }
6456

I suppose we can just initialize cb = NULL?

girishji · 2025-04-15T08:18:22Z

Yes, that should fix it.

chrisbra · 2025-04-15T16:13:42Z

fixed in d2079cf

…h 'complete' Problem: completion: cannot configure completion functions with 'complete' Solution: add support for setting completion functions using the f and o flag for 'complete' (Girish Palya) This change adds two new values to the `'complete'` (`'cpt'`) option: - `f` – invokes the function specified by the `'completefunc'` option - `f{func}` – invokes a specific function `{func}` (can be a string or `Funcref`) These new flags extend keyword completion behavior (e.g., via `<C-N>` / `<C-P>`) by allowing function-based sources to participate in standard keyword completion. **Key behaviors:** - Multiple `f{func}` values can be specified, and all will be called in order. - Functions should follow the interface defined in `:help complete-functions`. - When using `f{func}`, escaping is required for spaces (with `\`) and commas (with `\\`) in `Funcref` names. - If a function sets `'refresh'` to `'always'`, it will be re-invoked on every change to the input text. Otherwise, Vim will attempt to reuse and filter existing matches as the input changes, which matches the default behavior of other completion sources. - Matches are inserted at the keyword boundary for consistency with other completion methods. - If finding matches is time-consuming, `complete_check()` can be used to maintain responsiveness. - Completion matches are gathered in the sequence defined by the `'cpt'` option, preserving source priority. This feature increases flexibility of standard completion mechanism and may reduce the need for external completion plugins for many users. **Examples:** Complete matches from [LSP](https://github.com/yegappan/lsp) client. Notice the use of `refresh: always` and `function()`. ```vim set cpt+=ffunction("g:LspCompletor"\\,\ [5]). # maxitems = 5 def! g:LspCompletor(maxitems: number, findstart: number, base: string): any if findstart == 1 return g:LspOmniFunc(findstart, base) endif return {words: g:LspOmniFunc(findstart, base)->slice(0, maxitems), refresh: 'always'} enddef autocmd VimEnter * g:LspOptionsSet({ autoComplete: false, omniComplete: true }) ``` Complete matches from `:iabbrev`. ```vim set cpt+=fAbbrevCompletor def! g:AbbrevCompletor(findstart: number, base: string): any if findstart > 0 var prefix = getline('.')->strpart(0, col('.') - 1)->matchstr('\S\+$') if prefix->empty() return -2 endif return col('.') - prefix->len() - 1 endif var lines = execute('ia', 'silent!') if lines =~? gettext('No abbreviation found') return v:none # Suppresses warning message endif var items = [] for line in lines->split("\n") var m = line->matchlist('\v^i\s+\zs(\S+)\s+(.*)$') if m->len() > 2 && m[1]->stridx(base) == 0 items->add({ word: m[1], info: m[2], dup: 1 }) endif endfor return items->empty() ? v:none : items->sort((v1, v2) => v1.word < v2.word ? -1 : v1.word ==# v2.word ? 0 : 1) enddef ``` **Auto-completion:** Vim's standard completion frequently checks for user input while searching for new matches. It is responsive irrespective of file size. This makes it well-suited for smooth auto-completion. You can try with above examples: ```vim set cot=menuone,popup,noselect inf autocmd TextChangedI * InsComplete() def InsComplete() if getcharstr(1) == '' && getline('.')->strpart(0, col('.') - 1) =~ '\k$' SkipTextChangedIEvent() feedkeys("\<c-n>", "n") endif enddef inoremap <silent> <c-e> <c-r>=<SID>SkipTextChangedIEvent()<cr><c-e> def SkipTextChangedIEvent(): string # Suppress next event caused by <c-e> (or <c-n> when no matches found) set eventignore+=TextChangedI timer_start(1, (_) => { set eventignore-=TextChangedI }) return '' enddef ``` closes: vim#17065 Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: glepnir <glephunter@gmail.com> Signed-off-by: Girish Palya <girishji@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>

This will make use of Vims brand new completion functions. This is just the bare framework without any completor. It triggers on buffer change events in insert mode. Suggestions can be navigated with <tab>. Heavily based on the examples in vim/vim#17065

… with 'complete' Problem: completion: cannot configure completion functions with 'complete' Solution: add support for setting completion functions using the f and o flag for 'complete' (Girish Palya) This change adds two new values to the `'complete'` (`'cpt'`) option: - `f` – invokes the function specified by the `'completefunc'` option - `f{func}` – invokes a specific function `{func}` (can be a string or `Funcref`) These new flags extend keyword completion behavior (e.g., via `<C-N>` / `<C-P>`) by allowing function-based sources to participate in standard keyword completion. **Key behaviors:** - Multiple `f{func}` values can be specified, and all will be called in order. - Functions should follow the interface defined in `:help complete-functions`. - When using `f{func}`, escaping is required for spaces (with `\`) and commas (with `\\`) in `Funcref` names. - If a function sets `'refresh'` to `'always'`, it will be re-invoked on every change to the input text. Otherwise, Vim will attempt to reuse and filter existing matches as the input changes, which matches the default behavior of other completion sources. - Matches are inserted at the keyword boundary for consistency with other completion methods. - If finding matches is time-consuming, `complete_check()` can be used to maintain responsiveness. - Completion matches are gathered in the sequence defined by the `'cpt'` option, preserving source priority. This feature increases flexibility of standard completion mechanism and may reduce the need for external completion plugins for many users. **Examples:** Complete matches from [LSP](https://github.com/yegappan/lsp) client. Notice the use of `refresh: always` and `function()`. ```vim set cpt+=ffunction("g:LspCompletor"\\,\ [5]). # maxitems = 5 def! g:LspCompletor(maxitems: number, findstart: number, base: string): any if findstart == 1 return g:LspOmniFunc(findstart, base) endif return {words: g:LspOmniFunc(findstart, base)->slice(0, maxitems), refresh: 'always'} enddef autocmd VimEnter * g:LspOptionsSet({ autoComplete: false, omniComplete: true }) ``` Complete matches from `:iabbrev`. ```vim set cpt+=fAbbrevCompletor def! g:AbbrevCompletor(findstart: number, base: string): any if findstart > 0 var prefix = getline('.')->strpart(0, col('.') - 1)->matchstr('\S\+$') if prefix->empty() return -2 endif return col('.') - prefix->len() - 1 endif var lines = execute('ia', 'silent!') if lines =~? gettext('No abbreviation found') return v:none # Suppresses warning message endif var items = [] for line in lines->split("\n") var m = line->matchlist('\v^i\s+\zs(\S+)\s+(.*)$') if m->len() > 2 && m[1]->stridx(base) == 0 items->add({ word: m[1], info: m[2], dup: 1 }) endif endfor return items->empty() ? v:none : items->sort((v1, v2) => v1.word < v2.word ? -1 : v1.word ==# v2.word ? 0 : 1) enddef ``` **Auto-completion:** Vim's standard completion frequently checks for user input while searching for new matches. It is responsive irrespective of file size. This makes it well-suited for smooth auto-completion. You can try with above examples: ```vim set cot=menuone,popup,noselect inf autocmd TextChangedI * InsComplete() def InsComplete() if getcharstr(1) == '' && getline('.')->strpart(0, col('.') - 1) =~ '\k$' SkipTextChangedIEvent() feedkeys("\<c-n>", "n") endif enddef inoremap <silent> <c-e> <c-r>=<SID>SkipTextChangedIEvent()<cr><c-e> def SkipTextChangedIEvent(): string # Suppress next event caused by <c-e> (or <c-n> when no matches found) set eventignore+=TextChangedI timer_start(1, (_) => { set eventignore-=TextChangedI }) return '' enddef ``` closes: vim/vim#17065 vim/vim@cbe5319 Temporarily remove bufname completion with #if 0 to make merging easier. Co-authored-by: Girish Palya <girishji@gmail.com> Co-authored-by: Christian Brabandt <cb@256bit.org> Co-authored-by: glepnir <glephunter@gmail.com>

girishji added 4 commits April 6, 2025 10:16

Fix compiler warnings

61302b8

M src/insexpand.c

Fix Windows compile errors

586e9cc

M src/insexpand.c

Fix warnings

fd610ab

M src/insexpand.c

girishji added 4 commits April 7, 2025 20:53

Remove warnings

93f4bab

M src/insexpand.c

Fix warnings

273a640

M runtime/doc/options.txt M src/insexpand.c

Remove warning

f789551

M src/insexpand.c

Fix warnings

47a3f02

M src/insexpand.c

Merge branch 'vim:master' into pr_func_compl

14ccddc

Merge branch 'vim:master' into pr_func_compl

5c2f76f

This was referenced Apr 9, 2025

Feature: Add per-source match limit support to 'complete' option girishji/vim#1

Closed

Feature: Add per-source match limit support to 'complete' option #17087

Closed

Improve doc

1ada90d

M runtime/doc/options.txt

Add support for 'o' flag in 'complete' option to invoke 'omnifunc' fu…

47c9c81

…nction M runtime/doc/options.txt M src/insexpand.c M src/optionstr.c M src/testdir/test_ins_complete.vim M src/testdir/test_options.vim

chrisbra reviewed Apr 10, 2025

View reviewed changes

runtime/doc/options.txt Outdated Show resolved Hide resolved

runtime/doc/options.txt Outdated Show resolved Hide resolved

src/optionstr.c Outdated Show resolved Hide resolved

girishji and others added 3 commits April 11, 2025 08:58

Update runtime/doc/options.txt

213f06d

Co-authored-by: Christian Brabandt <cb@256bit.org>

Update runtime/doc/options.txt

fc0e0b6

Co-authored-by: Christian Brabandt <cb@256bit.org>

Remove unused var

f6735c6

M src/optionstr.c

chrisbra requested a review from Copilot April 12, 2025 16:11

Copilot AI reviewed Apr 12, 2025

View reviewed changes

src/optionstr.c Show resolved Hide resolved

chrisbra reviewed Apr 12, 2025

View reviewed changes

src/insexpand.c Outdated Show resolved Hide resolved

src/insexpand.c Outdated Show resolved Hide resolved

girishji and others added 2 commits April 13, 2025 19:36

Update src/insexpand.c

3032c44

Co-authored-by: Christian Brabandt <cb@256bit.org>

Refactor

1a574bc

Removed static variable, and code associated with it. Easier to read now. However, function name is not visible inside callback during debugging. M src/insexpand.c

zeertzjq reviewed Apr 14, 2025

View reviewed changes

runtime/doc/options.txt Outdated Show resolved Hide resolved

Update runtime/doc/options.txt

8d9d537

Co-authored-by: zeertzjq <zeertzjq@outlook.com>

glepnir reviewed Apr 14, 2025

View reviewed changes

src/insexpand.c Outdated Show resolved Hide resolved

src/insexpand.c Outdated Show resolved Hide resolved

src/insexpand.c Outdated Show resolved Hide resolved

src/optionstr.c Outdated Show resolved Hide resolved

src/optionstr.c Outdated Show resolved Hide resolved

girishji and others added 6 commits April 14, 2025 13:42

Add/modify test

d2e5974

To increase coverage M src/testdir/test_ins_complete.vim M src/testdir/test_options.vim

Update src/insexpand.c

d669849

Co-authored-by: glepnir <glephunter@gmail.com>

Update src/insexpand.c

443ea40

Co-authored-by: glepnir <glephunter@gmail.com>

Update src/insexpand.c

7e9e4c6

Co-authored-by: glepnir <glephunter@gmail.com>

Update src/optionstr.c

caa832b

Co-authored-by: glepnir <glephunter@gmail.com>

Update src/optionstr.c

1172684

Co-authored-by: glepnir <glephunter@gmail.com>

chrisbra closed this in cbe5319 Apr 14, 2025

girishji deleted the pr_func_compl branch April 16, 2025 21:13

chrisbra mentioned this pull request May 20, 2025

remove f and ffunc from complete option #17347

Closed

girishji mentioned this pull request May 29, 2025

Improve scheduling of F{func} in Ctrl-N completion #17396

Closed

zeertzjq mentioned this pull request May 31, 2025

vim-patch: various 'complete' features neovim/neovim#34247

Merged

girishji mentioned this pull request Jul 3, 2025

feat: allow functions in 'complete' to complete from non-keyword #17651

Closed

girishji mentioned this pull request Jul 21, 2025

Feat: Add 'autocomplete' option for automatic insert mode completion #17812

Closed

girishji mentioned this pull request Oct 4, 2025

runtime: add self to :h credits #18485

Closed

Uh oh!

Feature: Add support for function-based completion in 'complete' option #17065

Feature: Add support for function-based completion in 'complete' option #17065

Uh oh!

Conversation

girishji commented Apr 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chrisbra commented Apr 7, 2025

Uh oh!

glepnir commented Apr 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

girishji commented Apr 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

glepnir commented Apr 8, 2025

Uh oh!

chrisbra commented Apr 9, 2025

Uh oh!

girishji commented Apr 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chrisbra commented Apr 14, 2025

Uh oh!

girishji commented Apr 15, 2025

Uh oh!

chrisbra commented Apr 15, 2025

Uh oh!

girishji commented Apr 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chrisbra commented Apr 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

girishji commented Apr 6, 2025 •

edited

Loading

glepnir commented Apr 8, 2025 •

edited

Loading

girishji commented Apr 8, 2025 •

edited

Loading

girishji commented Apr 9, 2025 •

edited

Loading

girishji commented Apr 15, 2025 •

edited

Loading