[PATCH v2 2/2] Allow executing Windows Store's "app execution aliases"

The Windows Store version of Python (and apparently other Windows Store applications) install a special reparse point called "app execution alias" into the user's `PATH`. These applications can be executed without any problem, but they cannot be read as if they were files. This trips up Cygwin's b

[PATCH v2 1/2] Treat Windows Store's "app execution aliases" as symbolic links

When the Windows Store version of Python is installed, so-called "app execution aliases" are put into the `PATH`. These are reparse points under the hood, with an undocumented format. We do know a bit about this format, though, as per the excellent analysis: https://www.tiraniddo.dev/2019/09/overv

[PATCH v2 0/2] Handle "app execution aliases"

When installing e.g. Python via the Windows Store, it is common that the `python3.exe` entry in the `PATH` is not actually an executable at all, but an "app executaion alias" (i.e. a special class of reparse point). These filesystem entries are presented as 0-size files, but they are not readable,

Re: [PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

Hi Hans-Bernhard, On Mon, 15 Mar 2021, Hans-Bernhard Bröker wrote: > Am 15.03.2021 um 04:19 schrieb Johannes Schindelin via Cygwin-patches: > > > On Sat, 13 Mar 2021, Joe Lowe wrote: > > > > > I agree on the usefulness to the user of showing appexec target > > &g

Re: [PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

But for the common case of reading the corresponding `.exe` or accessing > > the path? Why should we follow your suggestion and keep making it really > > hard for users to get to that information? I really don't get it. > > > > Ciao, > > Johannes > > > > > > > >

Re: [PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

> > > The patch part 2 seems entirely appropriate. > > > Joe L. > > > On 2021-03-12 07:11, Johannes Schindelin via Cygwin-patches wrote: > > When the Windows Store version of Python is installed, so-called "app > > execution aliases" are put into the `PATH`.

[PATCH 2/2] Allow executing Windows Store's "app execution aliases"

The Windows Store version of Python (and apparently other Windows Store applications) install a special reparse point called "app execution alias" into the user's `PATH`. These applications can be executed without any problem, but they cannot be read as if they were files. This trips up Cygwin's b

[PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links

When the Windows Store version of Python is installed, so-called "app execution aliases" are put into the `PATH`. These are reparse points under the hood, with an undocumented format. We do know a bit about this format, though, as per the excellent analysis: https://www.tiraniddo.dev/2019/09/overv

[PATCH 0/2] Handle "app execution aliases"

When installing e.g. Python via the Windows Store, it is common that the `python3.exe` entry in the `PATH` is not actually an executable at all, but an "app executaion alias" (i.e. a special class of reparse point). These filesystem entries are presented as 0-size files, but they are not readable,