From: Angelo Graziosi <angelo.g0@libero.it>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: PGTK build starts at random position (WSLG)
Date: Fri, 25 Nov 2022 18:15:50 +0100 (CET) [thread overview]
Message-ID: <99254210.280314.1669396550599@mail1.libero.it> (raw)
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.
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?
TIA,
Angelo.
next reply other threads:[~2022-11-25 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 17:15 Angelo Graziosi [this message]
2022-11-27 11:11 ` PGTK build starts at random position (WSLG) Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99254210.280314.1669396550599@mail1.libero.it \
--to=angelo.g0@libero.it \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.