Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: Cygwin List Subject: Re: ln and mkshortcut inconsistent in handling of .exe extension References: <5.1.0.14.0.20030929161708.028d6fe0@127.0.0.1> From: Matt Swift Date: Mon, 29 Sep 2003 18:02:50 -0400 In-Reply-To: <5.1.0.14.0.20030929161708.028d6fe0@127.0.0.1> (Larry Hall's message of "Mon, 29 Sep 2003 16:20:23 -0400") Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Transfinites-MailScanner: clean X-Transfinites-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.9, required 5, BAYES_00 -4.90) Note-from-DJ: This may be spam >> "L" == Larry wrote: L> 'ln' and 'mkshortcut' have different behavior for a reason. See L> . L> The difference is why 'mkshortcut' exists. Otherwise, we'd just have L> 'ln' (which is all we had for quite some time until the need for L> different behavior was realized). I had seen that discussion. I found no discussion of the particular interaction of shortcuts/symlinks and the special handling of the .exe extension. To predict the results of the commands I listed, I had to experiment. Second, I still don't understand why `ln' shouldn't behave the way I suggested: how is it better the way it is than if `ln -s' never created broken shortcuts and 'ln' (hardlink) defaulted to a target of "foo.exe" when the supplied target "foo" doesn't exist? -- 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/