DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 579Ba7sY084738 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 579Ba7sY084738 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=nsU4IxYC X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3440F385735D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1754739364; bh=jkBw6nCZdgc2X5PwypR0K9zsI0FHItLTQ0VoZ/MGY9M=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=nsU4IxYCQZCYIzccpBaVL/1IXIjykAI/ofZjZtD+SIuUycoBVEv3FUDBBKTxXyUAg /u4QilRzK9EjJKVkeH8LaH29Ddqd+19Gunh/YMRXmbGl1Li6xhl5nor91Oo+PS00dt f8OGrEH3bYB1CbJ86rTieAWZ5FklzpFfnTom8VQ4= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 2078B3858D29 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 2078B3858D29 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754739305; cv=none; b=aZx0BGupuij8QPzYhhGBmtfx/vPYfymHXU+qbcN7Xcw1WZamjfnpZJ22EpDuuiTJiE7vl+V30VGPZHKSejN8YODR54Sqd6D9RPRI2CCub8+LncMrVSC2QRsoGh9FRoxOVn308dFC9D0BdGeGhvJhwhHRQue/jdAE64bSLc5Gn8U= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1754739305; c=relaxed/simple; bh=9DCD9tQZUhyEm95AUj+7lCL5EeNMEgYt0b9fEktY9to=; h=DKIM-Signature:Date:From:Message-ID:To:Subject:MIME-Version; b=iOYFgeTiNXeHysVVLuSGHXrgQqkkZdiy5ZWXP4g3+RexcUA/lu7/NAQ1Kd+Osofk3ID82QPGIhSCymRJDRp545HCqlZNu9UijpRri2bB+yrAF1MSxCNmeOAXyNA/zXqmMJEzMiyLXabCWP40e8RDtZ0bUt4pkh7Dcr+6Va1UXVc= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2078B3858D29 X-Yandex-Fwd: 1 Date: Sat, 9 Aug 2025 14:31:26 +0300 X-Mailer: The Bat! (v9.3.4) Professional Message-ID: <1164983593.20250809143126@yandex.ru> To: "Old, Oliver" , cygwin AT cygwin DOT com Subject: Re: Incorrect command line handling when launching Cygwin program from Windows In-Reply-To: References: <87264da9-cc87-4a63-89cb-e30fc6c1126b AT emrich-ebersheim DOT de> <1489952594 DOT 20250804215103 AT yandex DOT ru> MIME-Version: 1.0 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Andrey Repin via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Andrey Repin Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Greetings, Old, Oliver! >> Then do not mix environments. > That is not my choice, but rather my supervisor's choice. I began > engineering our new CMake-based build system purely with MinGW > toolchains in mind, statically linked ones even since I already know how > well-received it would be if I required people to install a MinGW > environment and had them add it to their PATH. > Then I was told we might have to abandon this new system if we can't > keep using our Cygwin toolchains. Then this is not an issue with Cygwin, or mingw, but rather, with the tools you are using. > I know it is very unwise to attempt this and entirely unproductive. >> Cygwin with automation scripts. > I wish that was good enough, but I'm supposed to make it work with all > the GUI and integrated debugging capabilities the other toolchains have. > It is so very frustrating. > Back to the technical aspects: I just don't see why the current command > line handling is supposed to be good. It is not good or bad. Keep in mind that there are more pieces moving than what you are thinking there are. > I find it to be very surprising as > its entire purpose is interfacing with non-Cygwin software. Why should > the "non-Cygwin" software assume the command line to be parsed according > to Bash's rules? No. It first parsed by CMD itself according to its own rules (CMD /? helps to clarify some o 'em, but I would strongly suggest https://ss64.com/nt/ as a WAY, WAY better source of information), and only when the line is passed down to the cygwin app, the Cygwin DLL reassebles and reparses the line according to POSIX rules. -- With best regards, Andrey Repin Saturday, August 9, 2025 14:24:26 Sorry for my terrible english... -- 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