You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/content/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ First, you need to instantiate wrapper-manager's lib. This can be done by pullin
107
107
108
108
### Classic
109
109
110
-
Wrapper-manager can be pulled in a classic (non-flake) setup for a devshell or nixos configuration, like so:
110
+
Wrapper-manager can be pulled in a classic (non-flake) setup for a dev-shell or NixOS configuration, like so:
111
111
112
112
```nix
113
113
# shell.nix
@@ -139,7 +139,7 @@ in {
139
139
Now that you already have `wrapper-manager` in scope, you need to evaluate `wrapper-manager.lib`. The argument is an attrset with following elements:
140
140
141
141
-`pkgs`: your nixpkgs instance used to bring `symlinkJoin` and `makeWrapper`, as well as passing it through the modules for convenience.
142
-
-`modules`: a list of wrapper-manager modules. As with NixOS, a module can be passed as a path to a module or directly. A proper module is either an attset, or a function to attrset.
142
+
-`modules`: a list of wrapper-manager modules. As with NixOS, a module can be passed as a path to a module or directly. A proper module is either an attrset, or a function to attrset.
143
143
-`specialArgs` (optional): extra arguments passed to the module system.
144
144
145
145
A convenience shorthand for `(wrapper-manager.lib {...}).config.build.toplevel` is available through: `wrapper-manager.lib.build {}`, which is probably what you want in 99% of the cases.
@@ -164,7 +164,7 @@ A convenience shorthand for `(wrapper-manager.lib {...}).config.build.toplevel`
164
164
# => «derivation /nix/store/...»
165
165
```
166
166
167
-
For example, if you want to use wrapper-manager in the context of a devshell, you can instatiate it directly like so:
167
+
For example, if you want to use wrapper-manager in the context of a dev-shell, you can instantiate it directly like so:
168
168
```nix
169
169
# pkgs and wrapper-manager in scope, see previous steps
170
170
# ...
@@ -194,7 +194,7 @@ mkShell {
194
194
195
195
These are some examples of wrapper-manager used in the wild. Feel free to PR yours.
0 commit comments