DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 5B5BCbAN1257707 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 5B5BCbAN1257707 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=M7s1XHrh X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A27794C900CC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1764933155; bh=zYnWCZTLDrdZ1yaeN8Gge9KZcL1rtOqqA3VKhVLovS0=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=M7s1XHrhjq+M6jrTbILySJF4+CizYfx4yduwQKB4ridqpBEfNFAFna+BngtDg55og UCaIIj57rFeKntJguz6YMawwjfi2JRkr3IYihTDm9vzOl55dVZUm1YV6bOEAHvkv9x 8/NM7C5CaVj+/w4Sw41x+Kti2J4dVrtnplN8W7bE= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3B9944BA23FD Date: Fri, 5 Dec 2025 12:11:47 +0100 To: cygwin AT cygwin DOT com Subject: Re: dynamic conpty loading Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <20251121190433 DOT 4a37dc959848a0aea89a8922 AT nifty DOT ne DOT jp> <62f3c1ae-1fd9-477d-a837-d865094dab06 AT towo DOT net> <20251126193220 DOT 1b890f58a121add2f0d05fa5 AT nifty DOT ne DOT jp> <3a6ed5bc-24fd-42b0-9f57-83c8eb678a1b AT towo DOT net> <20251127172026 DOT 6b6f876fd341f9c0cbd1f876 AT nifty DOT ne DOT jp> <20251203175638 DOT 0b4f51242c8fdab685ad9b7e AT nifty DOT ne DOT jp> <20251205185220 DOT 26512b609b7e96b388245244 AT nifty DOT ne DOT jp> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20251205185220.26512b609b7e96b388245244@nifty.ne.jp> 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: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen 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" On Dec 5 18:52, Takashi Yano via Cygwin wrote: > On Thu, 4 Dec 2025 12:01:58 +0100 > Corinna Vinschen wrote: > > Aren't from here on two patches folded into one? All but one hunk (the > > one calling CreatePseudoConsole_new) seem to be entirely independent of > > OpenConsole. > > This part is necessary to work with OpenConsle.exe. OpenConsole.exe uses > also ESC[c during startup while conhost.exe uses only ESC[6n. Ok, but ESC[c is a stock vt100 sequence. Admittedly, I have no idea if there are other terminals out there which use this sequence at startup, too... > > > - static const int wpbuf_len = strlen ("\033[32768;32868R"); > > > + static const int wpbuf_len = 64; /* for response to CSI6n nad CSIc */ > > > > Is there some macro for the count of 64 in this context, by any chance? > > I'm not sure for now that 64 is really enough for the responce to ESC[c. > mintty returns about 30 byte responce. But some other terminal may return > longer responce. Per the vt100 documentation, the response is supposed to be ESC [ ? 1 ; Ps c with Ps being a character in the range 0 - 7. Just being curious, what are mintty and OpenConsole returning? > > > [...] > > > if [ $(uname -m) = "x86_64" ] > > > then > > > POSTFIX="x64" > > > else > > > POSTFIX="x86" > > > > Do we really want a 32 bit version? Isn't there an aarch64 version? > > No. Weird. But Windows on AArch64 supports a x86_64 emulation, iiuc. > What should we assume result of "uname -m" in aarch64 machine? "aarch64" :) > > For a start, this may be ok, but we should really try to build our own > > OpenConsole package build by our own gcc or clang, IMHO. > > OpenConsole.exe also uses WIL, so it looks not easy to build it in cygwin > environment. > > Maybe just getting it from https://github.com/microsoft/wil/ is enough, > but I have not tried it yet. Oh, wow! Looks like fixes to build WIL on MingW have been merged just a couple of hours ago. Corinna -- 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