Help with diagnosing plugin crash on parsing of prompt variables

[helibom]

Hi there,

I find this plugin tremendously interesting, which is why I'm frustrated that I'm not able to resolve this issue I have with requests including prompt variables.

The problem I'm experiencing is that I'm running in to this issue when trying to Rest run any .http file that includes prompt variables.

I'm currently using the example from /spec/examples.

The issue does not reproduce when I run the minimal repro.lua config for lazy.nvim.

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
    spec = {
        "rest-nvim/rest.nvim",
        {
            "nvim-treesitter/nvim-treesitter",
            build = ":TSUpdate",
            main = "nvim-treesitter.configs",
            opts = {
                ensure_installed = { "http" },
                sync_install = false,
                highlight = { enable = true },
                indent = { enable = true },
            },
        },
    },
})

I'm running Neovim v.0.10.2 and therefore I'm not suspecting any compatibility issue with the core treesitter library in Neovim and the plugin.

So what remains? Configuration differences between the repro.lua config and my actual config.

Below you can see the repro.lua state on the left; my actual config on the right

And for what it's worth, below is the state of the nvim-treesitter plugin in both configurations.

I can also note that :InspectTree seems to yield the exact same syntax tree from the same prompt-example.http in both cases.

Any ideas on what I could try next?

I'm grudging the task of incrementally adding every single one of my plugins to the repro.lua config to identify some interferring plugin, but perhaps that is what is necessary...

[helibom]

I realized that it's one of my plugins responsible for a custom input prompt that messes up the input. Just haven't tracked down which one, since apparently more than one plugins that I'm using is providing new UIs for input prompts.

[helibom]

Seems like I've tracked it down to the fact that any plugin that interferes with the input prompt (e.g. by providing a custom prompt UI component) will wreck the algorithm that interpolates the prompt variables.
In my case, I can resolve the issue by removing my plugins yetone/avante.nvim and folke/snacks.nvim (snacks.nvim/input). Reintroducing either of these plugins causes the issue from the original post to reappear.