From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: xenodasein--- via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Date: Wed, 30 Nov 2022 12:51:07 +0100 (CET) Message-ID: References: <87cz99l4td.fsf@thaodan.de> <87v8n1w7cf.fsf@yahoo.com> <87wn7gc53k.fsf@thaodan.de> <87r0xnx4fs.fsf@yahoo.com> <87edtncvss.fsf@thaodan.de> <87ilizwbkw.fsf@yahoo.com> <87cz94vjgl.fsf@yahoo.com-NI70zP3----9> Reply-To: xenodasein@tutanota.de Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27045"; mail-complaints-to="usenet@ciao.gmane.io" Cc: =?UTF-8?Q?Bj=C3=B6rn_Bidar?= , emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 30 12:52:14 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 1p0LdN-0006nY-Ug for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Nov 2022 12:52:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0LcU-0004wi-6k; Wed, 30 Nov 2022 06:51:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0LcN-0004wD-Br for emacs-devel@gnu.org; Wed, 30 Nov 2022 06:51:12 -0500 Original-Received: from w4.tutanota.de ([81.3.6.165]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0LcL-0003CW-Ni for emacs-devel@gnu.org; Wed, 30 Nov 2022 06:51:11 -0500 Original-Received: from tutadb.w10.tutanota.de (unknown [192.168.1.10]) by w4.tutanota.de (Postfix) with ESMTP id 9B838106015D; Wed, 30 Nov 2022 11:51:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1669809067; s=s1; d=tutanota.de; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=gKwVOm2ShppmjyaDorv+juEDmkz5/0okxYNrra5FKkU=; b=0M8JYcu98csJXdzFmBRfYnmYmdhGOeTPEzDAXrlij9FG5gUUzKLOkdahXDdkFK0M lxANsWjGsvLzBNPQ55kzN8MZ/fvgsqZozJgDmMHAQkceX6ltPXHorzvjN2iCfpmo1Vq NkP0raCF16WK5KT+6J8wFC6ez6O2DypI9YLu5xprJF7UeNrnxJcnUWo/KMuB8yJHzZJ mhl6s6zD9y1WZ8AI7d2NeduPP9qRwy2LTRyLZY/lPkQyfQialRn1/lgRaK3OeSDJw7S W/dlqdYsbggAwKEmUK4LXVAx3I9ezRiWem/XSHdM9vuVXlX7uLZMYmV6umxwWN7/M8c 543WLJ8UHQ== In-Reply-To: <87cz94vjgl.fsf@yahoo.com-NI70zP3----9> Received-SPF: pass client-ip=81.3.6.165; envelope-from=xenodasein@tutanota.de; helo=w4.tutanota.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300757 Archived-At: Nov 30, 2022, 10:13 by luangruo@yahoo.com: > xenodasein@tutanota.de writes: > >> To give less headaches to the users, why else.=C2=A0 Have one binary, >> do it dynamically. >> > > Then will you volunteer to write the code that makes it safe? And keep > it working for the next 5 or so years, at least? Regardless of what the > GTK developers decide to do in the meantime? > First of all thank you for not going straight for it's not possible / no one would want that / it's the wrong way / etc. I tried to suggest last year a way to draw your own window content without GTK, Lars said great you can start from vanilla X build, you and Eli on the other hand gave the impression that you found it extremely undesirable.=C2=A0 Which brings me to the point that this seems like a question of what do you want done instead of how to.=C2=A0 I am myself not at the point where I could pull this off alone, but I'm getting there.=C2=A0 Others would attempt at things like that if they found any enthusiasm about I'm sure. You must keep in mind that big contributions like this must have a foundation if there will be any hope of them even happening.=C2=A0 For example I can almost imagine the answers if I suggested separating some translation units instead of using #ifdef's every five lines, so I won't don't worry.=C2=A0 Or take as example the recent discussion on macros.=C2=A0 It won't make much of a difference indeed if some line is a function or a macro, issue is the resistance to even simple changes like that; it implies the impossibility of something not as simple. You can say no it doesn't, regardless that is the picture it paints. I remember Eli requesting not to change the location of some function on the grounds that it will now be harder to find where it is. So what is my point, when some person asks why do I need to binaries, instead of saying things like "why not" say we need more people to work with C parts, that's all.