From: Gionatan Danti <g.danti@assyoma.it>
To: Gionatan Danti <g.danti@assyoma.it>,
Brian Inglis <Brian.Inglis@shaw.ca>,
cygwin@cygwin.com
Subject: Re: Can not stat file with utf char U+F020
Date: Fri, 14 Apr 2023 22:51:11 +0200 [thread overview]
Message-ID: <ba57420fb8184222cbe2889e2617b4fe@assyoma.it> (raw)
In-Reply-To: <ZDm6IurD9ykLOoSv@calimero.vinschen.de>
Il 2023-04-14 22:40 Corinna Vinschen ha scritto:
> This is really tricky. A new mount point flag could be used to
> override
> this behaviour on a per path basis. One problem is, the unicode ->
> multibyte conversion when evaluating a symlink is done before it's
> clear
> where the symlink target is. Only the string is converted and it might
> be a relative path, so the code doesn't know where the target ends up.
> And that's probably not all.
To tell the truth, it is such a corner (and infortunate) case that I
would not care if the workaround does not work for symlinks.
> Is it really worth to add code to support a long deprecated Windows
> service?
Yeah, I understand your point. I am not in the position to evaluate if
it would be worth.
Maybe a special case for only U+F020 (the most common "strange" char I
see) can be considered?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2023-04-14 20:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 17:53 Gionatan Danti
2023-04-14 19:00 ` Corinna Vinschen
2023-04-14 19:54 ` Brian Inglis
2023-04-14 20:20 ` Corinna Vinschen
2023-04-14 20:21 ` Gionatan Danti
2023-04-14 20:25 ` Corinna Vinschen
2023-04-14 21:01 ` Gionatan Danti
2023-04-17 5:36 ` Gionatan Danti
2023-04-17 9:05 ` Corinna Vinschen
2023-04-17 10:58 ` Andrey Repin
2023-04-17 13:46 ` Gionatan Danti
2023-04-18 21:09 ` Gionatan Danti
2023-04-19 1:10 ` L A Walsh
2023-04-19 11:56 ` Gionatan Danti
2023-04-14 20:17 ` Gionatan Danti
2023-04-14 20:40 ` Corinna Vinschen
2023-04-14 20:51 ` Gionatan Danti [this message]
2023-04-15 5:10 ` Brian Inglis
2023-04-17 9:10 ` 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=ba57420fb8184222cbe2889e2617b4fe@assyoma.it \
--to=g.danti@assyoma.it \
--cc=Brian.Inglis@shaw.ca \
--cc=cygwin@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).