unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
	zimoun <zimon.toutoune@gmail.com>,
	GNU Guix maintainers <guix-maintainers@gnu.org>,
	guix-devel@gnu.org
Subject: Re: Release v1.4?
Date: Fri, 17 Jun 2022 11:37:18 -0400	[thread overview]
Message-ID: <87h74j5m17.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <87bkurfgru.fsf@gnu.org>


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?

The mainline Emacs is not Wayland-native, but it (along with just 
about everything else) will run fine under XWayland. It's how I've 
been running it for some time now. The user experience is almost 
indistinguishable from either the ‘pgtk’ branch or the mainline, 
X-only branch.

> (FWIW folks like me who use exwm, ratpoison, or one of these 
> geeky
> tiling window managers probably can’t switch.)

This is correct, but I don't see why this should prevent Guix 
offering the option for Wayland-based compositors/window-managers 
out of the box as all it does is offer more options for users.

> 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.

Unless I'm misunderstanding something, I don't believe that 
setting the ‘wayland’ flag to #t in gdm-configuration causes 
Wayland to be used for your desktop environment, it merely 
*allows* it to be selected from the greeter. When logging in you 
can select from Gnome under X, Gnome under Wayland, or other 
window managers you may have installed under either 
environment. Without that flag only the X11 window managers will 
be selectable.

-bjc


  reply	other threads:[~2022-06-17 15:49 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. [this message]
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

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h74j5m17.fsf@ditto.jhoto.spork.org \
    --to=guix-devel@gnu.org \
    --cc=bjc@spork.org \
    --cc=dev@jpoiret.xyz \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).