Pressing F7 in Windows Terminal DOS brings up both the history AND a caret browsing message
From MSFT: 21451221
Well it interrupts every F7 keypress. this is especially sad when moving to the WSL world where more rich terminal apps like htop are more common. Those apps rely on handling those keypresses by themselves.
especially sad
Well, it's a bug in an as-yet-unreleased product; there's a maximum limit to its sadness :smile:
of course 馃ぃ馃ぃ馃ぃ was just trying to provide some context. no worries 馃槈
Is this "caret browsing" in Windows Terminal actually works? Having a way to select text on keyboard similar to caret browsing sounds like a great idea.
This is actually almost impossible to fix! Digging through the code for the Xaml platform keyboard handler, it intercepts F7 _before_ we're allowed to handle it (and reject its propagation.) The official recommendation from that team is to catch it in our island host's WM_KEYDOWN handler and synthesize it ourselves.
It might be totally impossible with our architecture.
Our hosting window doesn't even receive a _win32 window message_ it can suppress or transform; everything is going straight into the Xaml Island's input site.
/cc @Austin-Lamb who once had an idea about how we could solve this.
Austin, should I file this one on microsoft-ui-xaml for when WinUI 3.0 is available? :smile:
@DHowett-MSFT - yeah, that'd be great if you could file an issue on microsoft-ui-xaml for a better way to suppress F7 caret browsing dialog when using islands.
The problem is worsened by the fact that the "Do not ask me this again" option that it presents for your Caret Browsing choice is ignored between terminal close/launches
(this is now tracking https://github.com/microsoft/microsoft-ui-xaml/issues/1873)
Most helpful comment
The problem is worsened by the fact that the "Do not ask me this again" option that it presents for your Caret Browsing choice is ignored between terminal close/launches