René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`conhost.exe` console windows on Windows: cmdlets, e.g. `Select-String`,  do not render VT (ANSI) escape sequences in their for-display output with direct input from native (external) programs ","articleBody":"### Prerequisites\r\n\r\n- [X] Write a descriptive title.\r\n- [X] Make sure you are able to repro it on the [latest released version](https://github.com/PowerShell/PowerShell/releases)\r\n- [X] Search the existing issues.\r\n- [X] Refer to the [FAQ](https://github.com/PowerShell/PowerShell/blob/master/docs/FAQ.md).\r\n- [X] Refer to [Differences between Windows PowerShell 5.1 and PowerShell](https://learn.microsoft.com/powershell/scripting/whats-new/differences-from-windows-powershell).\r\n\r\n### Steps to reproduce\r\n\r\n* A reopening of #18294, #18771, and #19813, which were inappropriately closed as `Resolution-External`.\r\n* The problem still exists in v7.4.0, and was introduced in 7.3.0-preview.2, according to @Hermel's findings.\r\n\r\nTo recap the repro steps: The problem occurs:\r\n\r\n* on Windows\r\n* in regular console windows (`conhost.exe`), _not_ in Windows Terminal\r\n  * with the `VirtualTerminalLevel` registry value in key `HKEY_CURRENT_USER\\Console` NOT manually set to `1`, i.e. either set to `0` or - as is the default - with the value _not defined_.\r\n* with input from _external programs_\r\n\r\n\r\n```powershell\r\n# From a conhost.exe console window on Windows,\r\n# with the defaults (see note re `VirtualTerminalLevel` above).\r\ncmd /c echo foo | Select-String f\r\n```\r\n\r\nSuboptimal workarounds: \r\n\r\n* Enclose the external-program call in `(...)`\r\n* Enable ANSI/VT support in `conhost.exe` console windows _system-wide_, via the registry:\r\n  * `Set-ItemProperty HKCU:\\Console VirtualTerminalLevel -Type DWORD 1`\r\n  * The preferable alternative, namely to make PowerShell _itself_ unconditionally enable ANSI/VT support (something that Windows Terminal already does), was declined, even though it would be less drastic than a _system-wide_ setting: https://github.com/PowerShell/PowerShell/issues/19101#issuecomment-1480308331\r\n\r\nSuspected cause, quoting @SeeminglyScience from https://github.com/PowerShell/PowerShell/issues/18294#issuecomment-1281181217: \r\n\r\n\u003e I would guess it's related to https://github.com/PowerShell/PowerShell/pull/16612 but I've looked it over and I can't easily see how. We should be re-enabling VT more often rather than less, so something is a little off for sure. /cc @daxian-dbw\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\n```console\r\nfoo\r\n```\r\n\r\nwith `f` inverted, to highlight the matching part of the line.\r\n\r\n\r\n### Actual behavior\r\n\r\n```console\r\n←[7mf←[0moo\r\n```\r\n\r\nThat is, the VT escape sequence weren't rendered.\r\n\r\n### Error details\r\n\r\n_No response_\r\n\r\n### Environment data\r\n\r\n```powershell\r\nPowerShell 7.4.0 on Windows 11 22H2\r\n```\r\n\r\n\r\n### Visuals\r\n\r\n_No response_","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2023-12-11T19:27:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/20898/PowerShell/issues/20898"}