fzf_command_prefix not working

[linrongbin16]

using lazy to manage fzf and fzf.vim.

The init.vim:

" some settings about nvim itself.
set number
...

" setup lazy
lua<<EOF
local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "https://github.com/folke/lazy.nvim.git",
    "--branch=stable", -- latest stable release
    lazypath,
  })
end
vim.opt.rtp:prepend(lazypath)

local plugins={
  { 'junegunn/fzf', build = ":call fzf#install()"},
  { 'junegunn/fzf.vim'},
}
require("lazy").setup(plugins)
EOF


let g:fzf_command_prefix = "Fzf"

before migrate to lazy, the fzf commands are FzfFiles, FzfRg, etc.

But now the fzf commands are just Files, Rg.

I am not sure, looks like fzf is already loaded before it detect the fzf_command_prefix variable?

[folke]

You need to set those settings before loading lazy. So either in init() function part of the spec, or before calling lazy setup

[linrongbin16]

Thanks for your comment about init.

I am moving from vim and vim-plug, to neovim and lazy.

In vim-plug, I usually structrue my.vimrc file in this way:

plugin begin

Plug fzf
Plug fzf.vim
Plug lualine
Plug bufferline
...

plugin end

" each plugin config is in the
" related vim file under config directory.
" and load from.vimrc
source ~/.vim/config/fzf.vim
source ~/.vim/config/lualine.vim
source ~/.vim/config/bufferline.vim

But in lazy, we should load config until we load the plugin.
Looks like the main difference between lazy.nvim and vim-plug is: when to load the related plugin's configs.

Can I say, for old-style vim configs, I should use init. For lua configs, I should use config. Correct?

[folke]

Yes! That's pretty much spot on. Vimscript plugins expect the global options to have been set before loading, while setting options for Lua plugins is part of the setup.

[linrongbin16]

thanks very much!