-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Ctrl+X not working #94
Comments
Hi, really happy to see you again. This is my mistake. In the latest You can open the { "keys": "<Ctrl+X>{5}",
"modes": "remote",
"script": "() => { window.activeText.cancelModemTransfering() }"
}, to: { "keys": "<Ctrl+X>{5}",
"modes": "remote",
"when": "terminal.activeView().isModemTransfering()",
"script": "() => { window.activeText.cancelModemTransfering() }"
}, I think this can solve the problem, and I will provide a more complete solution in the next version. |
Hi, WindTerm_2.1.0_Prerelease_3 has just been released and this issue has been fixed. You can download and check it now. Thank you. |
Self-test passed WindTerm_2.1.0_Prerelase_4, and this issue will be closed because no further activity occurs during the last month. Please reopen this issue if it is still valid. Thank you. |
Still have this issue in 2.6.0, which makes |
Good afternoon! Maybe it's just fitch, but when I try to exit the nano editor by pressing Ctrl+X, the terminal displays a message like in the screenshot. And the exit from nano does not happen. In previous versions, this was not observed.
The text was updated successfully, but these errors were encountered: