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
As pointed out by @tonywoode, the method of tmux send-keys is not wonderfully ideal, mostly because it adds a command to the user's shell history.
The issue with a conventional call to vim *flags* *files* is that the call is blocking in Python until Vim closes. This means that tmux believes that the currently running program is Python, not Vim. While this is usually fine, it breaks compatibility with the excellent vim-tmux-navigator.
However, @tonywoode has also found a potential solution to this issue, by removing the command from the history after it's been made. There's a couple of solutions outlined regarding how this can be done on StackOverflow.
The text was updated successfully, but these errors were encountered:
As pointed out by @tonywoode, the method of tmux send-keys is not wonderfully ideal, mostly because it adds a command to the user's shell history.
The issue with a conventional call to
vim *flags* *files*
is that the call is blocking in Python until Vim closes. This means that tmux believes that the currently running program is Python, not Vim. While this is usually fine, it breaks compatibility with the excellent vim-tmux-navigator.However, @tonywoode has also found a potential solution to this issue, by removing the command from the history after it's been made. There's a couple of solutions outlined regarding how this can be done on StackOverflow.
The text was updated successfully, but these errors were encountered: