From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Jan Hlavacek <jhlavace@svsu.edu>
Subject: Re: odd behavior of symlinks on Win XP
Date: Fri, 28 Jan 2005 11:09:00 -0000 [thread overview]
Message-ID: <20050128090156.GB25553@cygbert.vinschen.de> (raw)
In-Reply-To: <s1f8f7f1.045@gw.svsu.edu>
On Jan 27 14:16, Jan Hlavacek wrote:
> I am not on the list, but I hope this will get through. I came across
> this discussion while I was searching for an answer to similar problem.
There are a couple of postings in the ML archives, all from this month,
which should explain the behaviour pretty well. There's a patch in
current Cygwin CVS which should solve the icon problem. But as soon as
you change the icon, the shortcut is changed by Windows in a way which
invalidates it as symlink for Cygwin. That's nothing we can change
without breaking other things. If you want to use a shortcut in Cygwin
and in native Windows, create it in Cygwin and don't touch it.
> [FAQ]
> Since version 1.3.0, Cygwin treats shortcuts as symlinks. "
I'll change the text in the FAQ.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-01-28 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 21:45 Jan Hlavacek
2005-01-28 11:09 ` Corinna Vinschen [this message]
[not found] <corinna-cygwin@cygwin.com>
2005-01-31 21:15 ` Jeff.Hodges
2005-02-01 19:43 ` Jeff.Hodges
2005-02-01 20:48 ` Christopher Faylor
[not found] <cgf-no-personal-reply-please@cygwin.com>
2005-02-06 6:50 ` Jeff.Hodges
2005-02-06 8:07 ` Jeff.Hodges
2005-02-06 9:39 ` Igor Pechtchanski
2005-02-06 15:12 ` Gary R. Van Sickle
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=20050128090156.GB25553@cygbert.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=jhlavace@svsu.edu \
/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).