More strange behavior when running Cygwin apps from a Windows prompt. The
quoting seems not to follow any rules that I can manage to track down:
The following are normal and expected, given that we discovered that all Cygwin
apps do some kind of as-yet-undefined partial bash preprocessing on th
--- On Wed, 9/9/09, Christopher Faylor
wrote:
> From: Christopher Faylor
> Subject: Re: syntax for Cygwin bash invoking Win apps
> To: cygwin@cygwin.com
> Date: Wednesday, September 9, 2009, 12:45 PM
> On Wed, Sep 09, 2009 at 12:10:44PM
> -0400, Mark J. Reed wrote:
> >On Wed, Sep 9, 2009 at 12:
--- On Wed, 9/9/09, Mark J. Reed wrote:
> From: Mark J. Reed
> Subject: Re: syntax for Cygwin bash invoking Win apps
> To: cygwin@cygwin.com
> Date: Wednesday, September 9, 2009, 11:10 AM
> On Wed, Sep 9, 2009 at 12:05 PM,
> Christopher Faylor wrote:
> > $ cmd /c echo "\"abc\""
> > "\"ab
>On Tue, Sep 8, 2009 at 11:30 PM, Ziser, Jesse wrote:
>> Hello list,
>>
>> When I type a command in bash to invoke a Windows application (like cmd.exe,
>> for example), I can't seem to find a pattern in the Windows command line that
>> actually gets executed.
>On 09/08/2009 11:30 PM, Ziser, Jesse wrote:
>> Hello list,
>>
>> When I type a command in bash to invoke a Windows application (like
>> cmd.exe, for example), I can't seem to find a pattern in the Windows command
>> line that actually gets executed. Ordinary
Hello list,
When I type a command in bash to invoke a Windows application (like cmd.exe,
for example), I can't seem to find a pattern in the Windows command line that
actually gets executed. Ordinary bash syntax does not seem to apply in general
when the command is a Windows app, but rather, s
6 matches
Mail list logo