starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

windows terminal will send one more character when use vim view mode to select characters send to repl using vim-repl or Nvim-R plugin #13074

New Issue
Closed
opened 2026-01-31 03:32:59 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 03:32:59 +00:00
Owner
Copy Link

Originally created by @ZihaoXingUP on GitHub (Mar 18, 2021).

windows terminal will send one more character when use vim view mode to select characters send to repl using vim-repl or Nvim-R plugin ,but when i use xshell, it won't send one more character and can work well. so ,i think it is the windows terminal's problem , and need to be solved.

use vim-repl to send 'a' on windows terminal :

image

use vim-repl to send 'a' on xshell:

image

Originally created by @ZihaoXingUP on GitHub (Mar 18, 2021). windows terminal will send one more character when use vim view mode to select characters send to repl using [vim-repl](https://github.com/sillybun/vim-repl.git) or [Nvim-R](https://github.com/jalvesaq/Nvim-R.git) plugin ,but when i use xshell, it won't send one more character and can work well. so ,i think it is the windows terminal's problem , and need to be solved. use vim-repl to send 'a' on windows terminal : ![image](https://user-images.githubusercontent.com/68001792/111582657-1b05c680-87f6-11eb-9c7e-221001aaae3d.png) use vim-repl to send 'a' on xshell: ![image](https://user-images.githubusercontent.com/68001792/111582854-661fd980-87f6-11eb-988f-9008fa8c9fb9.png)
claunia added the Needs-TriageResolution-Duplicate labels 2026-01-31 03:32:59 +00:00
claunia commented 2026-01-31 03:33:00 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 18, 2021):

Please do not open duplicate issue.

#9530

@skyline75489 commented on GitHub (Mar 18, 2021): Please do not open duplicate issue. #9530
claunia commented 2026-01-31 03:33:00 +00:00
Author
Owner
Copy Link

@ZihaoXingUP commented on GitHub (Mar 18, 2021):

Please do not open duplicate issue.

#9530

the windows terminal worker said to me "This is a common problem people have with vim. The character under the cursor is part of the visual selection. This is true on every terminal emulator on windows". he said "this problem also in putty."
but when when i use the xshell on windows, it can work well and won't send one more character. but he din't see it work on xshell in windows.

@ZihaoXingUP commented on GitHub (Mar 18, 2021): > Please do not open duplicate issue. > > #9530 the windows terminal worker said to me "This is a common problem people have with vim. The character under the cursor is part of the visual selection. This is true on every terminal emulator on windows". he said "this problem also in putty." but when when i use the xshell on windows, it can work well and won't send one more character. but he din't see it work on xshell in windows.
claunia commented 2026-01-31 03:33:01 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 18, 2021):

Yeah I get it. I happen to know this "windows terminal worker" personally. My point is you can just use that issue for discussion. Please do not open duplicate issue for the same problem, because this causes unnecessary noises for people who subscribe this repo.

@skyline75489 commented on GitHub (Mar 18, 2021): Yeah I get it. I happen to know this "windows terminal worker" personally. My point is you can just use that issue for discussion. Please do not open duplicate issue for the same problem, because this causes unnecessary noises for people who subscribe this repo.
claunia commented 2026-01-31 03:33:01 +00:00
Author
Owner
Copy Link

@ZihaoXingUP commented on GitHub (Mar 18, 2021):

Yeah I get it. I happen to know this "windows terminal worker" personally. My point is you can just use that issue for discussion. Please do not open duplicate issue for the same problem, because this causes unnecessary noises for people who subscribe this repo.

because he know the problem in windows terminal, but he close the issue so that i can't find my issue and reply him.

@ZihaoXingUP commented on GitHub (Mar 18, 2021): > Yeah I get it. I happen to know this "windows terminal worker" personally. My point is you can just use that issue for discussion. Please do not open duplicate issue for the same problem, because this causes unnecessary noises for people who subscribe this repo. because he know the problem in windows terminal, but he close the issue so that i can't find my issue and reply him.
claunia commented 2026-01-31 03:33:02 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 18, 2021):

Oh man, Here, just click the link #9530 .

You can reply to closed issue. You can even reopen them, if you like.

@skyline75489 commented on GitHub (Mar 18, 2021): Oh man, Here, just click the link #9530 . You can reply to closed issue. You can even reopen them, if you like.
claunia commented 2026-01-31 03:33:02 +00:00
Author
Owner
Copy Link

@ZihaoXingUP commented on GitHub (Mar 18, 2021):

Oh man, Here, just click the link #9530 .

You can reply to closed issue. You can even reopen them, if you like.

ok, thank's your reply.

@ZihaoXingUP commented on GitHub (Mar 18, 2021): > Oh man, Here, just click the link #9530 . > > You can reply to closed issue. You can even reopen them, if you like. ok, thank's your reply.
claunia commented 2026-01-31 03:33:04 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 18, 2021):

No problem.

Please do not take this personally. It's just an issue. It's not a Bitcoin or something. No one want to "steal" your issue away. We all trying to help. We just need to understand the problem better. That "windows terminal worker" is a good guy who leads a great team. But as you can see there's 1200+ open issues. It takes time (sometimes a very long time) to understand and solve an issue. We like to hear feedbacks from everyone. Just please be patient.

@skyline75489 commented on GitHub (Mar 18, 2021): No problem. Please do not take this personally. It's just an issue. It's not a Bitcoin or something. No one want to "steal" your issue away. We all trying to help. We just need to understand the problem better. That "windows terminal worker" is a good guy who leads a great team. But as you can see there's 1200+ open issues. It takes time (sometimes a very long time) to understand and solve an issue. We like to hear feedbacks from everyone. Just please be patient.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Triage Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13074
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?