document how to setup RA for nvim automatically

[jyn514]

No description provided.

[dianqk]

It works for me.

[Noratrieb]

any reason to not integrate this into x setup?

[jyn514]

this can't be done automatically. this goes in the global nvim/init.lua, not in a project specific file. if people want project-specific code, they need to use a plugin, and that's already recommended on the paragraph above.

[dianqk]

I'm really curious how neovim handles the ${workspaceFolder} variable. I've searched the codebases of neovim, nvim-lspconfig, and neoconf.nvim, but haven't found anything that seems to be processing it.

[dianqk]

The code snippet is from https://github.com/mfussenegger/nvim-dap/blob/379cf26e9c457b66a0152cd5d018418c03720d47/lua/dap.lua#L375-L402.

        local var_placeholders = {
          ['${workspaceFolder}'] = function(_)
            return vim.fn.getcwd()
          end,
        }

        local function expand_config_variables(option)
          if type(option) == "table" then
            local mt = getmetatable(option)
            local result = {}
            for k, v in pairs(option) do
              result[expand_config_variables(k)] = expand_config_variables(v)
            end
            return setmetatable(result, mt)
          end
          if type(option) ~= "string" then
            return option
          end
          local ret = option
          for key, fn in pairs(var_placeholders) do
            ret = ret:gsub(key, fn)
          end
          return ret
        end
        local options = expand_config_variables(json.lsp["rust-analyzer"].initialization_options)
        client.config.settings["rust-analyzer"] = options

[jyn514]

this is definitely not any part of base nvim. i am not sure why nvim-dap is trying to support this; you're welcome to add it to your config i guess but i don't think we should recommend it in the dev guide.

[jyn514]

(note it's also doing it wrong, the working directory is not necessarily the same as the workspace folder)

[dianqk]

this is definitely not any part of base nvim. i am not sure why nvim-dap is trying to support this; you're welcome to add it to your config i guess but i don't think we should recommend it in the dev guide.

I think we should at least mention this? Otherwise, some people might not understand why rustfmt and proc macros aren't working?

[dianqk]

(note it's also doing it wrong, the working directory is not necessarily the same as the workspace folder)

I believe this is the most commonly used. I think we just need to mention the replacement of ${workspaceFolder}, and everyone can modify this variable in their own preferred way.

[jyn514]

I think we should at least mention this? Otherwise, some people might not understand why rustfmt and proc macros aren't working?

oh i was confused, i'm sorry. you're right - the Zed file this is copying is using workspaceFolder. this is a good solution to make that work without further configuration, thank you for researching it.

[jyn514]

I believe this is the most commonly used. I think we just need to mention the replacement of ${workspaceFolder}, and everyone can modify this variable in their own preferred way.

i think we should suggest vim.lsp.buf.list_workspace_folders()[1], not getcwd().