Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!nuzba.szn.dk!pnx.dk!news.stack.nl!aioe.org!.POSTED!not-for-mail From: glen herrmannsfeldt Newsgroups: comp.lang.c Subject: Re: Command line arguments Date: Fri, 11 Jan 2013 19:33:24 +0000 (UTC) Organization: Aioe.org NNTP Server Lines: 30 Message-ID: References: <486a1ce3-650e-4c93-81b3-c42e6cbee62e@googlegroups.com> NNTP-Posting-Host: iv0FLp+Uhvv05NzXKWDP0Q.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org User-Agent: tin/1.9.6-20100522 ("Lochruan") (UNIX) (Linux/2.6.32-5-amd64 (x86_64)) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.c:29957 88888 Dihedral wrote: (snip) > Well, you are reminding me the dir function > from the M$ in the 1990 that refused to > do nested diretory search under 1M. The way command line expansion is done in current windows is still surprising to unix users. Unix ls, with shell globbing, will show the contents of the directories in the expanded directory list. dir * on windows will show the contents of the current directory. cd * doesn't work right on Windows (even if there is only one directory) but it does with unix shells. And I still remember my first MSDOS system, version 3.2, where the RENAME command wouldn't move files to a different directory (like unix mv) but the C library rename() function would. (The Windows MOVE command is much more recent.) -- glen