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

vim alt key behaviour #17454

New Issue
Closed
opened 2026-01-31 05:42:58 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:42:58 +00:00
Owner
Copy Link

Originally created by @seongbin on GitHub (May 10, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.613

Other Software

VIM - Vi IMproved 8.1 (2018 May 18, compiled Feb 01 2022 09:16:32)

Steps to reproduce

Windows Terminal JSON config

        {
            "command": "unbound",
            "keys": "alt+j"
        },
        {
            "command": "unbound",
            "keys": "alt+k"
        },

Vim key bindings

  1 nnoremap <A-k> :m .-2<CR>==
  2 inoremap <A-j> <Esc>:m .+1<CR>==gi
  3 inoremap <A-k> <Esc>:m .-2<CR>==gi
  4 vnoremap <A-j> :m '>+1<CR>gv=gv
  5 vnoremap <A-k> :m '<-2<CR>gv=gv

Expected Behavior

I tried to unbound ALT key in Windows Terminal by adding json config to move lines up or down in vim. Unfortunatlly, unbound feature looks like not working for me.

Actual Behavior

Normal j/k cursor move

Originally created by @seongbin on GitHub (May 10, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.22000.613 ### Other Software VIM - Vi IMproved 8.1 (2018 May 18, compiled Feb 01 2022 09:16:32) ### Steps to reproduce Windows Terminal JSON config ``` { "command": "unbound", "keys": "alt+j" }, { "command": "unbound", "keys": "alt+k" }, ``` Vim key bindings ``` 1 nnoremap <A-k> :m .-2<CR>== 2 inoremap <A-j> <Esc>:m .+1<CR>==gi 3 inoremap <A-k> <Esc>:m .-2<CR>==gi 4 vnoremap <A-j> :m '>+1<CR>gv=gv 5 vnoremap <A-k> :m '<-2<CR>gv=gv ``` ### Expected Behavior I tried to unbound ALT key in Windows Terminal by adding json config to move lines up or down in vim. Unfortunatlly, unbound feature looks like not working for me. ### Actual Behavior Normal j/k cursor move
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:42:59 +00:00
claunia commented 2026-01-31 05:43:00 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 10, 2022):

Curious. What keyboard layout are you using? Are you using an input method?

This works for me (US-104 keyboard, en-US):

vim-alt-k

@DHowett commented on GitHub (May 10, 2022): Curious. What keyboard layout are you using? Are you using an input method? This works for me (US-104 keyboard, en-US): ![vim-alt-k](https://user-images.githubusercontent.com/189190/167682265-2766bb1b-3ebd-4a32-981a-f92190b7d5a9.gif)
claunia commented 2026-01-31 05:43:00 +00:00
Author
Owner
Copy Link

@seongbin commented on GitHub (May 11, 2022):

In this PC, I have installed us-en and c/j/k input
image
And tried with en-us keyboard
Animation

!EDIT
When I bind shift key instead alt key to move line, it works.

@seongbin commented on GitHub (May 11, 2022): In this PC, I have installed us-en and c/j/k input ![image](https://user-images.githubusercontent.com/1720769/167756053-80d18a2e-0a74-4c67-ae9a-f107cd6e4d62.png) And tried with en-us keyboard ![Animation](https://user-images.githubusercontent.com/1720769/167756675-ed994dbd-4a3d-4999-b526-b1488165f36c.gif) !EDIT When I bind shift key instead alt key to move line, it works.
claunia commented 2026-01-31 05:43:00 +00:00
Author
Owner
Copy Link

@seongbin commented on GitHub (May 19, 2022):

NVM, after I unbind all unnecessary ALT key in Windows Terminal, it works.

@seongbin commented on GitHub (May 19, 2022): NVM, after I unbind all unnecessary ALT key in Windows Terminal, it works.
claunia commented 2026-01-31 05:43:00 +00:00
Author
Owner
Copy Link

@CervEdin commented on GitHub (Apr 21, 2023):

@seongbin what do you mean by "unbind all unnecessary ALT key"? Did you remove all Actions involving ALT?

@CervEdin commented on GitHub (Apr 21, 2023): @seongbin what do you mean by "unbind all unnecessary ALT key"? Did you remove all Actions involving ALT?
claunia commented 2026-01-31 05:43:01 +00:00
Author
Owner
Copy Link

@GTonehour commented on GitHub (Apr 11, 2025):

@CervEdin In Windows Terminal "Actions" settings, alt+shift+down is mapped to resize panel down (respectively up). Removing that keybinding solves the problem.

@GTonehour commented on GitHub (Apr 11, 2025): @CervEdin In Windows Terminal "Actions" settings, `alt+shift+down` is mapped to `resize panel down` (respectively up). Removing that keybinding solves the problem.
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 Issue-Bug Needs-Attention Needs-Tag-Fix Needs-Triage
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#17454
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?