Skip to content
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

VimuxInterruptRunner using wrong sendkeys #159

Open
kimperator opened this issue Oct 12, 2017 · 2 comments
Open

VimuxInterruptRunner using wrong sendkeys #159

kimperator opened this issue Oct 12, 2017 · 2 comments

Comments

@kimperator
Copy link

kimperator commented Oct 12, 2017

Hello I got some problem with the VimuxInterruptRunner

First of all my Use-Case:

execute VimuxRunCommand to execute "build.sh" to build and run server component. Since it's a server component ant blocking this shell is now executing this program.

For recompiling I want to interrupt the running server (sending Ctrl+c to the pane) and restarting the last server so I use a key-mapping for killing the current build using VimuxInterruptRunner and VimuxRunLastCommand

Problem:

This is currently not working, because VimuxInterruptRunner is sending the key "^c" instead of "C-c".

Questions for implementing a solution

Is this key valid in other terminals, or is this simple a bug?
on the one side we could simply edit change the sended keys, otherwise we have to make it variable.

Which one would you prefer?

Used toolset:
Archlinuxarm for raspberry pi 2
Vim 8.0
tmux 2.6

Workarround

Calling Vimux SendKeys directly

nnoremap <C-e> :call VimuxOpenRunner()<CR>:sleep 10m<CR>:call VimuxSendKeys("C-c")<CR>:sleep 20m<CR>:VimuxPromptCommand<CR>
nnoremap <C-l> :call VimuxSendKeys("C-c")<CR>:sleep 50m<CR>:VimuxRunLastCommand<CR>   
@alfunx
Copy link
Contributor

alfunx commented Oct 16, 2017

:VimuxInterruptRunner does work for me.

On:
Vim 8.0.1176
tmux 2.6
Zsh 5.4.2 as well as on bash 4.4.12(1)
termite v12
Arch Linux 4.13.6-1

@alerque
Copy link
Member

alerque commented Feb 14, 2021

Is this still a confirmed issue? If so is there any way we could work up a minimal test case with some dummy shell command so we can figure out who it does and doesn't work for with as little setup as possible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants