From: ebachalo AT cygnus DOT com (Eric Bachalo) Subject: Re: -@file 1 Apr 1998 12:01:33 -0800 Message-ID: <3.0.5.32.19980401114818.009ca480.cygnus.cygwin32.developers@pop.cygnus.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: cgf AT bbc DOT com, cygwin32-developers AT cygnus DOT com At 01:38 PM 4/1/98 GMT, Christopher Faylor wrote: > >>I did it on purpose because I thought is might be useful to be able to >>stick long quoted strings in a file. Don't know of any instance one needs >>a long or often used quote in a command line though. >> >>Instead of " -@file" one could type " \-@file" and get the response you >>wish. If being able to stick a file within quotes is not useful and if >>people believe insert_file should respect quotes then I (or anyone wishing >>to volunteer) will change the logic. > >I think it's counterintuitive for " -@file" to be interpreted as an >"option". Usually options begin with a '-', but in this special case an >option begins with a ' -', which is not what you usually expect. > >I think that if someone wants a long quoted string, they should put the >string in 'file'. See response to Tom. No problem if someone wants to change it. > >Btw, does -con work? That would allow a user to type in an arbitrarily long >string from the command line. -@con does not work in current implementation. Sorry. I think we should realize that this functionality was basically added for people using the command.com under Win95 so I tried to keep it as simple as possible so as not to unnecessarily clutter the code. But if this feature is believed to be of some value for general use and more than just the Win95 people use it than I am more willing to have it done right. I agree that it does not work as one would expect with quotes. Best Regards, Eric Bachalo