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=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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>

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