emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PGTK build starts at random position (WSLG)


From: Po Lu
Subject: Re: PGTK build starts at random position (WSLG)
Date: Sun, 27 Nov 2022 19:11:59 +0800
User-agent: Gnus/5.13 (Gnus v5.13)

Angelo Graziosi <angelo.g0@libero.it> writes:

> Recently there was a Windows update that back-ported WSLG
> (https://github.com/microsoft/wslg) to Win10 so one can run GUI app in
> WSL (Ubuntu 22.04 here)!
>
> I tried my Emacs master binaries (built on GNU/Linux Mint, GTK3+cairo)
> and they work (after the installation of some missing packages). I did
> directly the same build on WSL. I used also the same .emacs.d
> directory I have on Mint! Obviously it looks a bit different: there is
> no Emacs icon on the upper left corner (near the window title); the
> icon on the task bar is a little penguin over the Emacs icon..)
>
> Now I found this article:
> https://emacsredux.com/blog/2021/12/19/using-emacs-on-windows-11-with-wsl2
> so tried to build a PGTK version and also these binaries work but when
> I start this toolkit of Emacs, it starts at random even if I have this
> code in the init.el file:
>
> (setq default-frame-alist
>       '(
>         (width . 120) ; character
>         (height . 54) ; lines
>         (left . 835); pixel
>         (top  .   0); pixel
>         (font . "Monospace-11") ; font
>         ))
>
> Notice that I use more or less the same code for the Windows, macOS
> and GNU/Linux builds (just the font or the left parameter changes) and
> it is respected. Not by PGTK build. In short, PGTK seems to ignore the
> top and left statements.

That is definitely not a bug in the PGTK build, because the Wayland
protocol doesn't let it change the absolute position of its toplevels at
all.

> Another issue is that I cannot copy/paste (C-w, M-w) from pgtk-Emacs
> elsewhere.. (I had to write manually the above code in this email).
>
> Do you know if these are PGTK bugs? or is there some work around?

That is almost certainly a bug in WSL (which is in general of very low
quality; you ought to stay far away from it.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]