mirror of
https://github.com/nix-community/home-manager
synced 2024-12-24 02:39:48 +01:00
treewide: fix typos
This commit is contained in:
parent
c3060ab937
commit
b5c083300b
15 changed files with 38 additions and 39 deletions
|
@ -303,7 +303,7 @@ can be sourced directly by POSIX.2-like shells such as {bash}[Bash] or
|
|||
[NOTE]
|
||||
====
|
||||
By default user packages will not be ignored in favor of
|
||||
`environment.systemPackages`, but they will be intalled to
|
||||
`environment.systemPackages`, but they will be installed to
|
||||
`/etc/profiles/per-user/$USERNAME` if
|
||||
|
||||
[source,nix]
|
||||
|
|
|
@ -7,7 +7,7 @@ Home Manager includes a `flake.nix` file for compatibility with {nixos-wiki-flak
|
|||
The support is still experimental and may change in backwards incompatible ways.
|
||||
|
||||
[[sec-flakes-prerequisties]]
|
||||
=== Prerequisties
|
||||
=== Prerequisites
|
||||
|
||||
* Install Nix 2.4 or later, or have it in `nix-shell`.
|
||||
|
||||
|
|
|
@ -39,19 +39,19 @@ with lib;
|
|||
default = null;
|
||||
description = ''
|
||||
This optional key is used as a hint to <literal>launchctl(1)</literal> that it should not submit this job to launchd when
|
||||
loading a job or jobs. The value of this key does NOT reflect the current state of the job on the run-ning running
|
||||
ning system. If you wish to know whether a job is loaded in launchd, reading this key from a configura-tion configuration
|
||||
tion file yourself is not a sufficient test. You should query launchd for the presence of the job using
|
||||
loading a job or jobs. The value of this key does NOT reflect the current state of the job on the running
|
||||
system. If you wish to know whether a job is loaded in launchd, reading this key from a configuration
|
||||
file yourself is not a sufficient test. You should query launchd for the presence of the job using
|
||||
the <literal>launchctl(1)</literal> list subcommand or use the ServiceManagement framework's
|
||||
<literal>SMJobCopyDictionary()</literal> method.
|
||||
|
||||
Note that as of Mac OS X v10.6, this key's value in a configuration file conveys a default value, which
|
||||
is changed with the [-w] option of the <literal>launchctl(1)</literal> load and unload subcommands. These subcommands no
|
||||
longer modify the configuration file, so the value displayed in the configuration file is not necessar-ily necessarily
|
||||
ily the value that <literal>launchctl(1)</literal> will apply. See <literal>launchctl(1)</literal> for more information.
|
||||
longer modify the configuration file, so the value displayed in the configuration file is not necessarily
|
||||
the value that <literal>launchctl(1)</literal> will apply. See <literal>launchctl(1)</literal> for more information.
|
||||
|
||||
Please also be mindful that you should only use this key if the provided on-demand and KeepAlive crite-ria criteria
|
||||
ria are insufficient to describe the conditions under which your job needs to run. The cost to have a
|
||||
Please also be mindful that you should only use this key if the provided on-demand and KeepAlive criteria
|
||||
are insufficient to describe the conditions under which your job needs to run. The cost to have a
|
||||
job loaded in launchd is negligible, so there is no harm in loading a job which only runs once or very
|
||||
rarely.
|
||||
'';
|
||||
|
@ -147,8 +147,7 @@ with lib;
|
|||
type = types.nullOr types.bool;
|
||||
default = null;
|
||||
description = ''
|
||||
This flag causes launchd to use the <literal>glob(3)</literal> mechanism to update the program arguments before invoca-tion. invocation.
|
||||
tion.
|
||||
This flag causes launchd to use the <literal>glob(3)</literal> mechanism to update the program arguments before invocation.
|
||||
'';
|
||||
};
|
||||
|
||||
|
@ -236,12 +235,12 @@ with lib;
|
|||
description = ''
|
||||
This optional key is used to control whether your job is to be kept continuously running or to let
|
||||
demand and conditions control the invocation. The default is false and therefore only demand will start
|
||||
the job. The value may be set to true to unconditionally keep the job alive. Alternatively, a dictio-nary dictionary
|
||||
nary of conditions may be specified to selectively control whether launchd keeps a job alive or not. If
|
||||
the job. The value may be set to true to unconditionally keep the job alive. Alternatively, a dictionary
|
||||
of conditions may be specified to selectively control whether launchd keeps a job alive or not. If
|
||||
multiple keys are provided, launchd ORs them, thus providing maximum flexibility to the job to refine
|
||||
the logic and stall if necessary. If launchd finds no reason to restart the job, it falls back on
|
||||
demand based invocation. Jobs that exit quickly and frequently when configured to be kept alive will
|
||||
be throttled to converve system resources.
|
||||
be throttled to conserve system resources.
|
||||
'';
|
||||
};
|
||||
|
||||
|
@ -677,8 +676,8 @@ with lib;
|
|||
XPC connections. See <literal>xpc_transaction_begin(3)</literal> for details.
|
||||
|
||||
Interactive
|
||||
Interactive jobs run with the same resource limitations as apps, that is to say, none. Interac-tive Interactive
|
||||
tive jobs are critical to maintaining a responsive user experience, and this key should only be
|
||||
Interactive jobs run with the same resource limitations as apps, that is to say, none. Interactive
|
||||
jobs are critical to maintaining a responsive user experience, and this key should only be
|
||||
used if an app's ability to be responsive depends on it, and cannot be made Adaptive.
|
||||
'';
|
||||
};
|
||||
|
@ -687,8 +686,8 @@ with lib;
|
|||
type = types.nullOr types.bool;
|
||||
default = null;
|
||||
description = ''
|
||||
When a job dies, launchd kills any remaining processes with the same process group ID as the job. Set-ting Setting
|
||||
ting this key to true disables that behavior.
|
||||
When a job dies, launchd kills any remaining processes with the same process group ID as the job. Setting
|
||||
this key to true disables that behavior.
|
||||
'';
|
||||
};
|
||||
|
||||
|
@ -753,9 +752,9 @@ with lib;
|
|||
description = ''
|
||||
This optional key is used to specify launch on demand sockets that can be used to let launchd know when
|
||||
to run the job. The job must check-in to get a copy of the file descriptors using APIs outlined in
|
||||
launch(3). The keys of the top level Sockets dictionary can be anything. They are meant for the appli-cation application
|
||||
cation developer to use to differentiate which descriptors correspond to which application level proto-cols protocols
|
||||
cols (e.g. http vs. ftp vs. DNS...). At check-in time, the value of each Sockets dictionary key will
|
||||
launch(3). The keys of the top level Sockets dictionary can be anything. They are meant for the application
|
||||
developer to use to differentiate which descriptors correspond to which application level protocols
|
||||
(e.g. http vs. ftp vs. DNS...). At check-in time, the value of each Sockets dictionary key will
|
||||
be an array of descriptors. Daemon/Agent writers should consider all descriptors of a given key to be
|
||||
to be effectively equivalent, even though each file descriptor likely represents a different networking
|
||||
protocol which conforms to the criteria specified in the job configuration file.
|
||||
|
@ -829,8 +828,8 @@ with lib;
|
|||
default = null;
|
||||
description = ''
|
||||
This optional key is a variant of SockPathName. Instead of binding to a known path, a securely
|
||||
generated socket is created and the path is assigned to the environment variable that is inher-ited inherited
|
||||
ited by all jobs spawned by launchd.
|
||||
generated socket is created and the path is assigned to the environment variable that is inherited
|
||||
by all jobs spawned by launchd.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
|
@ -202,7 +202,7 @@ in {
|
|||
<citerefentry>
|
||||
<refentrytitle>nix.conf</refentrytitle>
|
||||
<manvolnum>5</manvolnum>
|
||||
</citerefentry> for avalaible options.
|
||||
</citerefentry> for available options.
|
||||
The value declared here will be translated directly to the key-value pairs Nix expects.
|
||||
</para>
|
||||
<para>
|
||||
|
|
|
@ -305,7 +305,7 @@ in {
|
|||
DPI=144
|
||||
;;
|
||||
*)
|
||||
echo "Unknown profle: $AUTORANDR_CURRENT_PROFILE"
|
||||
echo "Unknown profile: $AUTORANDR_CURRENT_PROFILE"
|
||||
exit 1
|
||||
esac
|
||||
|
||||
|
|
|
@ -64,7 +64,7 @@ let
|
|||
id = mkOption {
|
||||
type = strMatching "[a-zA-Z]{32}";
|
||||
description = ''
|
||||
The extension's ID from the Chome Web Store url or the unpacked crx.
|
||||
The extension's ID from the Chrome Web Store url or the unpacked crx.
|
||||
'';
|
||||
default = "";
|
||||
};
|
||||
|
|
|
@ -267,7 +267,7 @@ in {
|
|||
difftastic = {
|
||||
enable = mkEnableOption "" // {
|
||||
description = ''
|
||||
Enable the <command>difft</command> syntax highlighter.
|
||||
Enable the <command>difftastic</command> syntax highlighter.
|
||||
See <link xlink:href="https://github.com/Wilfred/difftastic" />.
|
||||
'';
|
||||
};
|
||||
|
@ -278,7 +278,7 @@ in {
|
|||
example = "dark";
|
||||
description = ''
|
||||
Determines whether difftastic should use the lighter or darker colors
|
||||
for syntax highlithing.
|
||||
for syntax highlighting.
|
||||
'';
|
||||
};
|
||||
|
||||
|
|
|
@ -61,7 +61,7 @@ in {
|
|||
<citerefentry>
|
||||
<refentrytitle>fnott.ini</refentrytitle>
|
||||
<manvolnum>5</manvolnum>
|
||||
</citerefentry> for a list of avaliable options and <link
|
||||
</citerefentry> for a list of available options and <link
|
||||
xlink:href="https://codeberg.org/dnkl/fnott/src/branch/master/fnott.ini"/>
|
||||
for an example configuration.
|
||||
'';
|
||||
|
|
|
@ -109,7 +109,7 @@ let
|
|||
example =
|
||||
"[ \${pkg.sway}/bin/swaymsg workspace 1, move workspace to eDP-1 ]";
|
||||
description = ''
|
||||
Commands executed after the profile is succesfully applied.
|
||||
Commands executed after the profile is successfully applied.
|
||||
Note that if you provide multiple commands, they will be
|
||||
executed asynchronously with no guaranteed ordering.
|
||||
'';
|
||||
|
|
|
@ -129,8 +129,8 @@ in {
|
|||
type = types.nullOr types.str;
|
||||
description = ''
|
||||
Set margin of each edge specified in pixels. Specify single value to
|
||||
apply margin on all sides. Two comma-seperated values will set
|
||||
vertical and horizontal edges seperately. Four comma-seperated will
|
||||
apply margin on all sides. Two comma-separated values will set
|
||||
vertical and horizontal edges separately. Four comma-seperated will
|
||||
give each edge a seperate value.
|
||||
For example: 10,20,5 will set top margin to 10, left and right to 20
|
||||
and bottom to five.
|
||||
|
@ -142,8 +142,8 @@ in {
|
|||
type = types.nullOr types.str;
|
||||
description = ''
|
||||
Set padding of each edge specified in pixels. Specify single value to
|
||||
apply margin on all sides. Two comma-seperated values will set
|
||||
vertical and horizontal edges seperately. Four comma-seperated will
|
||||
apply margin on all sides. Two comma-separated values will set
|
||||
vertical and horizontal edges separately. Four comma-seperated will
|
||||
give each edge a seperate value.
|
||||
For example: 10,20,5 will set top margin to 10, left and right to 20
|
||||
and bottom to five.
|
||||
|
|
|
@ -8,7 +8,7 @@ in {
|
|||
meta.maintainers = [ maintainers.thibautmarty ];
|
||||
|
||||
options.services.poweralertd.enable =
|
||||
mkEnableOption "the Upower-powered power alerterd";
|
||||
mkEnableOption "the Upower-powered power alertd";
|
||||
|
||||
config = mkIf cfg.enable {
|
||||
assertions = [
|
||||
|
|
|
@ -88,7 +88,7 @@ in {
|
|||
{ event = "lock"; command = "lock"; }
|
||||
]
|
||||
'';
|
||||
description = "Run command on occurence of a event.";
|
||||
description = "Run command on occurrence of a event.";
|
||||
};
|
||||
|
||||
extraArgs = mkOption {
|
||||
|
|
|
@ -193,7 +193,7 @@ let
|
|||
# We have to make sure the wrapper does not start a dbus session
|
||||
export DBUS_SESSION_BUS_ADDRESS=1
|
||||
|
||||
# A zero exit code means i3 succesfully validated the configuration
|
||||
# A zero exit code means i3 successfully validated the configuration
|
||||
i3 -c ${configFile} -C -d all || {
|
||||
echo "i3 configuration validation failed"
|
||||
echo "For a verbose log of the failure, run 'i3 -c ${configFile} -C -d all'"
|
||||
|
|
|
@ -33,7 +33,7 @@ in {
|
|||
<refentrytitle>swaynag</refentrytitle>
|
||||
<manvolnum>5</manvolnum>
|
||||
</citerefentry>
|
||||
for a list of avaliable options and an example configuration.
|
||||
for a list of available options and an example configuration.
|
||||
Note, configurations declared under <literal><config></literal>
|
||||
will override the default type values of swaynag.
|
||||
'';
|
||||
|
|
|
@ -50,7 +50,7 @@ in {
|
|||
AppleMetricUnits = mkNullableEnableOption "the metric system";
|
||||
|
||||
NSAutomaticCapitalizationEnabled =
|
||||
mkNullableEnableOption "automatic captilization";
|
||||
mkNullableEnableOption "automatic capitalization";
|
||||
|
||||
NSAutomaticDashSubstitutionEnabled =
|
||||
mkNullableEnableOption "smart dashes";
|
||||
|
|
Loading…
Reference in a new issue