Regards - Eliot Moss -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
I think what we mean is that, under Windows cmd, some things the shell does for you under Linux and
Cygwin will not have been done. For example, there is "glob" expansion of filenames. If I write
*.txt under bash, it gets expanded to a space-separated list of names of files that match that
pattern. This happens _before_ calling my program. If the program is run from Windows cmd.exe, the
program will receive an argument *.txt, and it will have to do the "globbing" itself. Etc.
- Unconsistent command-line parsing in case ... Jérôme Froissart
- Re: Unconsistent command-line parsing... Doug Henderson via Cygwin
- Re: Unconsistent command-line parsing... Andrey Repin via Cygwin
- Re: Unconsistent command-line par... Jérôme Froissart
- Re: Unconsistent command-line... Andrey Repin via Cygwin
- Re: Unconsistent command-... Jérôme Froissart
- Re: Unconsistent com... Andrey Repin via Cygwin
- Re: Unconsistent command-line... Brian Inglis
- Re: Unconsistent command-line... Thomas Wolff
- Re: Unconsistent command-... Brian Inglis
- Re: Unconsistent com... Eliot Moss
- Re: Unconsistent... Brian Inglis
- Re: Unconsistent command-line... Kaz Kylheku (Cygwin) via Cygwin
- Re: Unconsistent command-... Jérôme Froissart
- Re: Unconsistent com... Jérôme Froissart
- Re: UTF-8 quoted arg... Brian Inglis
- Re: Unconsistent com... Kaz Kylheku (Cygwin) via Cygwin
- Re: Unconsistent command-line... Brian Inglis