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, Sep 9, 2009 at 2:20 PM, Ziser, Jesse wrote:
> --- On Wed, 9/9/09, Christopher Faylor [...] wrote:
>From: [...]
Please don't quote email addresses and message headers.
> OK, yeah, I now see that is basically what's going on.
> Bash is processing it as normal and then Cygwin is adding all k
--- 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:
> >O
On Wed, Sep 09, 2009 at 12:10:44PM -0400, Mark J. Reed wrote:
>On Wed, Sep 9, 2009 at 12:05 PM, Christopher Faylor wrote:
>> $ cmd /c echo "\"abc\""
>> "\"abc\""
>>
>> # Wahhh?!
>>
>> Anyone who knows the explanation would make me very grateful. I've tried
>> this with o
--- 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:
> >&
On Wed, Sep 9, 2009 at 12:05 PM, Christopher Faylor wrote:
> $ cmd /c echo "\"abc\""
> "\"abc\""
>
> # Wahhh?!
>
> Anyone who knows the explanation would make me very grateful. I've tried
> this with other Windows apps too, and the same weirdness seems to occur.
>>
>>Lar
On 09/09/2009 11:27 AM, Ziser, Jesse wrote:
Huh? Last time I checked, bash translates "\"abc\"" to "abc".
Yeah, I don't know what test I did last night that made me think this was
right for
bash. The lesson here is that I shouldn't try a bunch of tests quickly late
at night. ;-)
Doe
On Wed, Sep 09, 2009 at 11:56:54AM -0400, Mark J. Reed wrote:
>On Wed, Sep 9, 2009 at 11:27 AM, Ziser, Jesse wrote:
$ cmd /c echo "\"abc\""
"\"abc\""
# Wahhh?!
Anyone who knows the explanation would make me very grateful. I've tried
this with other Windows apps to
>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. Ordinary bash syntax does not seem to
On Wed, Sep 9, 2009 at 11:27 AM, Ziser, Jesse wrote:
>>> $ cmd /c echo "\"abc\""
>>> "\"abc\""
>>>
>>> # Wahhh?!
>>>
>>> Anyone who knows the explanation would make me very grateful. I've tried
>>> this with other Windows apps too, and the same weirdness seems to occur.
Larry Hall:
>>All of the ab
>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 bash syntax does not seem to
>> apply i
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 bash syntax does not seem to
apply in general when t
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. Ordinary bash syntax does not seem to apply
13 matches
Mail list logo
