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: Abysmal state of GTK build Date: Mon, 22 Aug 2022 15:40:17 +0300 Message-ID: <83zgfwa1u6.fsf@gnu.org> References: <87ilmlluxq.fsf.ref@yahoo.com> <87ilmlluxq.fsf@yahoo.com> <87h725olz1.fsf@gnus.org> <87zgfxn6lt.fsf@gnus.org> <87tu65k9ec.fsf@yahoo.com> <87r119lnsd.fsf@gnus.org> <87mtbxlnf1.fsf@gnus.org> <87czctk890.fsf@yahoo.com> <87a67xlm9v.fsf@gnus.org> <87k070g6l0.fsf@yahoo.com> <8635do4u9b.fsf@gmail.com> <877d30g1az.fsf@yahoo.com> <87czcsfw4v.fsf@djcbsoftware.nl> <87mtbweaxj.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22217"; mail-complaints-to="usenet@ciao.gmane.io" Cc: djcb@djcbsoftware.nl, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 22 14:42:13 2022 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 1oQ6kv-0005ZY-Gw for ged-emacs-devel@m.gmane-mx.org; Mon, 22 Aug 2022 14:42:13 +0200 Original-Received: from localhost ([::1]:51290 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oQ6ku-00037b-52 for ged-emacs-devel@m.gmane-mx.org; Mon, 22 Aug 2022 08:42:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44054) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oQ6j4-0001rD-6t for emacs-devel@gnu.org; Mon, 22 Aug 2022 08:40:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:51692) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oQ6j2-0002eH-W0; Mon, 22 Aug 2022 08:40:17 -0400 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=iirOc70Rqdki4YhO7w1OcXvuT/1Lzx0wza3C4K8Yma8=; b=cuGPlegWciCC Sg5PxySV8gHcGPUKe1P3cE4NpCl0QcJCA7Z02r0iIB2rw6d29NF7HMB+pUsRz/DuG1xdNFkH+uB9D jqSUZOC0YiyYCBYk3qy/IOzSbj8+wH4y5U7S49APO5xi+dNouTpZP26rV+KHot+t+fxPkiP+J6U6x uDBos6fLfNvT6CxnWJYR4AS0U0YcNJaBzSZaW3w7yKFpHNb5YdNcrvgiRUstWJ34wxSRk3F4O4lpN aKQHt7HWOuUW7ZmT4Vo4nXDq5GYv/d1DwzS4LC6FSMqnbpay3Q8wQ4HNi/Ij2lutFbza6itzrkk97 d3vIN5d6c9fUFEYD3HFxKw==; 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 1oQ6j0-0004o6-S0; Mon, 22 Aug 2022 08:40:16 -0400 In-Reply-To: <87mtbweaxj.fsf@yahoo.com> (message from Po Lu on Mon, 22 Aug 2022 20:10:16 +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:293800 Archived-At: > From: Po Lu > Cc: emacs-devel@gnu.org > Date: Mon, 22 Aug 2022 20:10:16 +0800 > > > There have been grumblings about scenarios that GTK doesn't implement > > correctly or at all, and there were some big warning for that (there > > still may be). It seems we now emacs is adding a new such scenario > > (XInput2), while the GTK developers have lost some interest in X11 -- it > > seems we should just not enable XInput2 in that case. > > It seems to me that the same crowd asking for various "modern" GTK > features also want features like pixel-scroll-precision-mode and monitor > refresh synchronization, which cause crashes or don't work on GTK. We > are then blamed for the feature not working there as a result of bugs or > misdesigns in GTK. > > In any case, there is no excuse for GTK to have buggy XInput 2 support, > considering that it used to be something that we did not support, > requiring various workarounds to explictly disable in GTK, and is > mentioned in the first few paragraphs of the GTK+ 2 to 3 migration > guidelines. What is your opinion on defaulting the GTK build to be without XInput2? Since that option causes crashes, it sounds to me like a good compromise to leave the GTK build (by default) without the XInput2 niceties, providing an opt-in configure-time switch to use XInput2. This will allow people who don't mind an occasional crash, or can avoid that procedurally, to have the XInput2 features, while at the same time protecting the innocent.