Skip to content

Commit aa8320d

Browse files
knottioknottio
committed
fix: fix broken links
1 parent 3e9ea31 commit aa8320d

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

‎book/configuration.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ prev:
33
text: Nu as a Shell
44
link: /book/nu_as_a_shell.md
55
---
6+
67
# Configuration
78

89
## Quickstart
@@ -116,7 +117,7 @@ Other users may prefer a "modular" configuration where each file handles a small
116117
`config.nu` is commonly used to:
117118

118119
- Set [environment variables](#set-environment-variables) for Nushell and other applications
119-
- Set Nushell settings in [`$env.config`](#nushell-settings-in-the-envconfig-record)
120+
- Set Nushell settings in [`$env.config`](#nushell-settings-in-the-env-config-record)
120121
- Load modules or source files so that their commands are readily available
121122
- Run any other applications or commands at startup
122123

@@ -581,10 +582,10 @@ The following stages and their steps _may_ occur during startup, based on the fl
581582
| 18. | (config files) (plugin) | Processes the signatures in the user's `plugin.msgpackz` (located in the configuration directory) so that added plugins can be used in the following config files. |
582583
| 19. | (config files) | If this is the first time Nushell has been launched, then it creates the configuration directory. "First launch" is determined by whether or not the configuration directory exists. |
583584
| 20. | (config files) | Also, if this is the first time Nushell has been launched, creates a mostly empty (other than a few comments) `env.nu` and `config .nu` in that directory. |
584-
| 21. | (config files) (default_env.nu) | Loads default environment variables from the internal `default_env.nu`. This file can be viewed with: `config env --default \| nu-highlight \| less -R`. |
585+
| 21. | (config files) (default_env.nu) | Loads default environment variables from the internal `default_env.nu`. This file can be viewed with: `config env --default \| nu-highlight \| less -R`. |
585586
| 22. | (config files) (env.nu) | Converts the `PATH` variable into a list so that it can be accessed more easily in the next step. |
586587
| 23. | (config files) (env.nu) | Loads (parses and evaluates) the user's `env.nu` (the path to which was determined above). |
587-
| 24. | (config files) (config.nu) | Loads a minimal `$env.config` record from the internal `default_config.nu`. This file can be viewed with: `config nu --default \| nu-highlight \| less -R`. Most values that are not defined in `default_config.nu` will be auto-populated into `$env.config` using their internal defaults as well. |
588+
| 24. | (config files) (config.nu) | Loads a minimal `$env.config` record from the internal `default_config.nu`. This file can be viewed with: `config nu --default \| nu-highlight \| less -R`. Most values that are not defined in `default_config.nu` will be auto-populated into `$env.config` using their internal defaults as well. |
588589
| 25. | (config files) (config.nu) | Loads (parses and evaluates) the user's `config.nu` (the path to which was determined above). |
589590
| 26. | (config files) (login) | When Nushell is running as a login shell, loads the user's `login.nu`. |
590591
| 27. | (config files) | Loops through the vendor autoload directories and loads any `.nu` files found. The directories are processed in the order found in `$nu.vendor-autoload-dirs`, and files in those directories are processed in alphabetical order. |

‎book/custom_commands.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ prev:
33
text: Programming in Nu
44
link: /book/programming_in_nu.md
55
---
6+
67
# Custom Commands
78

89
As with any programming language, you'll quickly want to save longer pipelines and expressions so that you can call them again easily when needed.
@@ -158,7 +159,7 @@ In this case, the final expression is the `match` statement which can return:
158159

159160
- `null` if the directory is empty
160161
- Otherwise, a `record` representing the randomly chosen file
161-
:::
162+
:::
162163

163164
## Custom Commands and Pipelines
164165

@@ -191,7 +192,7 @@ my-ls | get name
191192
# => ╰───┴───────────────────────╯
192193
```
193194

194-
This lets us easily build custom commands and process their output. Remember that we don't use return statements like other languages. Instead, the [implicit return](#returning-values-from-a-command) allows us to build pipelines that output streams of data that can be connected to other pipelines.
195+
This lets us easily build custom commands and process their output. Remember that we don't use return statements like other languages. Instead, the [implicit return](#returning-values-from-commands) allows us to build pipelines that output streams of data that can be connected to other pipelines.
195196

196197
::: tip Note
197198
The `ls` content is still streamed in this case, even though it is in a separate command. Running this command against a long-directory on a slow (e.g., networked) filesystem would return rows as they became available.

‎book/modules/creating_modules.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ Only definitions marked with `export` (or `export-env` for environment variables
6464
An export cannot have the same name as that of the module itself.
6565
:::
6666

67-
In the [Basic Example](#basic-module-example) above, we had a module named `inc` with a command named `increment`. However, if we rename that file to `increment.nu`, it will fail to import.
67+
In the [Basic Example](#simple-module-example) above, we had a module named `inc` with a command named `increment`. However, if we rename that file to `increment.nu`, it will fail to import.
6868

6969
```nu
7070
mv inc.nu increment.nu

0 commit comments

Comments
 (0)