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

Ctrl+X not working #94

Closed
karagi4 opened this issue May 7, 2021 · 4 comments
Closed

Ctrl+X not working #94

karagi4 opened this issue May 7, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@karagi4
Copy link

karagi4 commented May 7, 2021

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.

image

@kingToolbox
Copy link
Owner

kingToolbox commented May 7, 2021

Hi, really happy to see you again. This is my mistake. In the latest WindTerm_2.1.0_Prerelease_2 version , I assigned the shortcut key <Ctrl+X>{5} to cancel the running lz/sz, this results in the <Ctrl+X> key being preferentially used to match <Ctrl+X>{5} instead of being sent to the remote server.

You can open the WindTerm-install-path/global/wind.keymaps and modify:

  { "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.

@kingToolbox kingToolbox self-assigned this May 7, 2021
@kingToolbox kingToolbox added the bug Something isn't working label May 7, 2021
@kingToolbox
Copy link
Owner

kingToolbox commented May 27, 2021

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.

@kingToolbox
Copy link
Owner

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.

@tangruixun
Copy link

Still have this issue in 2.6.0, which makes Emacs unusable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants