starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

arrow keys are not working in menus #9799

New Issue
Closed
opened 2026-01-31 02:04:04 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 02:04:04 +00:00
Owner
Copy Link

Originally created by @KaiDroste on GitHub (Jul 23, 2020).

Hello Together,

since the update from today (1.1.2021.0) I have the problem that the arrow keys are not working anymore into menus.
I have only the example of the esp idf menu. If I run it I can use all buttons but not the arrow keys anymore.
This is how the menu looks like. I want to go up and down with the arrow keys:
image

I also tested it in powershell and cmd. There is everything working fine.

EDIT: this Problem exist also at the powershell preview and also if you are using powershell into the VSCode terminal.

EDIT 2: I rolled now back to v1.0.1811.0 and there is everything working fine

Originally created by @KaiDroste on GitHub (Jul 23, 2020). Hello Together, since the update from today (1.1.2021.0) I have the problem that the arrow keys are not working anymore into menus. I have only the example of the esp idf menu. If I run it I can use all buttons but not the arrow keys anymore. This is how the menu looks like. I want to go up and down with the arrow keys: ![image](https://user-images.githubusercontent.com/59448194/88323773-06366900-cd23-11ea-8832-b4d3bc6c5895.png) I also tested it in powershell and cmd. There is everything working fine. EDIT: this Problem exist also at the powershell preview and also if you are using powershell into the VSCode terminal. EDIT 2: I rolled now back to v1.0.1811.0 and there is everything working fine
claunia commented 2026-01-31 02:04:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 24, 2020):

For future reference:
https://github.com/espressif/esp-idf

Does adding "experimental.input.forceVT": true to the root of your settings help by any chance?

@zadjii-msft commented on GitHub (Jul 24, 2020): For future reference: https://github.com/espressif/esp-idf Does adding `"experimental.input.forceVT": true` to the root of your settings help by any chance?
claunia commented 2026-01-31 02:04:06 +00:00
Author
Owner
Copy Link

@KaiDroste commented on GitHub (Jul 24, 2020):

Perfect. That works.

Beside this. Do you have any idea how to get this working at VSCode?

@KaiDroste commented on GitHub (Jul 24, 2020): Perfect. That works. Beside this. Do you have any idea how to get this working at VSCode?
claunia commented 2026-01-31 02:04:06 +00:00
Author
Owner
Copy Link

@Chips1234 commented on GitHub (Jul 26, 2020):

Perfect. That works.

Beside this. Do you have any idea how to get this working at VSCode?

Just use Visual Studio to build (Ctrl+Shift+B) then run (F5)

@Chips1234 commented on GitHub (Jul 26, 2020): > Perfect. That works. > > Beside this. Do you have any idea how to get this working at VSCode? Just use Visual Studio to build (<kbd>Ctrl+Shift+B</kbd>) then run (<kbd>F5</kbd>)
claunia commented 2026-01-31 02:04:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 27, 2020):

Thanks for confirming. This sounds an awful lot like #7074 ... can you follow the troubleshooting steps in https://github.com/microsoft/terminal/issues/7074#issuecomment-664668844?

@DHowett commented on GitHub (Jul 27, 2020): Thanks for confirming. This sounds an awful lot like #7074 ... can you follow the troubleshooting steps in https://github.com/microsoft/terminal/issues/7074#issuecomment-664668844?
claunia commented 2026-01-31 02:04:07 +00:00
Author
Owner
Copy Link

@KaiDroste commented on GitHub (Jul 28, 2020):

image

@KaiDroste commented on GitHub (Jul 28, 2020): ![image](https://user-images.githubusercontent.com/59448194/88712467-116e0800-d11a-11ea-8624-a3247a17f97c.png)
claunia commented 2026-01-31 02:04:07 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 28, 2020):

So, that's with experimental.input.forceVT turned on, which is the workaround. I'd be interested in seeing what happens with it turned off 😄

@DHowett commented on GitHub (Jul 28, 2020): So, that's with `experimental.input.forceVT` turned _on_, which is the workaround. I'd be interested in seeing what happens with it turned _off_ :smile:
claunia commented 2026-01-31 02:04:08 +00:00
Author
Owner
Copy Link

@KaiDroste commented on GitHub (Jul 28, 2020):

image
That's also not working correct. It will give either on true nor on false the same values. After switching a few times it gave other values. But now I'm not able to get those numbers back.

@KaiDroste commented on GitHub (Jul 28, 2020): ![image](https://user-images.githubusercontent.com/59448194/88714387-0d8fb500-d11d-11ea-887a-c462a461a30f.png) That's also not working correct. It will give either on true nor on false the same values. After switching a few times it gave other values. But now I'm not able to get those numbers back.
claunia commented 2026-01-31 02:04:08 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 28, 2020):

Thanks for following up. Those numbers are the ones I was looking for. You can return forceVT to true and use it in the future.

This is the same as /dup #7074, which I now understand. 😄

@DHowett commented on GitHub (Jul 28, 2020): Thanks for following up. Those numbers are the ones I was looking for. You can return `forceVT` to `true` and use it in the future. This is the same as /dup #7074, which I now understand. :smile:
claunia commented 2026-01-31 02:04:08 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 28, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 28, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Area-Input Issue-Bug Priority-2 Product-Terminal 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#9799
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?