On Thu, 27 Feb 2003, Curtis Siemens wrote:
How To Reproduce:
-
Install Cygwin under c:\ or c:\cygwin - some directory that doesn't
NEVER DO THAT!
see http://cygwin.com/faq/faq_2.html#SEC9
rlc
--
Unsubscribe info:
- Original Message -
From: Ronald Landheer-Cieslak [EMAIL PROTECTED]
To: Curtis Siemens [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, February 28, 2003 9:05 PM
Subject: Re: bash's (built-in) type command can not handle spaces in paths
On Thu, 27 Feb 2003, Curtis Siemens wrote:
Thanks for the responses. I managed to narrow down what's different
in my situation. Basically the bash builtin type command does work
fine with paths that contain spaces.
The problem is a side effect of using NTFS and accidentally banging my
head into NT's horrible over complicated/complex
On Fri, Feb 28, 2003 at 04:42:53PM -0800, Curtis Siemens wrote:
By the way, given that I can actually run an executable that bash/type
can't find, does this suggest that possibly the builtin type command
is doing something wrong?
Yes and no. Obviously it isn't working as it should. But in
On Fri, Feb 28, 2003 at 10:14:48PM -0500, Pierre A. Humblet wrote:
The problem is being addressed and will be solved perfectly (time will tell !)
soon.
Hmm. TPIBA.
I like it.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:
My platform is Windows 2000 (with all the latest patches). This problem
probably occurs on a number of Windows platforms. I'm using the latest
released Cygwin with Cygwin DLL release version 1.3.20-1
I've searched the Web/Faq/Documentation/Mailing-Lists and haven't seen
any reference to this
At 03:19 PM 2/27/2003 -0800, Curtis Siemens wrote:
Cygwin's type command (built into bash.exe) does not work for
executables that are under a directory that has spaces.
Well, it seems to work OK for me:
---
501 $ mkdir /foo\ bar
502 $ touch /foo\ bar/baz
503 $ chmod a+x /foo\ bar/baz
504 $
At 01:51 AM 2/28/2003 -0800, Jeremy Hetzler wrote:
What is different about your particular installation, I have no idea.
Actually, one idea. Your 'type' might be an alias or function that fails to
quote its arguments properly. Try builtin type -a type. If it doesn't
return precisely type is a
8 matches
Mail list logo