From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53466@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#53466] [PATCH v2] home: Add redshift service.
Date: Tue, 01 Feb 2022 09:36:36 +0100 [thread overview]
Message-ID: <87v8xz6l0r.fsf@gnu.org> (raw)
In-Reply-To: <091b93b3f04fe083d9fd0b798523a272fb623ce4.camel@telenet.be> (Maxime Devos's message of "Sun, 30 Jan 2022 18:43:18 +0100")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> Ludovic Courtès schreef op zo 30-01-2022 om 16:11 [+0100]:
>> +@item @code{location-provider} (default: @code{geoclue2}) (type: symbol)
>> +Geolocation provider---@code{'manual} or @code{'geoclue2}. In the
>> +former case, you must also specify the @code{latitude} and
>> +@code{longitude} fields so Redshift can determine daytime at your place.
>> +In the latter case, the Geoclue system service must be running; it will
>> +be queried for location information.
>> +
>> +@item @code{adjustment-method} (default: @code{randr}) (type: symbol)
>> +Color adjustment method.
>
> It would be nice to document which color adjustment methods exist,
> as done for 'location-provider'.
Good idea, will do.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-02-01 8:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 11:11 [bug#53466] [PATCH] home: Add redshift service Ludovic Courtès
2022-01-28 10:34 ` Andrew Tropin
2022-01-28 18:37 ` Ludovic Courtès
2022-01-31 18:22 ` Andrew Tropin
2022-02-01 9:15 ` Ludovic Courtès
2022-02-02 6:59 ` Andrew Tropin
2022-02-02 8:57 ` Andrew Tropin
2022-02-08 9:22 ` Ludovic Courtès
2022-03-13 9:52 ` Andrew Tropin
2022-01-30 15:11 ` [bug#53466] [PATCH v2] " Ludovic Courtès
2022-01-30 17:43 ` Maxime Devos
2022-02-01 8:36 ` Ludovic Courtès [this message]
2022-01-31 18:57 ` Andrew Tropin
2022-02-01 8:43 ` Ludovic Courtès
2022-02-02 7:48 ` Andrew Tropin
2022-02-06 23:13 ` bug#53466: [PATCH] " Ludovic Courtès
2022-02-07 15:16 ` [bug#53466] " Andrew Tropin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8xz6l0r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53466@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=maximedevos@telenet.be \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.