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: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning Date: Wed, 30 Nov 2022 19:43:43 +0200 Message-ID: <83bkoojq28.fsf@gnu.org> 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> <83iliwjtro.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1940"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, bjorn.bidar@thaodan.de, emacs-devel@gnu.org To: xenodasein@tutanota.de Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 30 18:44:57 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 1p0R8j-0000CN-7C for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Nov 2022 18:44:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0R83-0001On-CC; Wed, 30 Nov 2022 12:44:15 -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 1p0R82-0001Od-H4 for emacs-devel@gnu.org; Wed, 30 Nov 2022 12:44:14 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0R81-0003l8-Pi; Wed, 30 Nov 2022 12:44:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=j/xhDZzC+YOT7Qjol5nHaT1nYD+cq6HZRngSt4iaVbY=; b=Fn89s17J0q0/Px9YwlMC n1Ych95qU/YWiDJBREHlo4zeoh9pER+96OQSmvPKH/Z8sjRgIqq5cSvmIgc5qJO4pq+iCznhkQJzV lLXfiNmFn14LeEBXonGjitJcFaLLpFr5tjEZbYvbVqzE+rhbYazwxwdlxfhlq7bZ3xpl3WQTDRn6h CwqRMGb5QTtTRFnwAhi8UihDFRJQ1mx0ppC0hjCijcKxIQQKy9D1rX2ntSj7q1Yu8Oafh/3XYsWUo /EyyBpgx4/+dHrB630TvdrrwRnYUKjtieXXj///0H0LftQXPLCeurkOAlzAN1F9H458k8L/mYpHcC oGyNX9JPvvyNmQ==; Original-Received: from [87.69.77.57] (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 1p0R80-0004SL-Ij; Wed, 30 Nov 2022 12:44:12 -0500 In-Reply-To: (xenodasein@tutanota.de) 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:300778 Archived-At: > Date: Wed, 30 Nov 2022 17:56:39 +0100 (CET) > From: xenodasein@tutanota.de > Cc: luangruo@yahoo.com, bjorn.bidar@thaodan.de, emacs-devel@gnu.org > > I also repeatedly say adding completely new things like treesitter > is encouraged, because someone(tm) will maintain them supposedly. > Problem is tackling what's already in there, which happens almost > never compared the former. What do you mean by "tackling"? what is its purpose? > Overhauling display is going to require that, I'd love to see how it would > go without touching the infrastructure or without the friction I've seen > with simple mention of it before even changing code.  If someone attempts > that it would make it simpler to believe you, because I am discouraged to > take the first step. If someone redesigns and reimplements the display engine (which, btw, will be very welcome from where I stand), the result will be a complete rewrite of the relevant files, i.e. addition of new files and an almost total tossing of the old files. I know that because I was there when Gerd did that the last time. IOW, making such changes has very little to do with what is present, it has everything to do with introducing new files, functions, macros, and bugs. Of course, even writing completely new code needs to observe our conventions and coding style: Lisp primitives are defined using DEFUN, variables using DEFVAR_LISP etc., symbols are defined using DEFSYM, and there are protocols for initializing variables during the dumping and at startup etc. And your code and its design must be clean. But show me a project that doesn't have such conventions, and I will show you a dead project.