VimuxRunCommand just echoes (some of) the command into the current buffer

[cszczepaniak]

My setup:

• wezterm in WSL2
• tmux 3.0a
• neovim 0.10.0

When I call :call VimuxRunCommand("echo 'foobar'"), I get o 'foobar' printed where my cursor was in the buffer. If I use vim-test with strategy vimux within a Go test, I get the following printed in my buffer:

ear; echo -e 'go test -run '\''TestSomething$'\'' ./dir'; go test -run 'TestSomething$' ./dir

In both cases, no tmux split is created. How can I debug this further and fix it?

[beorgler1]

Same here with same setup except of Windows Terminal instead of wezterm.

[mvanderkamp]

This is interesting. I'm having trouble replicating, so I might need more information:

1. Do you have any splits open when you run the command?
   1. If yes, how are they set up and which split are you running VimuxRunCommand from?
2. What are your vimux settings? The most useful will probably be your values for the VimuxRunnerType, VimuxRunnerQuery, and VimuxUseNearest settings, but if you can share all of your settings that would be helpful!

The closest I've come to replicating so far is if I have one vertical split in my window, vim or nvim running in both panes, use let VimuxRunnerQuery = {'pane': '{left}'}, then call VimuxRunCommand from the vim instance in the split on the right.

[mvanderkamp]

Oh hold on this might be a windows thing. Can you try setting let VimuxUseNearest = v:false?