wezterm_cli_path problem with wezterm and WSL

[MrRothstein]

It doesn't seem like the plugin is correctly setting the wezterm_cli_path by default. In lazy vim, I can only get it to work with the following config:

return {
  "mrjones2014/smart-splits.nvim",
  lazy = false,
  opts = {
    wezterm_cli_path = "wezterm.exe",
  },
}

If I don't set wezterm_cli_path this way, I'm able switch into a vi tab, but not out of it (it just wraps).

[mrjones2014]

Does anything from this discussion help?

Unfortunately I do not have any Windows machines so I can't really help debug issues like this with WSL.

[MrRothstein]

I have it set in the path of both host and vm. And I'm able to actually execute "wezterm.exe" commands with lua from the minibuffer. And it works when I manually set the option. I'm guessing the logic to default it to the windows executable is off somehow, but I can't tell what it is... is_WSL check appears to be true (at least when I execute it manually from the minibuffer). Maybe the new_config picks up a value for wezterm_cli_path before it's checked here:

smart-splits.nvim/lua/smart-splits/config.lua

Line 119 in 22ca8bf

new_config.wezterm_cli_path = new_config.wezterm_cli_path or 'wezterm.exe'

that's as far as I got...

[MrRothstein]

I just reread that thread and I completely missed the first comment... Yes, calling setup manually works

[MrRothstein]

I think I got it... I don't think lazyvim is calling the setup function at all. When I add an explicit call to it, it works as expected:

return {
  "mrjones2014/smart-splits.nvim",
  lazy = false,
  config = function()
    require("smart-splits").setup({})
  end,
}

[mrjones2014]

I believe in lazy.nvim you can also just do config = true and it's equivalent

[mrjones2014]

Also considering this has come up a couple times now, I think maybe I can make the experience out of the box a bit better by lazily evaluating that config option