From: Marius Bakke <marius@gnu.org>
To: Brett Gilio <brettg@gnu.org>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 42516@debbugs.gnu.org
Subject: [bug#42516] [PATCH] doc: Extend tlp-service-type example.
Date: Sat, 25 Jul 2020 19:21:10 +0200 [thread overview]
Message-ID: <877durse7t.fsf@gnu.org> (raw)
In-Reply-To: <871rl0frpo.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
Brett Gilio <brettg@gnu.org> writes:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>
>> @deffn {Scheme Variable} tlp-service-type
>> -The service type for the TLP tool. Its value should be a valid
>> -TLP configuration (see below). To use the default settings, simply
>> -write:
>> +The service type for the TLP tool. The default settings are optimised
>> +for battery life on most systems, but you can tweak them to your heart's
>> +content by passing a valid @code{tlp-configuration} as its value:
>> @lisp
>> -(service tlp-service-type)
>> +(service tlp-service-type
>> + (tlp-configuration
>> + (cpu-scaling-governor-on-ac (list "performance"))
>> + (sched-powersave-on-bat? #t)))
>> @end lisp
>> @end deffn
>>
>> -By default TLP does not need much configuration but most TLP parameters
>> -can be tweaked using @code{tlp-configuration}.
>> -
>> Each parameter definition is preceded by its type; for example,
>> @samp{boolean foo} indicates that the @code{foo} parameter
>> should be specified as a boolean. Types starting with
>
> I would replace "as its value:" with "to the service type:", so it reads
> "... but you can tweak them to your heart's content by passing a valid
> tlp-configuration to the service type:"
Something about "tweak to your heart's content" rubs me the wrong way,
though I can't really explain why. It feels like the manual is
passive-aggressively mocking me for trying to understand how to
configure the thing. But that's probably just me. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-25 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:43 [bug#42516] [PATCH] doc: Extend tlp-service-type example Tobias Geerinckx-Rice via Guix-patches via
2020-07-24 22:55 ` Brett Gilio
2020-07-25 17:21 ` Marius Bakke [this message]
2020-07-25 19:54 ` Tobias Geerinckx-Rice via Guix-patches via
2020-07-25 21:00 ` Marius Bakke
2020-07-29 13:23 ` bug#42516: " Tobias Geerinckx-Rice via Guix-patches via
2020-07-25 18:45 ` [bug#42516] " Tobias Geerinckx-Rice via Guix-patches via
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=877durse7t.fsf@gnu.org \
--to=marius@gnu.org \
--cc=42516@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=me@tobias.gr \
/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).