Re: Questions regarding PGTK, high-dpi font-rendering, new X11-Warning

[Eli Zaretskii <eliz@gnu.org>]

> 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.