linrongbin16

looks like current engine cannot support such use case. ~ _ ~! For now the `cd` and `upper` keys are **Interactions**, and engine is running follow below steps when you...

yes, I would re-write them from fzf.vim, one by one.

> @linrongbin16 , do you want any input on the above? I'd be happy to help. sure, I am now trying to implement the nvim builtin buffer previewer, it's super...

emmmm, the code base is completely different, I don't think I could use it.

hi @savchenko , I submit #627 to add 'FzfxMarks' command, it implements the `marks` command. Would you please try it and give some feedbacks?

Sorry for letting you wait for so long time. Yes I am putting most of my time in rsvim now. But I may still spend some time to implement these...

I just added the ":History:" (in fzf.vim) equivalent command "FzfxCommandHistory". Please give me any feedbacks about it.

And I will move this issue to #749 , there lists all the missing commands in fzf.vim and fzf-lua. Hope we could fill the big gap with them.

hi @jam1015 , This is more about the product design. When I first create this plugin, I followed the design of [fzf.vim](https://github.com/junegunn/fzf.vim), which also contains multiple commands. The Pros: -...

There are two designs we could do. ## Current Status FzfxFiles variants group: - `FzfxFiles args` (Note: `args` can be ommitted) - `FzfxFiles unres_args` - `FzfxFiles visual` - `FzfxFiles unres_visual`...