PowerShell / PowerShell/Win32-OpenSSH
Win32-OpenSSH V8.9.1.0p1-Beta sending Ctrl+space is not clean enough to cause <c-space> not to be processed correctly
Open
@tgauth is already working on this.
Since Oct 17, 2022.
Investigate
- Dominant language
- No language data
- Stars
- 8.3k
- Forks
- 819
- PR merge metrics
- No merged PRs in 30d
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
I'm using the Win32-OpenSSH V8.9.1.0p1-Beta version on Windows, connecting to a remote archlinux host, and using coc.nvim to code-completion by pressing the Ctrl + Space shortcut, but extra characters appear. In WSL2, Ctrl + Space successfully handles completion syntax. I suspect it's a problem with Win32-OpenSSH V8.9.1.0p1-Beta
Steps to reproduce
- Please install the latest version of
Arch Linuxin advance. - Execute the
install.shscript of vimrc to automatically install with one click. - Using Win32-OpenSSH V8.9.1.0p1-Beta to connect to a remote
Arch Linuxhost onWindows. - Create arbitrary cpp files, such as
vim demo.cpp - Enter the
cppcode, pressCtrl + Spaceto complete the code.
key code
Use <c-space> to trigger completion.
Expected behavior
Successfully handle code completion.
Actual behavior
Code completion, extra characters appear.
Error details
No response
Environment data
- Windows 10 Pro x86_64 21H2
- Windows Terminal x86_64 1.14.1962.0
- Win32-OpenSSH V8.9.1.0p1-Beta
- Arch Linux x86_64
- openSUSE Tumbleweed on Windows 10 x86_64 (WSL2)
- vim 9.0.236
Version
V8.9.1.0p1-Beta
Visuals
Expected behavior

Actual behavior

OS Environment


Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.