Hi Eric, Thanks very much for prompt reply.
1. We downloaded these programs from GNU coreutils site. I didn't realise there were different versions. I will have a look for "cygwin" version. 2. I thought that "cat" may not do globbing, it's just that the old version of "cat" we had from MKS (Mortice Korn Systems) works ok in the same environment. 3. > This email and any files transmitted with it are confidential I didn't include this in my original email and my company does not add any disclaimers (as far as I am aware)- it must have been added during forwarding to you. So, the final outcome appears that I should get "cygwin" version of cat, as you have found that this works as expected Thanks again, Neil -----Original Message----- From: Eric Blake [mailto:[EMAIL PROTECTED] Sent: Tuesday, 19 December 2006 4:31 PM To: Clough, Neil Cc: [email protected] Subject: Re: Wildcard (globbing) in directory names -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Clough, Neil on 12/18/2006 5:54 PM: > Hi, > > We have a problem using the GNU coreutils "cat" program under Win32. If you got this program pre-compiled from a particular Windows port, such as cygwin, you may be better off asking the people that maintain that port for help. > > eg cat <part dir name>*/<part file name>* > > And cat would find all files matching to <part file name>* in all > directories matching to <part dir name>* > > This does not seem to happen with GNU coreutils cat ! Actually, cat does not do ANY globbing. Instead, in Unix tradition, cat defers globbing to the shell. But Windows shell cmd.com is rather deficient, and does not do any globbing either, so people who port GNU programs to Unix must provide a glob wrapper that executes prior to main() when called from cmd. I suspect that whatever version you are using has a bug in that wrapper. You may want to try the cygwin port instead, as I just verified that the cygwin version of cat does not have this problem, whether run from cmd or from a proper shell such as bash. > This email and any files transmitted with it are confidential That is not a very wise disclaimer to stick on mail to publicly-archived mailing lists, as it is practically impossible to enforce. If your employer adds it blindly, then I would suggest looking into a free email account for use when posting to these sorts of lists. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFh3j884KuGfSFAYARAqRdAJ9hcf5EU2XYELzknRpbpuKGulKpjgCggbqi te4dUFSaTliamMEISoLXv5Q= =pvQc -----END PGP SIGNATURE----- ******************************************************** This message was scanned for viruses using Trend Micro's IMSS, and was found to be virus-free. ******************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately. ******************************************************** _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
