{"version":"2.1.233","anchor":"windows-bash-argument-scanning-sees-through-flag-value-and-n","canonical_anchor":"windows-bash-argument-scanning-sees-through-flag-value-and-n","heading":"Windows Bash argument scanning sees through --flag=value and NT device paths","tier":"notice","area":"Windows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/windows-bash-argument-scanning-sees-through-flag-value-and-n","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Windows Bash argument scanning sees through `--flag=value` and NT device paths\n\nWindows command scanning now unwraps flag=value arguments and spots NT object-manager paths.\n\n**What**\n\nOn Windows, the check that spots network and device paths in Bash command arguments now strips `--flag=` and `-f=` prefixes repeatedly and re-checks what is left, and recognises `\\??\\` NT object-manager paths. Off entirely on other platforms.\n\n**Details**\n\n- Path checks in Read, Edit and NotebookEdit, plus the file-path display component, moved from ad-hoc `\\\\` \/ `\/\/` prefix tests to shared helpers that also cover `\/net\/<host>` autofs paths.\n- NotebookEdit lost its shortcut that accepted UNC paths without further checks, so those paths now go through the `.ipynb` extension check like any other.\n\n**Evidence**\n\n`WAd = \/^--?[A-Za-z0-9][\\w-]*=\/`\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}