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

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

[Pedro Andres Aranda Gutierrez]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

Po Lu <luangruo@yahoo.com> writes:

> Why? There is already a perfectly good X build, so doing so would be a
> waste of our energy.

Let's say it's a "reasonable" build. The N times the Emacs window is
resized and moved around before it lands where you want it to be is
something that should be looked into. And that doesn't happen on the pgtk
build (at least for me-TM).

My .2 cents, /PA

-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 1055 bytes --]

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

[Po Lu]

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

> Let's say it's a "reasonable" build. The N times the Emacs window is
> resized and moved around before it lands where you want it to be is
> something that should be looked into. And that doesn't happen on the
> pgtk build (at least for me-TM).

That's a bug in Cairo.  GTK works around it by using a completely
different settings mechanism that AFAIK only works on GNOME.

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

[Björn Bidar]

Po Lu <luangruo@yahoo.com> writes:

> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
>> Let's say it's a "reasonable" build. The N times the Emacs window is
>> resized and moved around before it lands where you want it to be is
>> something that should be looked into. And that doesn't happen on the
>> pgtk build (at least for me-TM).
>
> That's a bug in Cairo.  GTK works around it by using a completely
> different settings mechanism that AFAIK only works on GNOME.

Did you test Kwin? I'm not sure if the bug happens on my devices but I
haven't experienced it.

Br,

Björn