New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop current running process in runner #79
Comments
Hi @giovannibenussi, good question! Unfortunately the current version of the plugin does not support sending That said, I've wanted behavior like this and similar before, so I pulled together a quick branch to test out a new API. You can check out the branch here: https://github.com/christoomey/vim-tmux-runner/tree/cjt-add-send-raw-command. It introduces two new commands:
Would you mind trying out this branch to see if this works for you? Assuming it works, I'll update the documentation and merge this in. Thanks! |
Hi @christoomey, thanks for your fast answer and solution! I don't really understand what do you mean with the mapping for
I try that and it works as expected! That was what you mean? Regards! |
I was trying various version of I'm going to keep this issue open until I merge in the final version, but hopefully the branch is enough to keep you going in the mean time. Thanks! |
That's very nice, I like that mapping! Thanks a lot @christoomey! :) |
Thanks @christoomey! It's very well and improves my workflow! |
@christoomey love this! Edit: Created PR #98 updating the documentation. Would love to see this merged! |
It is possible to send a SIGINT or stop a process that is running in the current attached pane.
This can be useful for example when you're coding something in vim that takes some seconds to finish and you want to execute it directly in an attached pane without leave vim. If you realize that you make a mistake, it can be easier to cancel directly the running process without leave vim.
Currently the process is (starting in vim): move to the attached pane, press ctrl-c, go back to vim.
Also, this can be useful to exit copy mode in the attached pane directly from vim (solves partially #70)
The text was updated successfully, but these errors were encountered: