From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: WSL symbolic links
Date: Fri, 27 Mar 2020 06:46:01 +0100 [thread overview]
Message-ID: <87y2rmfizq.fsf@Otto.invalid> (raw)
In-Reply-To: <8e330046-97bb-ba3e-15dc-25aedf915d90@towo.net> (Thomas Wolff's message of "Fri, 27 Mar 2020 00:52:17 +0100")
Thomas Wolff writes:
>> - Last but not least, could you please create a symlink pointing to a
>> target with a non-ASCII char, e. g., some german umlaut?
> Not sure what kind of remote you'd like to see. I have a 'net use'
> (cifs/smbfs) mounted drive but couldn't mount it in WSL. Otherwise:
That's exactly why WSL is so nearly useless to me and why Cygwin
continues to hold its place.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2020-03-27 5:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:00 Thomas Wolff
2020-03-26 11:00 ` Corinna Vinschen
2020-03-26 16:15 ` Thomas Wolff
2020-03-26 19:12 ` Brian Inglis
2020-03-26 19:56 ` Corinna Vinschen
2020-03-26 23:52 ` Thomas Wolff
2020-03-27 5:46 ` ASSI [this message]
2020-03-27 11:21 ` Corinna Vinschen
2020-03-27 12:24 ` Thomas Wolff
2020-03-27 13:01 ` Corinna Vinschen
2020-03-27 14:43 ` Thomas Wolff
2020-03-26 20:05 ` Corinna Vinschen
2020-03-27 17:58 ` Brian Inglis
2020-03-27 18:53 ` Corinna Vinschen
2020-03-28 3:32 ` Brian Inglis
2020-03-28 10:31 ` Henry S. Thompson
2020-03-28 11:30 ` Thomas Wolff
2020-03-28 11:59 ` Andrey Repin
2020-03-28 20:45 ` Brian Inglis
2020-03-29 11:52 ` Andrey Repin
2020-03-30 8:46 ` Corinna Vinschen
2020-04-04 14:32 ` Denis Excoffier
2020-04-05 15:22 ` 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=87y2rmfizq.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).