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

Midnight Command (mc.exe) doesn't accept mouse input (selects text instead) #14328

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

Originally created by @DrPepperBianco on GitHub (Jun 24, 2021).

I installed Midnight commander on my system (Windows 10). If I launch it "C:\Program Files (x86)\Midnight Commander\mc.exe" via Windows Terminal and try to click on anything it doesn't work. It instead only selects the text.

If I try to google this problem, I only get results, telling me, that "Windows Terminal" support mouse input for Midnight Commander from around March 2020. These articles mean linux though, either via SSH or via WSL. And if I connect via SSH to linux and then use midnight commander the mouse works. But if I start a midnight commander session locally, it doesn't.

I actually had the same problem, when I just started "mc.exe" in a regular console window. But there I opened the properties and deactivates "Quick Edit". Thus selection had to be activated explicitly and other mouse clicks works as expected.

But I didn't found a similar option in the settings of Windows Terminal.

Originally created by @DrPepperBianco on GitHub (Jun 24, 2021). I installed Midnight commander on my system (Windows 10). If I launch it "C:\Program Files (x86)\Midnight Commander\mc.exe" via Windows Terminal and try to click on anything it doesn't work. It instead only selects the text. If I try to google this problem, I only get results, telling me, that "Windows Terminal" support mouse input for Midnight Commander from around March 2020. These articles mean linux though, either via SSH or via WSL. And if I connect via SSH to linux and then use midnight commander the mouse works. But if I start a midnight commander session locally, it doesn't. I actually had the same problem, when I just started "mc.exe" in a regular console window. But there I opened the properties and deactivates "Quick Edit". Thus selection had to be activated explicitly and other mouse clicks works as expected. But I didn't found a similar option in the settings of Windows Terminal.
claunia commented 2026-01-31 04:07:16 +00:00
Author
Owner
Copy Link

@zadjii commented on GitHub (Jun 25, 2021):

What version of the terminal are you using? And what version of mc.exe?

@zadjii commented on GitHub (Jun 25, 2021): What version of the terminal are you using? And what version of mc.exe?
claunia commented 2026-01-31 04:07:17 +00:00
Author
Owner
Copy Link

@KaranKad commented on GitHub (Jun 29, 2021):

Mouse input support for windows applications was added in v1.9.1445.0 Preview. Try using that.

@KaranKad commented on GitHub (Jun 29, 2021): Mouse input support for windows applications was added in v1.9.1445.0 Preview. Try using that.
claunia commented 2026-01-31 04:07:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 29, 2021):

Yep! This is correct.

Now, if you're using 1.9+ and mouse input doesn't work for MC (Windows), it could be the case that it is not managing the mouse mode in a way that Terminal can detect.

For maximal behavioral compatibility with Windows applications, we had to make a couple compromises in how mouse mode was detected. Otherwise, all windows applications would try to eat cursor input events ... which would be significantly worse from a user experience standpoint 😦

@DHowett commented on GitHub (Jun 29, 2021): Yep! This is correct. Now, if you're using 1.9+ and mouse input doesn't work for MC (Windows), it could be the case that it is not managing the mouse mode in a way that Terminal can detect. For maximal behavioral compatibility with Windows applications, we had to make a couple compromises in how mouse mode was detected. Otherwise, *all* windows applications would try to eat cursor input events ... which would be significantly worse from a user experience standpoint 😦
claunia commented 2026-01-31 04:07:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 11, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jul 11, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#14328
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?