Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<17B78BDF120BD411B70100500422FC6309E220@IIS000>
From:	Bernard Dautrevaux <Dautrevaux AT microprocess DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: New symlinks.
Date:	Wed, 28 Feb 2001 17:58:32 +0100
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)
Note-from-DJ:	This may be spam

> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com]
> Sent: Wednesday, February 28, 2001 5:06 PM
> To: Cygwin
> Subject: Re: New symlinks.
> 
> 
> On Wed, Feb 28, 2001 at 01:52:44PM +0100, Corinna Vinschen wrote:
> >> another icon ;^). Don't underestimate people using 
> Windows; most of them are
> >> not idiots and are used to Windows idiosyncrasisms, so 
> when using cygwin
> >> they can adapt :-)
> >
> >I wonder...
> >
> >*restrain sarcasm*
> >
> >...anyway, you may be right here ;-)
> 
> I HEARTILY disagree with this.  We have repeatedly see the 
> confusion of people
> on this mailing list on all matter of subjects.  I have no 
> reason to assume that
> having files with a .lnk extension will be any different -- 
> especially since
> Microsoft goes out of its way to hide the extension itself.

People that only use the Windows GUI would be confused by the ".lnk"
extension if shown by cygwin, but as we don't show it by default there's no
problem. OTOH people used to CMD.exe will be used to the lnk suffix (as DIR
shows it) but should understand that cygwin is doing the same as Explorer,
and hide it.

So I don't think there will be so much confusion. In fact th econfusion
caused by ".lnk" should be less than the one caused by ".exe", as it is more
consistent: there's not this 
	$ if [ -r xxx ]; then cp xxx yyy; fi
	cp: xxx: No such file of directory
due to test finding xxx.exe but cp searching only xxx, not xxx.exe. With
symlinks as they are now this will work OK. So if someone is able to
understand the .exe stuff, they should have no problem with  .lnk :-).

Regards,

	Bernard
 
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux AT microprocess DOT com
		b DOT dautrevaux AT usa DOT net
-------------------------------------------- 

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -