unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Felix <felix.dick@web.de>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 57781@debbugs.gnu.org, Sean Whitton <spwhitton@spwhitton.name>
Subject: bug#57781: missing wallpaper command
Date: Thu, 15 Sep 2022 00:51:39 +0200	[thread overview]
Message-ID: <87a671h861.fsf@web.de> (raw)
In-Reply-To: <CADwFkm=oniKfEQiZpFmevnBUFNu3OZRM00hXzh3+G3N9AquG_Q@mail.gmail.com>


Stefan Kangas <stefankangas@gmail.com> writes:

> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>>> To test for Wayland, it only checks if $WAYLAND_DISPLAY is set.
>>> We could do something more fancy if needed, possibly involving
>>> loginctl.
>>
>> Since it's protocol-dependent, I don't know if it will work on anything
>> other than wlroots-based compositors.  Before relying solely on
>> WAYLAND_DISPLAY, perhaps we should also check it works with GNOME?
>
> I need help here, as I don't have access to Wayland.
>
> Would you be willing to help test it, and/or make concrete suggestions
> for how to do better?  I'd ideally need someone to tell me which
> environment variables or commands to run, and which values to expect,
> but any information you could provide would help.

I'm switching back and forth from Xorg to wayland and I'm
tinkering with different desktops/WMs anyways.
I would be happy to help!
I will try wallpaper.el with gnome tomorrow.
If there are any things you want me
to test, just let me know.





  reply	other threads:[~2022-09-14 22:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 20:20 bug#57781: missing wallpaper command Felix
2022-09-14  5:41 ` Stefan Kangas
2022-09-14 17:00   ` Sean Whitton
2022-09-14 22:51     ` Stefan Kangas
2022-09-14 22:51       ` Felix [this message]
2022-09-14 23:22         ` Stefan Kangas
2022-09-15  9:47           ` Felix
2022-09-16 21:09             ` Stefan Kangas
2022-09-17 12:00               ` Felix
2022-09-17 17:48                 ` Stefan Kangas
2022-09-18 11:16                   ` Felix
2022-09-19  9:40                     ` Stefan Kangas
2022-09-18 22:19                   ` Felix
2022-09-19  9:40                     ` Stefan Kangas
2022-09-19 17:19                       ` Felix
2022-09-19 19:16                         ` Stefan Kangas
2022-09-19 19:26                           ` Felix
2022-09-19 20:07                             ` Stefan Kangas
2022-09-19 21:04                               ` Felix
2022-09-15 10:37           ` Felix
2022-09-16 21:09             ` Stefan Kangas
2022-09-16 15:50           ` Thierry Volpiatto
2022-09-16 20:52             ` Stefan Kangas
2022-09-17  6:14               ` Thierry Volpiatto
2022-09-17 18:34                 ` Stefan Kangas
2022-09-18  3:33                   ` Thierry Volpiatto
2022-10-04  5:58         ` Stefan Kangas
     [not found]           ` <87v8owv8lc.fsf@web.de>
2022-10-07  9:08             ` Stefan Kangas
2022-10-07 19:55               ` Felix
2022-10-07 20:16                 ` Stefan Kangas
2022-09-14 23:25       ` Sean Whitton
2022-09-14 13:50 ` bug#57781: wbg " Felix
2022-09-14 16:27   ` Stefan Kangas
2022-09-14 20:01     ` Felix
2022-09-14 23:06       ` Stefan Kangas

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87a671h861.fsf@web.de \
    --to=felix.dick@web.de \
    --cc=57781@debbugs.gnu.org \
    --cc=spwhitton@spwhitton.name \
    --cc=stefankangas@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/emacs.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).