On Fri, Aug 08, 2008 at 02:47:43PM -0500, Tim McDaniel wrote:
> On Fri, 8 Aug 2008, Christopher Faylor
> <[EMAIL PROTECTED]> wrote:
>> On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote:
>>> That's most unpleasant. I don't suppose there's any way to control
>>> Cygwin's bash in re where
On Fri, Aug 08, 2008 at 03:29:48PM -0400, Christopher Faylor wrote:
>On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote:
>>That's most unpleasant. I don't suppose there's any way to control
>>Cygwin's bash in re where to put double quotes around arguments being
>>passed to a Windows comm
On Fri, Aug 8, 2008 at 15:47, Tim McDaniel wrote:
> On Fri, 8 Aug 2008, Christopher Faylor
> <[EMAIL PROTECTED]> wrote:
>>
>> On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote:
>>>
>>> That's most unpleasant. I don't suppose there's any way to control
>>> Cygwin's bash in re where to p
On Fri, 8 Aug 2008, Christopher Faylor <[EMAIL PROTECTED]> wrote:
On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote:
That's most unpleasant. I don't suppose there's any way to control
Cygwin's bash in re where to put double quotes around arguments
being passed to a Windows command (s
On Fri, Aug 08, 2008 at 01:58:12PM -0500, Tim McDaniel wrote:
>That's most unpleasant. I don't suppose there's any way to control
>Cygwin's bash in re where to put double quotes around arguments being
>passed to a Windows command (since getting Microsoft to make
>explorer.exe be sane is hopeless)?
On Fri, 8 Aug 2008, Lev Bishop <[EMAIL PROTECTED]> wrote:
On Fri, Aug 8, 2008 at 12:28, Christopher Faylor wrote:
Is there any documentation on who rewrites arguments, under what
conditions, and how they're altered?
I missed this when it was first mentioned.
I've skipped parts of this thre
On Fri, Aug 08, 2008 at 01:39:49PM -0400, Lev Bishop wrote:
>On Fri, Aug 8, 2008 at 12:28, Christopher Faylor wrote:
>
>>> Is there any documentation on who rewrites arguments, under what
>>> conditions, and how they're altered?
>>
>> I missed this when it was first mentioned. Cygwin doesn't mung
On Fri, Aug 8, 2008 at 12:28, Christopher Faylor wrote:
>> Is there any documentation on who rewrites arguments, under what
>> conditions, and how they're altered?
>
> I missed this when it was first mentioned. Cygwin doesn't munge command
> line arguments. Why would it assume that /e,something
On Fri, Aug 08, 2008 at 10:16:57AM -0500, Tim McDaniel wrote:
> On Fri, 8 Aug 2008, Luke Kendall wrote:
>> On 4 Aug, Gary R. Van Sickle wrote:
>>> explorer /e,$XPATH & disown %-
>>
>> Don't try this variant, though, since it doesn't work:
>>
>>explorer /e,"$XPATH" & disown %-
>>
>> What ha
On Fri, 8 Aug 2008, Luke Kendall wrote:
On 4 Aug, Gary R. Van Sickle wrote:
explorer /e,$XPATH & disown %-
Don't try this variant, though, since it doesn't work:
explorer /e,"$XPATH" & disown %-
What happens if you try that innocuous-looking variant is that
Cygwin (or bash?) norm
On Fri, Aug 8, 2008 at 02:41, Luke Kendall wrote:
> Don't try this variant, though, since it doesn't work:
>
>explorer /e,"$XPATH" & disown %-
>
> What happens if you try that innocuous-looking variant is that Cygwin
> (or bash?) normalises the path /e,... to a windows path first, producing
>
On 4 Aug, Gary R. Van Sickle wrote:
> Hi Luke,
>
> > I discovered today that if I try to run Windows Explorer from
> > the Cygwin command line, and give it a pathname with spaces,
> > it fails, but if I give the same command line to a cmd.exe
> > command line, Explorer works!
> >
> > I.e. f
On 4 Aug, Buchbinder, Barry (NIH/NIAID) [E] wrote:
> Luke Kendall wrote on Monday, August 04, 2008 4:18 AM:
>
> > I discovered today that if I try to run Windows Explorer from the
> > Cygwin command line, and give it a pathname with spaces, it fails,
> > but if I give the same command line to a
Hi Luke,
> I discovered today that if I try to run Windows Explorer from
> the Cygwin command line, and give it a pathname with spaces,
> it fails, but if I give the same command line to a cmd.exe
> command line, Explorer works!
>
> I.e. from Bash, explorer fails with an error message like
>
Luke Kendall wrote on Monday, August 04, 2008 4:18 AM:
> I discovered today that if I try to run Windows Explorer from the
> Cygwin command line, and give it a pathname with spaces, it fails,
> but if I give the same command line to a cmd.exe command line,
> Explorer works!
>
> I.e. from Bash,
On Mon, Aug 4, 2008 at 04:18, Luke Kendall wrote:
>$ explorer /e,c:\\temp\\space\ dir
>$ # NBG^
>$ explorer /e,c:\\temp
>$ # GOOD^
>$ explorer c:\\temp\\space\ dir
>$ # GOOD^ (but no side pane)
>$ explorer /e,"c:\temp\space dir"
>$ # NBG^
>$ explorer /e,"\"c:\te
I discovered today that if I try to run Windows Explorer from the Cygwin
command line, and give it a pathname with spaces, it fails, but if I
give the same command line to a cmd.exe command line, Explorer works!
I.e. from Bash, explorer fails with an error message like
"The path '/e,c:\temp\space
17 matches
Mail list logo
