buffer/filetype specific key configuration

[cova-fe]

Hi, I'm wondering if it could be possible to have a filetype specific configuration. Use case: when working on files with different filetypes in several buffers, it would be a nice feature if you can have the same key to trigger a filetype specific binding. So, for example, "l" (for "language") will open a submenu/group with golang specific commands in go buffers, and the same "l" will open a lua submenu in lua buffers. I tried to use "cond" option and also a ftplugin configuration that includes wk.add() but it seems that the configuration is read only once and then kept for all the buffers. Before digging further I'd like to know if it is like so by design or if it is possible to get this behavior in some ways.
Thanks!

[rodhash]

+1 also interested in this.

With vim.api.nvim_get_current_buf this almost work.

ie:

local wk = require("which-key")
local buf = vim.api.nvim_get_current_buf()

wk.add({
  mode = { "n" },
  {"l", "...", desc = "...", buffer = buf},

  cond = function ()
    return vim.bo.filetype == "javascript"
  end
})

I'm able to use the same keybinding in different filetypes where each FT have it's own binding.

ie: If I switch to a "py" or "cpp" buffer each will have it's own binding.

But ...

If I open two buffers of the same FT only the first buffer gets this binding .. for some reason this doesn't work if we have multiple buffers of the same FT.

[phortonssf]

What file are you writing this code in? If you haven't already try putting it in nvim/after/ftplugin/javascript.lua.

[phortonssf]

This is working for me. Shows up in whick-key menu as well using my localleader key. I couldn't get the bindings to work properly using the which-key to add the local mappings.

ftplugin/lua.lua

local bufnr = vim.api.nvim_get_current_buf()


  vim.api.nvim_buf_set_keymap(
    bufnr,
    "n",
    "<localleader>l",
    ':echo "lua filetype"<CR>',
    { desc = "lua", noremap = true, silent = true }
  )

[rodhash]

What file are you writing this code in? -> it was in my main file for whichkey.lua (usually I have a specific lua file for each config)

Yeah I didn't think about using the ftplugin dir.. that's something I usually avoid but it's a good idea.

at the end I was able to work around the 2+ buffers issue by creating an auto command to load it for every buffer, so far it seems to be working fine as well.