This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules
- From: "Stephen Provine via cygwin" <cygwin at cygwin dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>, "Brian dot Inglis at SystematicSw dot ab dot ca" <Brian dot Inglis at SystematicSw dot ab dot ca>
- Date: Fri, 30 Aug 2019 20:59:12 +0000
- Subject: RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bgV1T/+mLwuPXO1QpAlxT9+Yn3qxae7UkJRiquybzMM=; b=kVfhu1nfN3LmI2pg/vxiMRqjOm+DZZNh6Ww/DmCliDkeNp9ZxHxTq0fQgUopYO+Da0EkGYUxE59v/rh8k6/obDVPx2UIT3AgFMu1YRATQNlgK34ZyJR7CNYdDfJXxTvGZ358L6DYouuNyZeoUwJVrT5QrMjiGIu0yy6JYZJxu+WewSzjYdHV4kymPpKzDkZmlH/jk3hp0oP4NNZL7Pq/CGhlwr0VNECVR3hGJVlllxJPWOlZ7PFcC+lx/Grfaj6WG51pvoDeZPU8BvNpDlPPqzqXf065sOoF8VB8PG/VblTUNJ7I5d4Vo0L7U/Mh0iuTdK2ISuT11KlySR7GLXRSyA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cc8holrObyY7dfrem/J59riOzzl4vo3NspMX9oXlgm10hZ5Z0GUr82Fb3OheeS1ST+UsJi98/OgKH7PpedlusrGY89aKeCRm3nrHKI1qkNPY94DGGTopk8EMoFSnCj7EU9Bln+q4bY9lp8ltjqHfCX7FKTsVwbsRBxJPI7FLjKjh7h4jXwu39G6FxSxpEbQL3h2CKEw7Ap5F8uOha+Ulkl3v8EKlhPTKCVgMC6+sTMwxmotTiQNnf2JGhTMGH0xHWfCKdp/KBAD3U1zHparPiBwOYRfCVVFuWkfjKOF7pIVDLkfoRTeja802Ay+os0fx0XXaqj5Pu+wCpV9bZYHPmA==
- References: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0@MWHPR21MB0845.namprd21.prod.outlook.com>
- Reply-to: Stephen Provine <stephpr at microsoft dot com>
> Cygwin command line parsing has to match Unix shell command line processing,
> like argument splitting, joining within single or double quotes or after a
> backslash escaped white space characters, globbing, and other actions normally
> performed by a shell, when any Cygwin program is invoked from any Windows
> program e.g. cmd, without those Windows limitations which exclude any use of a
> backslash escape character except preceding another or a double quote.
I guess my assumption was that the "winshell" parameter would be used to determine
when a Cygwin process is called from a non-Cygwin process and that it would be more
appropriate to use standard Windows command line processing (as limiting as it may
be) in that case. Once in the Cygwin environment, calls from one process to another
should obviously process command lines according to Unix shell rules.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple