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

Ctrl+F doesn't bring up find dialog in cmd+PS #1629

New Issue
Closed
opened 2026-01-30 22:32:25 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 22:32:25 +00:00
Owner
Copy Link

Originally created by @asklar on GitHub (Jun 12, 2019).

Environment

Windows build number: 10.0.18362.86
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

cmd then launch powershell, ctrl+F prints ^F on the command line instead of bringing up the find dialog

Expected behavior

find dialog is brought up

Actual behavior

^F is displayed

image

Originally created by @asklar on GitHub (Jun 12, 2019). # Environment ```none Windows build number: 10.0.18362.86 Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce cmd then launch powershell, ctrl+F prints ^F on the command line instead of bringing up the find dialog <!-- A description of how to trigger this bug. --> # Expected behavior find dialog is brought up # Actual behavior ^F is displayed ![image](https://user-images.githubusercontent.com/22989529/59378767-efdd7180-8d09-11e9-857d-015d420807f7.png) <!-- What's actually happening? -->
claunia added the Product-ConhostIssue-QuestionResolution-By-DesignArea-Input labels 2026-01-30 22:32:25 +00:00
claunia commented 2026-01-30 22:32:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 12, 2019):

I'm pretty sure this is because of PSReadline using raw input mode. If you Remove-Module PSReadline, the find dialog will work again, but break a bunch of other powershell functionality psreadline provides.

For the record, Ctrl+F doesn't work in wsl for the same reason.

While it may not be the best behavior, it is by design, and hopefully something we can fix in the new terminal (by providing custom keybindings)

@zadjii-msft commented on GitHub (Jun 12, 2019): I'm pretty sure this is because of PSReadline using raw input mode. If you `Remove-Module PSReadline`, the find dialog will work again, but break a bunch of other powershell functionality psreadline provides. For the record, Ctrl+F doesn't work in wsl for the same reason. While it may not be the best behavior, it is *by design*, and hopefully something we can fix in the new terminal (by providing custom keybindings)
claunia commented 2026-01-30 22:32:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 12, 2019):

@lzybkr may be interested in the PSReadline angle -- perhaps there's a binding that'll work for this?

@DHowett-MSFT commented on GitHub (Jun 12, 2019): @lzybkr may be interested in the PSReadline angle -- perhaps there's a binding that'll work for this?
claunia commented 2026-01-30 22:32:27 +00:00
Author
Owner
Copy Link

@lzybkr commented on GitHub (Jun 12, 2019):

See this comment.

@lzybkr commented on GitHub (Jun 12, 2019): See this [comment](https://github.com/PowerShell/PSReadLine/issues/280#issuecomment-441338880).
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-Question Product-Conhost Resolution-By-Design
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#1629
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?