When is configuration evaluated?

[AlexXandreE]

Hi, new to nvim and dap configuration.

I'm trying to setup a dynamic debug workspace, atm I'm using lua for configuration but I don't see how can I reuse the module variable to the cwd. I could try to do this with another function outside of dap.configurations which is why I'm asking when is this evaluated, since the program function call only happens when I trigger the debug.

dap.configurations.cpp = {
  {
    name = "Launch",
    type = "lldb",
    request = 'launch',
    program = function()
        local module = vim.fn.input('Module name: ')
        local apps = {'non_test_app', 'non_test_app2'}
        local is_test = true
        for k, v in ipairs(apps) do
            if module == v then
                is_test = false
            end
        end

        if is_test then
            return '${workspaceFolder}/bin/tests/debug/' .. module .. '/' .. module .. '-tests'
        end
      return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/bin/', 'file')
    end,
    cwd = ' This should be the folder with the same name as <MODULE> above',
    stopOnEntry = false,
    args = {}
  }
}

Thanks for the help :)

[mfussenegger]

The configuration is evaluated when you launch a new debug session.

I think what could work is using a forward reference to mutate the configuration within the program function:

local lldb_launch
lldb_launch = {
  name = "Launch",
  type = "lldb",
  request = 'launch',
  program = function()
    local module = vim.fn.input('Module name: ')
    local apps = {'non_test_app', 'non_test_app2'}
    local is_test = true

    -- 👇❗
    lldb_launch.cwd = 'whatever'

    for _, v in ipairs(apps) do
      if module == v then
          is_test = false
      end
    end
    if is_test then
        return '${workspaceFolder}/bin/tests/debug/' .. module .. '/' .. module .. '-tests'
    end
    return vim.fn.input('Path to executable: ', vim.fn.getcwd() .. '/bin/', 'file')
  end,
  stopOnEntry = false,
  args = {}
}
dap.configurations.cpp = { lldb_launch, }

[AlexXandreE]

Thx a lot, didn't know this would work :)