From: cgf AT bbc DOT com (Christopher Faylor)
Subject: Re: -@file
1 Apr 1998 05:55:50 -0800
Message-ID: <EqqLvK.232.cygnus.cygwin32.developers@bbc.com>
References: <m1d8f2tica DOT fsf AT creche DOT cygnus DOT com>
Reply-To: cgf AT bbc DOT com
To: cygwin32-developers AT cygnus DOT com

In article <3 DOT 0 DOT 5 DOT 32 DOT 19980401015746 DOT 00965430 AT pop DOT cygnus DOT com>,
Eric Bachalo  <ebachalo AT cygnus DOT com> wrote:
>At 06:56 PM 3/31/98 -0700, Tom Tromey wrote:
>>However, there is a bug in insert_files().  It doesn't properly
>>respect the quoting style defined by build_argv().  For instance, this
>>string will be misinterpreted as a request for file insertion (the
>>quotes are part of the string):
>>
>>	" -@file"
>>
>>I think it's important to respect this quoting style, because it is
>>the same quoting style used by spawn_guts().
>>
>>Tom
>
>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'.

Btw, does -con work?  That would allow a user to type in an arbitrarily long
string from the command line.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."