From: Josselin Poiret <dev@jpoiret.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: zimoun <zimon.toutoune@gmail.com>,
Guix Devel <guix-devel@gnu.org>,
GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Release v1.4?
Date: Fri, 17 Jun 2022 17:45:59 +0200 [thread overview]
Message-ID: <87pmj7ths8.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87bkurfgru.fsf@gnu.org>
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> So plain ‘emacs’ package doesn’t work on Wayland? That sounds like a
> recipe for a poor user experience, no?
It does, but only through XWayland which is not ideal, and doesn't look
as good as Emacs on native X or emacs-pgtk on Wayland (font rendering in
XWayland isn't as good as either of those).
> (FWIW folks like me who use exwm, ratpoison, or one of these geeky
> tiling window managers probably can’t switch.)
Maybe someone would love to write ewwm? :p
> Yeah, understood. (I think we should have a section in the manual
> documenting, with actual examples, how to set up Wayland!)
>
> Surely there’s a geek audience who expects Wayland, and another geek
> audience who needs X for their tools; in between, there’s probably a lot
> of people who’s fine either way.
What I was advocating was only to change GDM's default mode to Wayland,
not force everyone to use a Wayland compositor! The reason is that GDM
running in X mode will not pick up Wayland sessions, whereas GDM running
in Wayland mode will happily list and launch both types. Also, note
that X software can run on Wayland through XWayland, which is part of
the official xorg project and works quite well, minus some small
wrinkles such as the one noted above.
> I have no objection to defaulting to Wayland, but my gut feeling is that
> we have enough on our plate for 1.4 already, so I’d rather delay that
> post-release.
>
> WDYT?
Seems ok to me, since in any case most people trying out Guix in a VM
will `guix pull` before `guix reconfigure`'ing, as long as we do that at
some point it will work OOTB for them. We can postpone all of this for
after the release.
Best,
--
Josselin Poiret
prev parent reply other threads:[~2022-06-17 15:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:35 Release v1.4? zimoun
2022-06-03 16:41 ` Ludovic Courtès
2022-06-05 17:57 ` zimoun
2022-06-05 22:31 ` vidak
2022-06-06 15:39 ` Maxim Cournoyer
2022-06-06 21:17 ` Merging ‘staging’? Ludovic Courtès
2022-06-08 11:50 ` Efraim Flashner
2022-06-08 21:24 ` Ludovic Courtès
2022-06-10 7:57 ` Efraim Flashner
2022-06-11 9:53 ` Ludovic Courtès
2022-06-11 10:49 ` Tom Fitzhenry
2022-06-12 3:58 ` Efraim Flashner
2022-06-12 21:08 ` Ludovic Courtès
2022-06-13 7:03 ` Ludovic Courtès
2022-06-14 4:01 ` Thiago Jung Bauermann
2022-06-14 10:32 ` Release ? (was: Merging ‘staging’?) zimoun
2022-06-14 13:08 ` Efraim Flashner
2022-06-15 9:21 ` Release ? Ludovic Courtès
2022-06-09 17:19 ` Merging ‘staging’? pelzflorian (Florian Pelz)
2022-06-09 17:41 ` Efraim Flashner
2022-06-09 19:02 ` pelzflorian (Florian Pelz)
2022-06-10 6:07 ` pelzflorian (Florian Pelz)
2022-06-11 7:35 ` pelzflorian (Florian Pelz)
2022-07-15 10:52 ` Rock64 segfaults (was: Merging ‘staging’?) Timotej Lazar
2022-06-12 4:54 ` Merging ‘staging’? Thiago Jung Bauermann
2022-06-12 21:06 ` Ludovic Courtès
2022-06-10 15:47 ` Release v1.4? Josselin Poiret
2022-06-15 8:54 ` Ludovic Courtès
2022-06-15 16:51 ` Gábor Boskovits
2022-06-16 8:59 ` Josselin Poiret
2022-06-17 15:31 ` Ludovic Courtès
2022-06-17 15:37 ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-19 3:33 ` Further thoughts on Xorg "vs" Wayland etc -- was: " bokr
2022-06-19 18:16 ` Philip McGrath
2022-06-22 13:31 ` Ludovic Courtès
2022-06-28 9:02 ` Efraim Flashner
2022-06-17 15:45 ` Josselin Poiret [this message]
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=87pmj7ths8.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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/guix.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.