From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Removing the `window-id' frame parameter on non-Core Input platforms Date: Sat, 18 Dec 2021 11:35:56 +0200 Message-ID: <83tuf6b6gz.fsf@gnu.org> References: <87y24ifpkj.fsf.ref@yahoo.com> <87y24ifpkj.fsf@yahoo.com> <8335mqcqvm.fsf@gnu.org> <87mtkyfix2.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20276"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 18 10:36:51 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1myW93-00052Y-Sq for ged-emacs-devel@m.gmane-mx.org; Sat, 18 Dec 2021 10:36:50 +0100 Original-Received: from localhost ([::1]:38872 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1myW92-0007BG-Qu for ged-emacs-devel@m.gmane-mx.org; Sat, 18 Dec 2021 04:36:48 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:47496) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myW8O-0005yq-SV for emacs-devel@gnu.org; Sat, 18 Dec 2021 04:36:08 -0500 Original-Received: from [2001:470:142:3::e] (port=45692 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myW8O-0005HX-Jm; Sat, 18 Dec 2021 04:36:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=7l3veYSzH35RjooolchDx30x0xHobCOludg5TquVbg4=; b=nPFdqm9JEwGT BaHFjUjFS6SnONYcJDkB2EkNY5SzV5QBVAKhBt3s5OgzD73WBkFI+U2waAGplWvaY1kFezVpdtZk/ oaDFqwaH4J1NK0xN+494lL+d1AtRhvLuAqOgcVMu2pABiJ3dsMB+tFgHVXb3Pjjfs3HfzCQLn8EPJ W7oMEkYu2HNplIttlw4LqO3ABsNUsYlNqJSLVUdBX4kn8Y20BWKUMQWpZXAhqoVMLtmrZorcReEi5 2pOlevtPiZHe8KN87lx9qwRsgELjs0MmO9oOFR3zUXjlTMizcPGfLQocRr7fhIEhyX+dy2S24sOWm nyKfAVxjobIvTNUBgn55dg==; Original-Received: from [87.69.77.57] (port=2634 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myW8O-0005fW-Ci; Sat, 18 Dec 2021 04:36:08 -0500 In-Reply-To: <87mtkyfix2.fsf@yahoo.com> (message from Po Lu on Sat, 18 Dec 2021 15:53:29 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:282271 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Sat, 18 Dec 2021 15:53:29 +0800 > > Essentially, to work around the freeze described in PROBLEMS, a frame's > window is recreated which changes the XID of the frame. Non-Emacs X > clients that have kept track of the previous XID will crash with a > BadValue error when trying to use the previous XID. But that isn't Emacs-specific, is it? AFAIR, the window ID is a general X feature, we just support it. > Other uses of the `window-id' parameter such as to display windows as > children of a frame are discouraged on XInput2 builds, as it can > interfere with XInput2 event handling You mean, using it for our child frames?