From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92579 invoked by alias); 30 Aug 2019 20:59:17 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 92572 invoked by uid 89); 30 Aug 2019 20:59:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy= X-HELO: NAM04-BN3-obe.outbound.protection.outlook.com Received: from mail-eopbgr680104.outbound.protection.outlook.com (HELO NAM04-BN3-obe.outbound.protection.outlook.com) (40.107.68.104) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 30 Aug 2019 20:59:15 +0000 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== 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-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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bgV1T/+mLwuPXO1QpAlxT9+Yn3qxae7UkJRiquybzMM=; b=iriRl147ZiDGD9pSDoKtmGQvDNauIblhNaVJAVU2vJpAB4BuZYIV2ejzeZfaeGa6Ubsqm6AlG81HmbLs2mCckBIFtnpboFfHgb3ctaQSB+HLd/UxBR/4JyqdlRNMi5m6YIRSrMJJxH83usCKftrTX9UgYntivumCjwbTUJAoaoQ= Received: from MWHPR21MB0845.namprd21.prod.outlook.com (10.173.51.139) by MWHPR21MB0142.namprd21.prod.outlook.com (10.173.52.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.8; Fri, 30 Aug 2019 20:59:13 +0000 Received: from MWHPR21MB0845.namprd21.prod.outlook.com ([fe80::3085:a037:7cbc:be5]) by MWHPR21MB0845.namprd21.prod.outlook.com ([fe80::3085:a037:7cbc:be5%5]) with mapi id 15.20.2241.000; Fri, 30 Aug 2019 20:59:13 +0000 From: "Stephen Provine via cygwin" Reply-To: Stephen Provine To: "cygwin@cygwin.com" , "Brian.Inglis@SystematicSw.ab.ca" Subject: RE: Command line processing in dcrt0.cc does not match Microsoft parsing rules Date: Fri, 30 Aug 2019 21:21:00 -0000 Message-ID: References: In-Reply-To: authentication-results: spf=none (sender IP is ) smtp.mailfrom=stephpr@microsoft.com; x-ms-oob-tlc-oobclassifiers: OLM:8882; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: cFpqeO2hF7eiEtyk7iCQ4whRqt23BN2MQGY+xo+JRtwcN+Z25B9olBC6yLTRAe8H9AjMMMITUn+tMm5Nxr5lHQ== X-SW-Source: 2019-08/txt/msg00435.txt.bz2 > Cygwin command line parsing has to match Unix shell command line processi= ng, > like argument splitting, joining within single or double quotes or after a > backslash escaped white space characters, globbing, and other actions nor= mally > 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 de= termine 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