Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 28 Feb 2001 18:32:19 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: New symlinks. Message-ID: <20010228183219.A5603@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <17B78BDF120BD411B70100500422FC6309E21C AT IIS000> <20010228135244 DOT I8464 AT cygbert DOT vinschen DOT de> <20010228110624 DOT B2327 AT redhat DOT com> <006a01c0a1cd$1d6156e0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <006a01c0a1cd$1d6156e0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Thu, Mar 01, 2001 at 08:26:27AM +1100 On Thu, Mar 01, 2001 at 08:26:27AM +1100, Robert Collins wrote: >>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 :-) > >If they are using cygwin I think a certain amount of adaptation _is >required_. We're not trying to build a new friendly GUI, we're trying >to take one of the most flexible computing environments and put it on >one of the least :] We're also taking a step backwards "Symlinks used to work in 1.1.8 but now all of my symlinks have a .lnk extension. How do I get rid of that?" Am I the only person who reads this mailing list regularly? I can't believe that anyone could seriously put forth an argument of "a certain amount of adaptation is required". For one thing, we have repeatedly seen that every time we do diverge from UNIX (e.g., textmode/binmode) people will complain about it and spend a lot of time offering "new" "ideas" for how things could be improved. The other thing is that I try extremely hard to limit the amount of adaptation that a user must endure to use Cygwin. I'm really not comfortable adding another incompatibility. >> >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. > >And Microsoft have been publicly slammed by the security community on >this and a number of related actions because of the reduction in user >environment awareness. Are the people using Windows aware of this public slamming? I was discussing this issue with someone who works on Windows today and he was enthusiastic about using Windows links. I mentioned that these links have a ".lnk" extension and he said "They do? I didn't know that." The bottom line is I don't care a fig about what is "correct". I'm concerned about surprising people. I'm not concerned about exposing the ".lnk" for power users if it causes confusion for the vast majority of people who are not power users. I'm concerned about increasing mailing list traffic by 10% when it could be avoided. >My vote: we expose the.lnk at at least one place in the interface. We >also make it interoperate seamlessly for scripts/batch files etc. I'm not sure what "interoperate seamlessly" means. It would be nice if people would try what Corinna has implemented before offering opinions. Or, maybe you have done this and are just reiterating Corinna's implementation. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple