You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using slimux for half a year now and I love it. Until recently I've been using bash as my default shell, but now I have really been enjoying fish (friendly interactive shell). I have found a problem whereby within a fish shell I start tmux, create two panes, open vim in the top pane and my repl in the bottom pane, I send the first line and hence select the bottom pane, but it appears in the top pane! The lines of vim get send back to vim and not to the repl!
If I repeat the above procedure from bash it works fine. Does anyone know what could cause this?
Thanks :)
The text was updated successfully, but these errors were encountered:
Hmm, can you describe more of your environment? I just installed fish (cool shell by the way, I hadn't tried it before) and didn't see this behavior. I'm running ViM 7.4 on Arch Linux (technically in a chroot via chroagh). Does the problem still occur if you have bash as your default shell, but switch to fish (both for launching tmux and in the top pane when you launch vim)?
Fish is cool, especially with oh-my-fish :) I'm running fedora 22 with vim 7.4.827. I can confirm the problem does not arise when bash is my default shell but switch to fish prior to launching tmux.
I've been using slimux for half a year now and I love it. Until recently I've been using bash as my default shell, but now I have really been enjoying fish (friendly interactive shell). I have found a problem whereby within a fish shell I start tmux, create two panes, open vim in the top pane and my repl in the bottom pane, I send the first line and hence select the bottom pane, but it appears in the top pane! The lines of vim get send back to vim and not to the repl!
If I repeat the above procedure from bash it works fine. Does anyone know what could cause this?
Thanks :)
The text was updated successfully, but these errors were encountered: