From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 1/2] Treat Windows Store's "app execution aliases" as symbolic links
Date: Mon, 15 Mar 2021 20:04:23 +0100 [thread overview]
Message-ID: <69dc492e-cce9-1a1a-7d4b-92a58dbfe981@t-online.de> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2103150408230.50@tvgsbejvaqbjf.bet>
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 effect of not being able to do
> anything useful with app execution aliases in the first place.
That argument might hold more sway if Windows itself didn't quite so
completely hide that information from users, too.
I found only one Windows native tool that will even show _any_ kind of
information about these reparse points: fsutil. That is a) only
available as part of the highly optional WSL feature and b) only gives
you a hexdump of the actual data, without any meaningful interpretation.
For something that Windows itself gives the "no user servicable parts
inside" treatment to the extent it does for these reparse points, I
rather doubt that Cygwin users really _need_ to see it.
next prev parent reply other threads:[~2021-03-15 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:11 Johannes Schindelin
2021-03-12 17:03 ` Joe Lowe
2021-03-14 0:21 ` Johannes Schindelin
2021-03-14 3:41 ` Joe Lowe
2021-03-15 3:19 ` Johannes Schindelin
2021-03-15 19:04 ` Hans-Bernhard Bröker [this message]
2021-03-22 15:22 ` Johannes Schindelin
2021-03-22 21:54 ` Hans-Bernhard Bröker
2021-03-23 9:30 ` Corinna Vinschen
2021-03-24 18:55 ` Hans-Bernhard Bröker
2021-03-24 20:58 ` Ken Brown
2021-03-26 1:29 ` Hans-Bernhard Bröker
2021-03-15 10:17 ` Corinna Vinschen
2021-03-15 19:52 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69dc492e-cce9-1a1a-7d4b-92a58dbfe981@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin-patches@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).