unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: desktop-background.el as a new library?
Date: Wed, 27 Oct 2021 21:02:32 +0200	[thread overview]
Message-ID: <87y26ee0gz.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnGyc+CuJCZBUN8zVzYDf00kfy28GtcMw97E2DUFBq=Uw@mail.gmail.com>

Stefan Kangas <stefan@marxist.se> writes:

Hi Stefan,

> Please see the attached tentative diff for image-dired.el to get an
> idea.  (Please ignore the somewhat unwieldy defcustoms; I followed the
> scheme in image-dired.el and intend to clean that up.)
>
> Maybe this will even work automagically on other operating systems
> than GNU/Linux, if the commands it uses has been ported to them.

None of the provided commands will work for wayland compositors (I
think) which are becoming more and more the standard on GNU/Linux.  For
example, I'm using sway so when $WAYLAND_DISPLAY and $SWAYSOCK are set,
the background must be set using the swaybg command.  Similarly, with
GNOME, I'd say it's generally the best bet to set the wallpaper using
gsettings because that will work with both GNOME on X11 and GNOME on
Wayland.  But with gsettings, the set wallpaper would be persistent
whereas all other commands would set the wallpaper only for the current
session.

That said, I like the idea.  It's just that the program for setting the
wallpaper is not necessarily a user preference (defcustom) but can also
be a necessity dictated by the WM/compositor/platform.

Bye,
Tassilo



  reply	other threads:[~2021-10-27 19:02 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 16:41 desktop-background.el as a new library? Stefan Kangas
2021-10-27 19:02 ` Tassilo Horn [this message]
2021-10-27 19:51   ` Stefan Kangas
2021-10-28  2:36     ` Po Lu
2021-10-29 17:26 ` Arthur Miller
2021-10-29 17:44   ` Stefan Kangas
2021-11-15 20:51     ` Arthur Miller
2022-09-13 16:28 ` New library wallpaper.el pushed to master Stefan Kangas
2022-09-13 16:54   ` Eli Zaretskii
2022-09-13 17:09     ` Stefan Kangas
2022-09-13 17:22       ` Eli Zaretskii
2022-09-14  7:13         ` Stefan Kangas
2022-09-14  7:36           ` Stefan Kangas
2022-09-14  7:36           ` Po Lu
2022-09-14 11:10           ` Stefan Kangas
2022-09-14 11:44           ` Eli Zaretskii
2022-09-14 12:01             ` Stefan Kangas
2022-09-15 16:48               ` Stefan Kangas
2022-09-15 11:59           ` Eli Zaretskii
2022-09-15 13:39             ` Po Lu
2022-09-15 13:44               ` Eli Zaretskii
2022-09-15 13:49                 ` Po Lu
2022-09-14  2:46   ` Po Lu
2022-09-14  6:39     ` Po Lu
2022-09-14  7:04       ` Stefan Kangas
2022-09-14  7:33         ` Po Lu
2022-09-14 11:53           ` Stefan Kangas
2022-09-14 12:30             ` Stefan Kangas
2022-09-14 13:42             ` Po Lu
2022-09-14 16:58           ` Sean Whitton
2022-09-15  7:28             ` Stefan Kangas
2022-09-15 16:19               ` Sean Whitton
2022-09-16  1:27                 ` Po Lu
2022-09-14 11:39       ` Eli Zaretskii
2022-09-14 11:52         ` Stefan Kangas
2022-09-14 12:01           ` Eli Zaretskii
2022-09-14 12:07             ` Stefan Kangas
2022-09-14 12:24             ` Po Lu
2022-09-14 12:41               ` 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=87y26ee0gz.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).