Am 24.03.2021 um 21:58 schrieb Ken Brown:
On 3/24/2021 2:55 PM, Hans-Bernhard Bröker wrote:
Am 23.03.2021 um 10:30 schrieb Corinna Vinschen via Cygwin-patches:
> On Mar 22 22:54, Hans-Bernhard Bröker wrote:
>> Am 22.03.2021 um 16:22 schrieb Johannes Schindelin:
It's what WSL Debian creates
On 3/24/2021 2:55 PM, Hans-Bernhard Bröker wrote:
Am 23.03.2021 um 10:30 schrieb Corinna Vinschen via Cygwin-patches:
> On Mar 22 22:54, Hans-Bernhard Bröker wrote:
>> Am 22.03.2021 um 16:22 schrieb Johannes Schindelin:
>>> One of those under-documented reparse point types is the WSL symbolic
Am 23.03.2021 um 10:30 schrieb Corinna Vinschen via Cygwin-patches:
> On Mar 22 22:54, Hans-Bernhard Bröker wrote:
>> Am 22.03.2021 um 16:22 schrieb Johannes Schindelin:
>>> One of those under-documented reparse point types is the WSL symbolic
>>> link, which you will notice are supported in
On Mar 22 22:54, Hans-Bernhard Bröker wrote:
> Am 22.03.2021 um 16:22 schrieb Johannes Schindelin:
> > One of those under-documented reparse point types is the WSL symbolic
> > link, which you will notice are supported in Cygwin, removing quite some
> > sway from your argument...
>
> I notice no
Am 22.03.2021 um 16:22 schrieb Johannes Schindelin:
On Mon, 15 Mar 2021, Hans-Bernhard Bröker wrote:
Am 15.03.2021 um 04:19 schrieb Johannes Schindelin via Cygwin-patches:
That argument might hold more sway if Windows itself didn't quite so
completely hide that information from users, too.
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
> > > executable as symlink target. But
Hi Johannes,
I'm not opposed to treat these applinks as symlinks. I have a
suggestion and a style nit, though.
On Mar 12 16: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`.
Am 15.03.2021 um 04:19 schrieb Johannes Schindelin via Cygwin-patches:
Hi Joe,
On Sat, 13 Mar 2021, Joe Lowe wrote:
I agree on the usefulness to the user of showing appexec target executable as
symlink target. But I am uncertain about the effect on code.
Maybe. But I am concerned about the
Hi Joe,
On Sat, 13 Mar 2021, Joe Lowe wrote:
> I agree on the usefulness to the user of showing appexec target executable as
> symlink target. But I am uncertain about the effect on code.
Maybe. But I am concerned about the effect of not being able to do
anything useful with app execution
On Mar 13 19:41, Joe Lowe via Cygwin-patches wrote:
> Hi Johannes,
>
> I agree on the usefulness to the user of showing appexec target executable
> as symlink target. But I am uncertain about the effect on code.
>
> One example: Any app that is able to archive/copy posix symlinks will
> convert
Hi Johannes,
I agree on the usefulness to the user of showing appexec target
executable as symlink target. But I am uncertain about the effect on code.
One example: Any app that is able to archive/copy posix symlinks will
convert the appexec to a symlink and silently drop the appexec data.
Hi Joe,
On Fri, 12 Mar 2021, Joe Lowe wrote:
> I am skeptical about this patch (part 1), interposing appexec reparse point
> data as symlinks for cygwin applications.
>
> The appexec reparse point data is essentially an extended attribute holding
> data that is used by CreateProcess(), more like
I am skeptical about this patch (part 1), interposing appexec reparse
point data as symlinks for cygwin applications.
The appexec reparse point data is essentially an extended attribute
holding data that is used by CreateProcess(), more like a windows .lnk
file or an X11 .desktop file, not
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:
14 matches
Mail list logo