X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:message-id:date:to:subject:from; q=
	dns; s=default; b=iJvzG0naKhEVa90XJyqpLORzPzKyJdTJi5JfvTyESonmPs
	+hKa+nl1YIevGdPd2wv3mLtN0SHxLxiXqpZw8ewf9MB9hlN3XbF20Rn7kVLnzBnC
	aE7nTKEv7yZUQJMH6BB8lszaHz3LyOUD5901fVCWGa147Q8A/waFQDKh4yJ8Q=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:message-id:date:to:subject:from; s=
	default; bh=xhkmWINf6vnZ5kZn9cTtyPOvoG4=; b=BDHMb4/cu2yhCQfoUwpJ
	mk+u59mLedLkWALuQkN+V6ej7M/FbbogVtbQHrYWRLcSuiMZkhVcg457FpePgwDB
	iyF8QorHXcw2vdcaCTNLl2XbujhF68YXRhhqdQksx9UQlCTC6B2SO8NEif9ahCbe
	fFc+dE789IFYdi8a3LxPjGw=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.0 required=5.0 tests=AWL,BAYES_00,FROM_BLANK_NAME,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.1 spammy=privileges, indeed
X-HELO:	p3plsmtpa11-08.prod.phx3.secureserver.net
X-Sender:	inbox AT kosowsky DOT org
MIME-Version:	1.0
Message-ID:	<24070.7571.896562.93733@consult.pretender>
Date:	Fri, 27 Dec 2019 10:04:51 -0500
To:	cygwin AT cygwin DOT com
Subject:	Any downside to using winsymlinks over cygwin-style symlinks?
From:	"" <cygwin AT kosowsky DOT org>
X-IsSubscribed:	yes

Based on the documentation and practical use of the Windows-style
symlinks (winsymlinks) vs Cygwin-style symlinks, it seems to me that:
1. Winsymlinks have the advantage of working as symlinks/shortcuts
   under both Cygwin and Windows Explorer while Cygwin links are
   recognized only in Cygwin

2. They both are basically text files with some MAGIC numbers and
   attributes that allow them to be interpreted as symlinks

So, is there any *disadvantage* to always using Winsymlinks and indeed
converting my old Cygwin-style links to Windows-style?

(Note: I can't use Windows Native symlinks because I don't have admin
privileges on all my machines)

Finally, where is the best place to set CYGWIN=winsymlinks?
In .bash_profile?

Thanks!
Jeff

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -