There are a few things left to do here.
As much as this is a good document to test out my own plugin, it is also good to keep track of things in GitHub issues.
I can’t seem to get fzf native reloading to work, without flickering. It seems to only support that for string actions.
I re-implemented parts of fzf-lua’s configuration infrastructure, but perhaps this plugin’s configs can go into the same fzf-lua setup block alongside the rest of its builtin providers.
I prefer not to introduce more highlight groups because that just pollutes
the highlight group namespace + it forces users to use have to put executable
code like vim.cmd[[highlight ...]] in their config. It’s just easier to
have a field in the setup_opts that maps each entry component to the name of
the highlight the user prefers.
orgmode.nvim doesn’t seem to expose an API for this yet (but I haven’t looked very hard).
Like live grep, but using orgmode search syntax.
Not sure if this is possible. fzf-lua seems to work best with external processes.
ctrl-i and ctrl-o to step in and out of search context, for refining search context.
I’m not sure how to communicate with the contents callback from an action function.
Not sure how this will play with the whole :FzfLua subsystem though.
I’m hesitant to just introduce a new command when users can define that themselves.