starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Text input fields in Settings have autocorrect enabled (oops) #15078

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

Originally created by @joslinpr on GitHub (Sep 3, 2021).

Windows Terminal version (or Windows build number)

Windows 10 ECB 9.0 SAC 20H2 / Windows Feature Experience Pack 120.2212.551.0

Other Software

OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

Steps to reproduce

Create a New Profile / Edit an existing profile.

Under General, type into command line:

C:\Windows\System32\OpenSSH\ssh.exe -A -i C:\Users\username\.ssh\id_rsa user@hostname

What you get is:

C:\Windows\System32\OpenSSH\ssh.exe -A-I C:\Users\username\.ssh\id_rsa username@hostname

Note the capital I. This does not occur when you cut and paste, but will if you remove the "I" and type "i".

If you use the new profile, you get the unexpected error "no support for PKCS#11." from ssh.exe.

Expected Behavior

What you type is what you get.

Actual Behavior

Autocorrect changes -i to -I, leading to an error message.

Originally created by @joslinpr on GitHub (Sep 3, 2021). ### Windows Terminal version (or Windows build number) Windows 10 ECB 9.0 SAC 20H2 / Windows Feature Experience Pack 120.2212.551.0 ### Other Software OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5 ### Steps to reproduce ### Create a New Profile / Edit an existing profile. #### Under General, type into command line: ```C:\Windows\System32\OpenSSH\ssh.exe -A -i C:\Users\username\.ssh\id_rsa user@hostname``` #### What you get is: ``` C:\Windows\System32\OpenSSH\ssh.exe -A ```**-I**``` C:\Users\username\.ssh\id_rsa username@hostname``` Note the capital I. This does not occur when you cut and paste, but will if you remove the "I" and type "i". If you use the new profile, you get the unexpected error "no support for PKCS#11." from ```ssh.exe```. ### Expected Behavior What you type is what you get. ### Actual Behavior Autocorrect changes -i to -I, leading to an error message.
claunia commented 2026-01-31 04:27:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2021):

Jeez-o, we should not have autocorrect enabled on our input fields!

@DHowett commented on GitHub (Sep 3, 2021): Jeez-o, we should not have autocorrect enabled on our input fields!
claunia commented 2026-01-31 04:27:52 +00:00
Author
Owner
Copy Link

@ianjoneill commented on GitHub (Sep 3, 2021):

This looks easy to fix - I assume you'd like to keep autocorrect enabled in text-boxes for names (e.g. profile name, tab title), but not for paths/command lines etc.

@ianjoneill commented on GitHub (Sep 3, 2021): This looks easy to fix - I assume you'd like to keep autocorrect enabled in text-boxes for names (e.g. profile name, tab title), but not for paths/command lines etc.
claunia commented 2026-01-31 04:27:52 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 5, 2021):

Why is only "-i" being capitalized? The first option "-A" won't be autocorrected if typed "-a". None other ssh.exe options are being capitalized. This is not SSH client related.

Just by entering "-i" in the command line box it will be turned into "-I". I tried "--i" and "---i" and same behavior. However, if "I" is being corrected any other "i" entries won't be capitalized.

@elsaco commented on GitHub (Sep 5, 2021): Why is only "-i" being capitalized? The first option "-A" won't be autocorrected if typed "-a". None other ssh.exe options are being capitalized. This is not SSH client related. Just by entering "-i" in the command line box it will be turned into "-I". I tried "--i" and "---i" and same behavior. However, if "I" is being corrected any other "i" entries won't be capitalized.
claunia commented 2026-01-31 04:27:52 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 20, 2021):

:tada:This issue was addressed in #11137, which has now been successfully released as Windows Terminal Preview v1.12.2922.0.🎉

Handy links:

@ghost commented on GitHub (Oct 20, 2021): :tada:This issue was addressed in #11137, which has now been successfully released as `Windows Terminal Preview v1.12.2922.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.12.2922.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-SettingsUI Help Wanted Issue-Bug Needs-Triage Priority-2 Product-Terminal Resolution-Fix-Committed
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#15078
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?