Skip to content

Commit e8e326b

Browse files
committed
README: rm hardwraps, let editors wrap lines automatically
Manual hardwrap of human text considered harmful, especially in the document files.
1 parent 4e35c08 commit e8e326b

File tree

1 file changed

+5
-12
lines changed

1 file changed

+5
-12
lines changed

README.md

Lines changed: 5 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,7 @@ Enter REPL:
5151
hnix --repl
5252
```
5353
54-
To evaluate an expression and make it available in the REPL
55-
as the `input` variable use
56-
54+
To evaluate an expression and make it available in the REPL as the `input` variable use:
5755
```
5856
hnix --eval -E '(import <nixpkgs> {}).pkgs.hello' --repl
5957
```
@@ -62,8 +60,7 @@ Use the `:help` command for a list of all available REPL commands.
6260
6361
## Building with full debug info
6462
65-
To build `hnix` for debugging, and with full tracing output and stack traces,
66-
use:
63+
To build `hnix` for debugging, and with full tracing output and stack traces, use:
6764
6865
```
6966
nix-shell
@@ -72,8 +69,7 @@ cabal v2-build
7269
cabal v2-run hnix -- -v5 --trace <args> +RTS -xc
7370
```
7471
75-
Note that this will run quite slowly, but will give the most information as to
76-
what might potentially be going wrong during parsing or evaluation.
72+
Note that this will run quite slowly, but will give the most information as to what might potentially be going wrong during parsing or evaluation.
7773
7874
## Building with benchmarks enabled
7975
@@ -99,8 +95,7 @@ cabal v2-run hnix -- <args> +RTS -p
9995
10096
## Using the Cachix binary cache
10197
102-
If you're on macOS, you can use the binary cache at Cachix to avoid building
103-
the specific dependencies used by hnix. Just use these commands:
98+
If you're on macOS, you can use the binary cache at Cachix to avoid building the specific dependencies used by hnix. Just use these commands:
10499
105100
```
106101
nix-env -iA cachix -f https://github.com/NixOS/nixpkgs/tarball/db557aab7b690f5e0e3348459f2e4dc8fd0d9298
@@ -124,9 +119,7 @@ Please, check that all tests that were passing prior (most probably all tests me
124119
125120
### Evaluating Nixpkgs with HNix
126121
127-
Currently the main high-level goal is to be able to evaluate all of Nixpkgs. To
128-
run this yourself, first build `hnix` with `nix-build`, then run the following
129-
command:
122+
Currently the main high-level goal is to be able to evaluate all of Nixpkgs. To run this yourself, first build `hnix` with `nix-build`, then run the following command:
130123
131124
```
132125
./result/bin/hnix --eval -E "import <nixpkgs> {}" --find

0 commit comments

Comments
 (0)