Overview
| Artifact ID: | 7e5e93eeeb382b73c261546ca8222423dc643fa1cf3edc44218c644508791657 |
|---|---|
| Ticket: | 4f0b5767acbec00396762e6a3a6d10f59d2be778
exec does not handle app execution aliases on Windows |
| User & Date: | apnadkarni 2025-01-26 03:20:15 |
Changes
- assignee changed to: "nobody"
- closer changed to: "nobody"
- cmimetype changed to: "text/x-markdown"
- comment changed to:
Reported by Julian Noble on the chat: ``` JulianNoble › exec is not so nice on windows.. some modern apps seem to be installed as reparse points - which tcl doesn't seem to handle [22:08] JulianNoble › winget being a notable example ``` Google shows Tcl is not the only one suffering from this. See [here](https://stackoverflow.com/questions/77926324/how-to-select-app-execution-reparse-points-in-qfiledialog), [here](https://stackoverflow.com/questions/60421250/windows-10-user-unable-to-execute-appexeclink-reparse-point-exe-files) or [here](https://stackoverflow.com/questions/62474046/how-do-i-find-the-target-of-a-windows-app-execution-alias-in-c-win32-api) for example.
- is_private changed to: "0"
- login: "apnadkarni"
- priority changed to: "5 Medium"
- private_contact changed to: "9546e9877f1a8899e25a89082561ee694e7fb402"
- resolution changed to: "None"
- severity changed to: "Important"
- status changed to: "Open"
- submitter changed to: "apnadkarni"
- subsystem changed to: "- New Builtin Commands"
- title changed to:
exec does not handle app execution aliases on Windows
- type changed to: "Bug"