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 09:29:49 +0200 Message-ID: <8335mqcqvm.fsf@gnu.org> References: <87y24ifpkj.fsf.ref@yahoo.com> <87y24ifpkj.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26241"; 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 08:32:33 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 1myUCl-0006gi-2C for ged-emacs-devel@m.gmane-mx.org; Sat, 18 Dec 2021 08:32:31 +0100 Original-Received: from localhost ([::1]:43566 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1myUCj-0000Y7-OR for ged-emacs-devel@m.gmane-mx.org; Sat, 18 Dec 2021 02:32:29 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58370) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1myUAL-0006kl-8y for emacs-devel@gnu.org; Sat, 18 Dec 2021 02:30:01 -0500 Original-Received: from [2001:470:142:3::e] (port=38780 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 1myUAK-0005vF-WB; Sat, 18 Dec 2021 02:30:01 -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=j/pW+jmGW5s1i3EJNepcl4fYE85ZcmLSQz+WXHg6LZ0=; b=fL1ZjoXH2wRV FaggZiq03C/RTfJOjRNLNmUgO5hJPKtCPqJ5rVYAKLQyHqGdWaNyb/SB3IJyY6v6p8IJYoZjU1LQB nYdQKaUjKXFwdbVf4ySBWUxZu8mE+L6NY0d7j4sE/Fi4rKLn2lGfosSuSE/aeDu3jCj/IlDY2TzPN gc6IQoHmeg4mC2L0bZcuWoJNVlqobfzoGzjczOZZnej50ptwVlJZRICXG0zizzSpPXNDE3zO/EQuT pL7FCzyDHmnauWZ9DMohTfKFrUFfvh8rh06ug7xwfJRu3TT5x9yUg+/afFYJWc+3sCNlhmIY7Jv4l SnOWaJFV1WJSfeEPf0OLjA==; Original-Received: from [87.69.77.57] (port=2878 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 1myUAK-0001Y9-RZ; Sat, 18 Dec 2021 02:30:01 -0500 In-Reply-To: <87y24ifpkj.fsf@yahoo.com> (message from Po Lu on Sat, 18 Dec 2021 13:29:48 +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:282257 Archived-At: > From: Po Lu > Date: Sat, 18 Dec 2021 13:29:48 +0800 > > The only platform where it is useful is X with Core Input, where third > party programs can use it to manipulate a frame's X Window. > > This is safe on Core Input, but on XInput 2 I'd like the freedom to > change the underlying X window of a frame after it is created to work > around some difficult GTK related problems, which will make continuing > to support the `window-id' parameter unreasonable. Touch event tracking > on XInput2 also requires that no non-Emacs code modify a window created > by Emacs to work correctly. Please describe the problems you see in continuing the support for window-id. You say it's unreasonable, but please tell more to clarify why it is so. I don't necessarily object to the idea, but there could be in principle other alternatives that are less backward-incompatible. I'd like us to weigh those before we make the decision. Thanks.