picker global definitions

[ranjithshegde]

Is it possible to set global definitions for pickers at the config instead of in keymap or as cargs?

For example

require('fzf-lua').setup({
  lsp = {
    definition = {   jump_to_single_result = true },
    references = { winopts = {...}}
   }

So far they seem to be ingored. Would be really nice to set some winopts as well to each picker

[ibhagwan]

So far they seem to be ingored. Would be really nice to set some winopts as well to each picker

All LSP locations are groups under lsp, take a look at defaults.lua to see all categories:

require('fzf-lua').setup({
  lsp = {
     jump_to_single_result = true,
    winopts = {...},
   }
})

[ranjithshegde]

Thank you for a quick respnse (and a great plugin!!). This works.
Would you ever be interested in allowing more granular defaults such as lsp = { references = { winopts = {...}}, document_symbol = {winopts {...}}} or is that too opinionated?

[ibhagwan]

Thank you for a quick respnse (and a great plugin!!). This works.
Would you ever be interested in allowing more granular defaults such as lsp = { references = { winopts = {...}}, document_symbol = {winopts {...}}} or is that too opinionated?

That would greatly depend on what these are, IMHO the correct place for these are in a “profile” (:FzfLua profiles), what are you thinking about specifically?

[ranjithshegde]

I am used to a very specific config I had with telescope for LSP stuff, where for anything cword dependent like code actions, referenfces, calls etc I had a cursor positioned dropdown list, and anything 'browsing' related like document symbols, workspace symbols I used the freshly minted 'ivy' profile.

While all this is possible with args, having defaults makes it so that no matter where I am calling those pickers from (maps, cmd, lua functions ...) it uses those winopts.

I get that this is a very opinionated workflow and there is probably no real benefit of having it in the repo.

[ibhagwan]

I am used to a very specific config I had with telescope for LSP stuff, where for anything cword dependent like code actions, referenfces, calls etc I had a cursor positioned dropdown list, and anything 'browsing' related like document symbols, workspace symbols I used the freshly minted 'ivy' profile.

While all this is possible with args, having defaults makes it so that no matter where I am calling those pickers from (maps, cmd, lua functions ...) it uses those winopts.

I get that this is a very opinionated workflow and there is probably no real benefit of having it in the repo.

This is indeed very opinionated and will probably raise issues from other users, personally I also use code actions relative to cursor, just set winopts under lsp.code_acrions, here’s mine:
https://github.com/ibhagwan/nvim-lua/blob/2605283ee192b928517143b7e51a2169b2da355d/lua/plugins/fzf-lua/setup.lua#L206-L217

[ranjithshegde]

Makes sense.
Btw, is there a way to apply profiles selectively, either via config defaults or as cmd args require('fzf-lua').lsp_document_symbol({'ivy'}) or is always global as documented in help?

[ibhagwan]

Makes sense. Btw, is there a way to apply profiles selectively, either via config defaults or as cmd args require('fzf-lua').lsp_document_symbol({'ivy'}) or is always global as documented in help?

Not yet but I was going to add it.

[ibhagwan]

#1729 if you wish to track.