-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pgtk to the snapshot build #45
Conversation
Thanks for the PR but as far as I know pgtk is still not recommended when running under X - and since the emacs snap is designed to run under both X and Wayland then I don't think it is appropriate to enable this for all users. Instead if there is some particular benefit to using pgtk on Wayland, then perhaps we could look at building emacs both with and without pgtk enabled (and having each then compiled into a separate binary), ship both these binaries inside the snap and choose which one to actually run at runtime by detecting if the session is using Wayland. |
Thanks, I wasn't aware of the issues with pgtk under X. |
pgtk is (currently) required for fractional scaling to work in Wayland, that might justify the effort? |
Unfortunately I don't have the time to look at this at the moment - but I would be more than happy to include something like this if anyone wants to submit a PR. Thanks. |
Hey @alexmurray, thanks a lot for providing the Emacs snaps and also maildir-utils, those are super convenient to use. If I can add an extra point, having Your snaps work fine without I've noticed quiet a few Emacs devs using WSL and compiling Emacs with |
So we either need to look at shipping a single emacs snap build that has binaries compiled with and without pgtk and then dynamically selecting which one to use on load - OR we have a separate branch in the repo which enables pgtk and then build this via a separate snap recipe in Launchpad which finally publishes to a separate track in the Snap Store - then when installing the snap users can either install the regular one EDITED to add: forum request is at https://forum.snapcraft.io/t/track-request-for-emacs-snap/32886 |
The second option sounds the best to me. It avoids having two binaries at the same time and also you won't have to implement some code to figure out which precise environment the snap is running in. ps: do we need to do something on the forum to vote for your request? |
Ok the track is now created and I have a simple build that enables pgtk and pushes to the new track - however it dies on startup since the version of gsettings-desktop-schemas in Ubuntu 20.04 (as the snap is core20 based) is too old - so I am now trying to port the emacs snap to core22 (however this is another huge can of worms to deal with as per https://snapcraft.io/blog/the-new-classic-confinement-in-snaps-even-the-classics-need-a-change). So at this stage having a working pgtk build of the emacs snap is looking quite challenging. |
Hey Alex, I can confirm I have the same error on startup using Ubuntu 22.10 (GNOME/Wayland): (emacs:3613): GLib-GIO-ERROR **: 09:46:42.394: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing' Good news though, I also tried your build on WSL with WSLg and I don't have a single problem so far. |
It may depend on what host environment you are using - but I am glad it works at least in some cases. I'll keep working towards a proper solution and will update this issue when I get something going. |
No description provided.