Search history failed(failed-fwd-i-search)
See original GitHub issuePress Ctrl + s
, then enter the content to search, and ‘failed-fwd-i-search’ will be displayed directly, and the search will fail.
PS version: 7.1.1 PSReadline version: 2.1.0-beta2 os: 10.0.18362.1014 (WinBuild.160101.0800) PS file version: 7.1.1.0 HostName: ConsoleHost BufferWidth: 120 BufferHeight: 9001
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Search history failed(failed-fwd-i-search)
Press Ctrl + s , then enter the content to search, and 'failed-fwd-i-search' will be displayed directly, and the search will fail.
Read more >Clear Web Browser Data (History, Cookies, and Cache)
If you receive this error continuously, lease try clearing the cache/cookies from your web browser. Then close all the browser windows and try...
Read more >Manage & delete your Search history - Android
Fix problems with your Search history · On your Android phone or tablet, open the Google app . · At the top right,...
Read more >Clear your web browser's cache, cookies, and history
At the top of the "Clear browsing data" window, select Advanced. · Select the following: Browsing history; Download history; Cookies and other ...
Read more >SWIFT Clear Browser history
If you experience difficulties trying to view data or access the log-in page for SWIFT, clearing your browsing history may help resolve these...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
History search always starts from the end of the list, so you should start with a reverse search using <kbd>Ctrl+r</kbd>.
The forward search is used when you go too far in your reverse search, similar to how you start with <kbd>UpArrow</kbd> but when you go too far, you use <kbd>DownArrow</kbd>.
PSReadLine emulates GNU readline which does not wrap. I think this is a good thing as it can be hard to know when you’ve wrapped. Editors naturally provide a nice visual cue that you’ve wrapped (either implicit in the context, or explicit in the current line number in the status bar). PSReadLine could provide something similar but does not, so I would not expect wrapping to be popular.