Liu-Cheng Xu

Still unimplemented, not a priority for me. PR welcome.

Sorry for taking so long on this issue, for the simplicity, a new provider can be added for such a purpose. Could you try this branch https://github.com/liuchengxu/vim-clap/tree/input-history-provider? @arashm @svermeulen @mtuzinskiy...

The input history provider does not require the Rust binary. The idea is to record each input in this provider and use these history inputs as the source and it's...

@arashm I have pushed a new commit to fix the vim issue you just ran into, please pull the latest commit of that branch and try again. I didn't test...

https://github.com/liuchengxu/vim-clap/blob/input-history-provider/autoload/clap/provider/input_history.vim#L8 the history size is limited right now, you can change it to a larger number temporarily. I just pushed another commit to reverse the order. Basically, the history records...

>before I start typing, preferably if this could be replaced with the history of previous files I open with files would be much easier. I don't quite follow. Can you...

>Invoking grep like this, won't show anything in the history, only if I manually type in grep window, it will appear in the history. Pushed a new commit, should be...

@arashm Another commit pushed, please try again. Seems to work on my machine this time.

Well, you can centainly do that in `source()` function. Firstly, you need to store `project-name` somewhere so that the provider can use it. And you check if `project-name` exists in...

I misunderstand your initial question. See how `filer` handles the case of no matches found. https://github.com/liuchengxu/vim-clap/blob/ee02a6f841a4012cbacac6ef79ddc6c1ed862ed1/autoload/clap/provider/filer.vim#L254 https://github.com/liuchengxu/vim-clap/blob/ee02a6f841a4012cbacac6ef79ddc6c1ed862ed1/autoload/clap/provider/filer.vim#L220-L222