Closed Penaz91 closed 1 year ago
@Penaz91 @stevearc https://github.com/stevearc/dressing.nvim/pull/65 related
This is a bug in fzf-lua. Fixed here: https://github.com/ibhagwan/fzf-lua/pull/522
This is a bug in fzf-lua. Fixed here: ibhagwan/fzf-lua#522
Merged @stevearc’s PR, apologize for the mess.
@ibhagwan no worries! Bugs happen :)
@ibhagwan no worries! Bugs happen :)
I didn’t know anyone used fzf_wrap
like this (directly by ref from require'fzf-lua'
), I guess this was written before the introduction of the fzf_exec
API which would be the better (and clearer way) to write this.
Let me know if you wish, I can submit a PR to convert the current fzf_wrap
code to fzf_exec
.
Would love a PR to convert it to the best-practice API!
https://github.com/stevearc/dressing.nvim/pull/67
Also took the liberty to improve upon the item number extraction using a lua regex :-)
Updated both fzf-lua and dressing to the latest commit, everything seems to be working perfectly.
It's great seeing such tight cooperation between different repository owners.
Thank you for everything, feel free to close!
Describe the bug The first time I use vim.ui.select after starting Nvim, I get an error similar to the following:
This was triggered by using the
:lua vim.ui.select({1,2,3}, {}, function(opt)end)
command. Running the command again will work correctlySystem information
vim.ui.select
backend? If so, which one? Fzf_luaTo Reproduce Steps to reproduce the behavior:
:lua vim.ui.select({1,2,3}, {}, function(opt)end)
Additional context I'm using the following lua plugin related to FZF: