Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Thu, 3 May 2001 13:44:54 -0400 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: Problem with Windows .lnk files treated as Symlinks Message-ID: <20010503134454.D5353@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: <549191FE7B71D311BC5900104B292132010E4F8C@kirk.takefive.co. at> <4.3.1.2.20010503104233.02700c48@pop.ma.ultranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.1.2.20010503104233.02700c48@pop.ma.ultranet.com>; from lhall@rfk.com on Thu, May 03, 2001 at 10:48:05AM -0400 On Thu, May 03, 2001 at 10:48:05AM -0400, Larry Hall (RFK Partners, Inc) wrote: >>2.) If CYGWIN=nowinsymlinks is set, not only symbolic link >> creation but also symbolic link interpretation should >> be "classical", i.e. *.lnk files are treated as files. > >This may be indicative of a bug. This isn't a bug. The setting is only to force creation of old style symlinks. Either style is supposed to be recognized on "reading". I suppose the option could have been "nocreatewinsymlinks"... cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple