unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Cairn <cairn@pm.me>, 57052@debbugs.gnu.org
Subject: bug#57052: elogind-service specifies a variable that's ignored by defualt
Date: Mon, 08 Aug 2022 12:45:10 +0200	[thread overview]
Message-ID: <8b93b5ce9f1c9caab7a65fcc672dddd24c7ad373.camel@ist.tugraz.at> (raw)
In-Reply-To: <1MoJ5UI-6FMbpR2WSMjNbdVXZd4GisV-Dl1HPuLfgYLOQYl4Udg7HLNR8NDmZ47slyi4grIwH93xXL8xORLxUo4O80MR34q3wLXMmnktYH8=@pm.me>

Am Sonntag, dem 07.08.2022 um 23:29 +0000 schrieb Cairn:
> "HandleLidSwitchExternalPower= is completely ignored by default (for
> backwards compatibility)"[1]
> 
> I noticed (with help in IRC) that my laptop wasn't suspending on lid
> close when plugged in and charging, which I hadn't seen happen on
> other systems. I now know that I can set this by configuring the
> `elogind-service` parameter `handle-lid-switch-external-power`.
> Regardless, it seems like it should default to being unset rather
> than set/ignored, since that would heed the line I quoted above.
I think you're misreading that line.  What it states is not that
"HandleLidSwitchExternalPower" is ignored by default, but
"HandleLidSwitchExternalPower=" is ignored by default, i.e. there will
be no value unless one was provided (whichever semantics "no value" has
later on) is only confusingly explained later on.

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.

Cheers




  reply	other threads:[~2022-08-08 11:14 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 [this message]
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
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=8b93b5ce9f1c9caab7a65fcc672dddd24c7ad373.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=57052@debbugs.gnu.org \
    --cc=cairn@pm.me \
    /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).