I get a warning when compiling emacs from source with the pgtk flag telling me about a known bug in my version of gtk that causes problems when opening and closing multiple emacs instances. Do you know anything about this? In particular would it be resolved by switching to the snap?
I have no idea about that compilation issue you get. Since the emacs snaps (pgtk and x) are pre built binaries, you wont get that problem. Ive been using Emacs PGTK from snaps on WSLg for a year without any issue.
Yep that’s what finally caused me to switch to using Emacs on WSL2 (instead of the Windows build). Then you can also get rid of that ugly white border from WSLg.
Not sure if there’s something else missing in your setup. I’m using WSL2 (Ubuntu), and in my case all I had to do was compile Emacs passing the --with-pgtk flag, then:
that sometimes happens when wslg has issues with bind mounting the runtime dir from the system distro or runtime dir permissions, were you by chance using it with a uid != 1000?
You can try emacs-pgtk package, cause WSLg relies on Wayland
I downloaded the source code for emacs and compiling it locally with the --with-pgtk flag. (And --with-native-compilation for better performance)
That made my life improve a lot.
takes notes
You can also install pgtk emacs directly from snaps when under Ubuntu in wsl, if you prefer.
I get a warning when compiling emacs from source with the pgtk flag telling me about a known bug in my version of gtk that causes problems when opening and closing multiple emacs instances. Do you know anything about this? In particular would it be resolved by switching to the snap?
I have no idea about that compilation issue you get. Since the emacs snaps (pgtk and x) are pre built binaries, you wont get that problem. Ive been using Emacs PGTK from snaps on WSLg for a year without any issue.
Yep that’s what finally caused me to switch to using Emacs on WSL2 (instead of the Windows build). Then you can also get rid of that ugly white border from WSLg.
any details on that white border stuff? pgtk didnt autofix it for me in the past and id love to not have it searing my eyes
Not sure if there’s something else missing in your setup. I’m using WSL2 (Ubuntu), and in my case all I had to do was compile Emacs passing the
--with-pgtkflag, then:And ran
gnome-tweaksin the terminal, and changed the application and icon themes to Yaru-dark.that sometimes happens when wslg has issues with bind mounting the runtime dir from the system distro or runtime dir permissions, were you by chance using it with a uid != 1000?