From: Cairn via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
"57052@debbugs.gnu.org" <57052@debbugs.gnu.org>
Subject: bug#57052: elogind-service specifies a variable that's ignored by defualt
Date: Tue, 09 Aug 2022 06:42:38 +0000 [thread overview]
Message-ID: <Hn1ZMO3EcuXfolkFXd2euaROYzm7lwKwbIgeQ82pjNGbM68RunaCTpULgweXApiDu8ghd_lYyC4ntDAwaIezrahGq55_FQnT9VCXwsQ19_c=@pm.me> (raw)
In-Reply-To: <8b93b5ce9f1c9caab7a65fcc672dddd24c7ad373.camel@ist.tugraz.at>
[-- Attachment #1.1: Type: text/plain, Size: 746 bytes --]
(Resending this email, since I forgot to add the debugs.gnu.org address as a recipient)
> IMHO the Guix behaviour of always setting a value is the right one
> (explicit is better than implicit after all). As for the default
> values, one might disagree as to which fits, but I don't think ignoring
> lid switches while powered is harmful.
That's fair!
Well, if explicitly setting variables is the standard, then I suggest changing `handle-lid-switch-external-power` to the same value as `handle-lid-switch` ("suspend"). I agree that the current setting isn't harmful, but this change would match the default, unconfigured behavior of `elogind`. It would also be more consistent with other distros' defaults from what I've experienced.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 855 bytes --]
next prev parent reply other threads:[~2022-08-09 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 23:29 bug#57052: elogind-service specifies a variable that's ignored by defualt Cairn via Bug reports for GNU Guix
2022-08-08 10:45 ` Liliana Marie Prikler
2022-08-09 1:52 ` bokr
2022-08-09 6:34 ` Liliana Marie Prikler
2022-08-09 6:42 ` Cairn via Bug reports for GNU Guix [this message]
2022-08-09 13:52 ` Maxim Cournoyer
2022-08-09 13:57 ` Maxim Cournoyer
2022-08-09 14:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-08-09 14:42 ` Cairn via Bug reports for GNU Guix
2022-08-10 4:38 ` Maxim Cournoyer
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='Hn1ZMO3EcuXfolkFXd2euaROYzm7lwKwbIgeQ82pjNGbM68RunaCTpULgweXApiDu8ghd_lYyC4ntDAwaIezrahGq55_FQnT9VCXwsQ19_c=@pm.me' \
--to=bug-guix@gnu.org \
--cc=57052@debbugs.gnu.org \
--cc=cairn@pm.me \
--cc=liliana.prikler@ist.tugraz.at \
/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).