Move book/commands to commands/commands (#785)

* Move `book/commands` to `commands/commands`

* Move `commands/commands` to `commands/docs`

* Address review comments

---------

Co-authored-by: Justin Ma <[email protected]>

Author: Hofer-Julian

.prettierignore

@@ -6,7 +6,7 @@ operators.md
 dataframes.md
 nushell_map.md
 *_bash*.md
-book/commands/*.md
+commands/docs/*.md
 .vuepress/.temp
 .vuepress/.cache
 .vuepress/dist/

.vuepress/configs/sidebar/en.ts

@@ -104,34 +104,34 @@ export const sidebarEn: SidebarConfig = {
       text: 'Commands',
       collapsible: false,
       children: [
-        'bits.md',
-        'bytes.md',
-        'conversions.md',
-        'core.md',
-        'database.md',
-        'dataframe.md',
-        'date.md',
-        'default.md',
-        'deprecated.md',
-        'env.md',
-        'experimental.md',
-        'expression.md',
-        'filesystem.md',
-        'filters.md',
-        'formats.md',
-        'generators.md',
-        'hash.md',
-        'lazyframe.md',
-        'math.md',
-        'misc.md',
-        'network.md',
-        'platform.md',
-        'prompt.md',
-        'random.md',
-        'shells.md',
-        'strings.md',
-        'system.md',
-        'viewers.md',
+        '/commands/categories/bits.md',
+        '/commands/categories/bytes.md',
+        '/commands/categories/conversions.md',
+        '/commands/categories/core.md',
+        '/commands/categories/database.md',
+        '/commands/categories/dataframe.md',
+        '/commands/categories/date.md',
+        '/commands/categories/default.md',
+        '/commands/categories/deprecated.md',
+        '/commands/categories/env.md',
+        '/commands/categories/experimental.md',
+        '/commands/categories/expression.md',
+        '/commands/categories/filesystem.md',
+        '/commands/categories/filters.md',
+        '/commands/categories/formats.md',
+        '/commands/categories/generators.md',
+        '/commands/categories/hash.md',
+        '/commands/categories/lazyframe.md',
+        '/commands/categories/math.md',
+        '/commands/categories/misc.md',
+        '/commands/categories/network.md',
+        '/commands/categories/platform.md',
+        '/commands/categories/prompt.md',
+        '/commands/categories/random.md',
+        '/commands/categories/shells.md',
+        '/commands/categories/strings.md',
+        '/commands/categories/system.md',
+        '/commands/categories/viewers.md',
       ],
     },
   ],

book/coloring_and_theming.md

@@ -392,7 +392,7 @@ Coloring of the prompt is controlled by the `block` in `PROMPT_COMMAND` where yo
 
 ## `LS_COLORS` colors for the `ls` command
 
-Nushell will respect and use the `LS_COLORS` environment variable setting on Mac, Linux, and Windows. This setting allows you to define the color of file types when you do a [`ls`](commands/ls.md). For instance, you can make directories one color, _.md markdown files another color, _.toml files yet another color, etc. There are a variety of ways to color your file types.
+Nushell will respect and use the `LS_COLORS` environment variable setting on Mac, Linux, and Windows. This setting allows you to define the color of file types when you do a [`ls`](/commands/docs/ls.md). For instance, you can make directories one color, _.md markdown files another color, _.toml files yet another color, etc. There are a variety of ways to color your file types.
 
 There's an exhaustive list [here](https://github.com/trapd00r/LS_COLORS), which is overkill, but gives you an rudimentary understanding of how to create a ls_colors file that `dircolors` can turn into a `LS_COLORS` environment variable.
 

book/configuration.md

@@ -34,7 +34,7 @@ By convention, this variable is defined in the `config.nu` file.
 
 ### Environment
 
-You can set environment variables for the duration of a Nushell session using [`let-env`](commands/let-env.html) calls inside the `env.nu` file. For example:
+You can set environment variables for the duration of a Nushell session using [`let-env`](/commands/docs/let-env.html) calls inside the `env.nu` file. For example:
 
 ```
 let-env FOO = 'BAR'
@@ -77,7 +77,7 @@ You can build the full set of environment variables by running Nu inside of anot
 > env | each { |it| echo $"let-env ($it.name) = '($it.raw)'" } | str join (char nl)
 ```
 
-This will print out [`let-env`](commands/let-env.html) lines, one for each environment variable along with its setting.
+This will print out [`let-env`](/commands/docs/let-env.html) lines, one for each environment variable along with its setting.
 
 Next, on some distros you'll also need to ensure Nu is in the /etc/shells list:
 
@@ -106,7 +106,7 @@ There is an environment variable `$nu.loginshell-path` containing the path to th
 ### macOS: Keeping `/usr/bin/open` as `open`
 
 Some tools (e.g. Emacs) rely on an `open` command to open files on Mac.
-As Nushell has its own [`open`](commands/open.md) command which has different semantics and shadows `/usr/bin/open`, these tools will error out when trying to use it.
+As Nushell has its own [`open`](/commands/docs/open.md) command which has different semantics and shadows `/usr/bin/open`, these tools will error out when trying to use it.
 One way to work around this is to define a custom command for Nushell's `open` and create an alias for the system's `open` in your `config.nu` file like this:
 
 ```
@@ -116,13 +116,13 @@ alias open = ^open
 
 ## PATH configuration
 
-In Nushell, [the PATH environment variable](<https://en.wikipedia.org/wiki/PATH_(variable)>) (Path on Windows) is a list of paths. To append a new path to it, you can use [`let-env`](commands/let-env.html) and [`append`](commands/append.html) in `env.nu`:
+In Nushell, [the PATH environment variable](<https://en.wikipedia.org/wiki/PATH_(variable)>) (Path on Windows) is a list of paths. To append a new path to it, you can use [`let-env`](/commands/docs/let-env.html) and [`append`](/commands/docs/append.html) in `env.nu`:
 
 ```
 let-env PATH = ($env.PATH | split row (char esep) | append '/some/path')
 ```
 
-This will append `/some/path` to the end of PATH; you can also use [`prepend`](commands/prepend.html) to add entries to the start of PATH.
+This will append `/some/path` to the end of PATH; you can also use [`prepend`](/commands/docs/prepend.html) to add entries to the start of PATH.
 
 Note the `split row (char esep)` step. We need to add it because in `env.nu`, the environment variables inherited from the host process are still strings. The conversion step of environment variables to Nushell values happens after reading the config files (see also the [Environment](environment.html#environment-variable-conversions) section). After that, for example in the Nushell REPL when `PATH`/`Path` is a list , you can use `append`/`prepend` directly.
 

book/custom_commands.md

@@ -318,7 +318,7 @@ Rest parameters can be used together with positional parameters:
 
 ```
 def greet [vip: string, ...name: string] {
-  $"hello to our VIP ($vip)" 
+  $"hello to our VIP ($vip)"
   "and hello to everybody else:"
   for $n in $name {
     $n
@@ -399,13 +399,13 @@ Custom commands stream their output just like built-in commands. For example, le
 > ls | get name
 ```
 
-Let's move [`ls`](commands/ls.md) into a command that we've written:
+Let's move [`ls`](/commands/docs/ls.md) into a command that we've written:
 
 ```nushell
 def my-ls [] { ls }
 ```
 
-We can use the output from this command just as we would [`ls`](commands/ls.md).
+We can use the output from this command just as we would [`ls`](/commands/docs/ls.md).
 
 ```
 > my-ls | get name

book/dataframes.md

@@ -93,7 +93,7 @@ We can have a look at the first lines of the file using `first`:
 ### Loading the file
 
 Let's start by comparing loading times between the various methods. First, we
-will load the data using Nushell's [`open`](commands/open.md) command:
+will load the data using Nushell's [`open`](/commands/docs/open.md) command:
 
 ```shell
 > benchmark {open .\Data7602DescendingYearOrder.csv}

book/environment.md

@@ -2,7 +2,7 @@
 
 A common task in a shell is to control the environment that external applications will use. This is often done automatically, as the environment is packaged up and given to the external application as it launches. Sometimes, though, we want to have more precise control over what environment variables an application sees.
 
-You can see the current environment variables using the [`env`](commands/env.html) command:
+You can see the current environment variables using the [`env`](/commands/docs/env.html) command:
 
 ```
    #           name                 type                value                 raw
@@ -25,7 +25,7 @@ The environment is initially created from the Nu [configuration file](configurat
 
 There are several ways to set an environment variable:
 
-### [`let-env`](commands/let-env.html)
+### [`let-env`](/commands/docs/let-env.html)
 
 Using the `let-env` command is the most straightforward method
 
@@ -44,7 +44,7 @@ let-env Path = ($env.Path | prepend 'C:\path\you\want\to\add')
 Here we've prepended our folder to the existing folders in the Path, so it will have the highest priority.
 If you want to give it the lowest priority instead, you can use the `append` command.
 
-### [`load-env`](commands/load-env.html)
+### [`load-env`](/commands/docs/load-env.html)
 
 If you have more than one environment variable you'd like to set, you can use `load-env` to create a table of name/value pairs and load multiple variables at the same time:
 
@@ -57,7 +57,7 @@ If you have more than one environment variable you'd like to set, you can use `l
 These are defined to be active only temporarily for a duration of executing a code block.
 See [Single-use environment variables](environment.md#single-use-environment-variables) for details.
 
-### Calling a command defined with [`def-env`](commands/def-env.md)
+### Calling a command defined with [`def-env`](/commands/docs/def-env.md)
 
 See [Defining environment from custom commands](environment.md#defining-environment-from-custom-commands) for details.
 
@@ -93,7 +93,7 @@ true
 
 ## Changing directory
 
-Common task in a shell is to change directory with the [`cd`](commands/cd.html) command.
+Common task in a shell is to change directory with the [`cd`](/commands/docs/cd.html) command.
 In Nushell, calling `cd` is equivalent to setting the `PWD` environment variable.
 Therefore, it follows the same rules as other environment variables (for example, scoping).
 
@@ -106,14 +106,14 @@ A common shorthand to set an environment variable once is available, inspired by
 BAR
 ```
 
-You can also use [`with-env`](commands/with-env.html) to do the same thing more explicitly:
+You can also use [`with-env`](/commands/docs/with-env.html) to do the same thing more explicitly:
 
 ```
 > with-env { FOO: BAR } { $env.FOO }
 BAR
 ```
 
-The [`with-env`](commands/with-env.html) command will temporarily set the environment variable to the value given (here: the variable "FOO" is given the value "BAR"). Once this is done, the [block](types_of_data.html#blocks) will run with this new environment variable set.
+The [`with-env`](/commands/docs/with-env.html) command will temporarily set the environment variable to the value given (here: the variable "FOO" is given the value "BAR"). Once this is done, the [block](types_of_data.html#blocks) will run with this new environment variable set.
 
 ## Permanent environment variables
 
@@ -129,7 +129,7 @@ let-env FOO = 'BAR'
 ## Defining environment from custom commands
 
 Due to the scoping rules, any environment variables defined inside a custom command will only exist inside the command's scope.
-However, a command defined as [`def-env`](commands/def-env.html) instead of [`def`](commands/def.html) (it applies also to `export def`, see [Modules](modules.md)) will preserve the environment on the caller's side:
+However, a command defined as [`def-env`](/commands/docs/def-env.html) instead of [`def`](/commands/docs/def.html) (it applies also to `export def`, see [Modules](modules.md)) will preserve the environment on the caller's side:
 
 ```
 > def-env foo [] {
@@ -192,15 +192,15 @@ Because `nu` is an external program, Nushell translated the `[ a b c ]` list acc
 Running commands with `nu -c` does not load the config file, therefore the env conversion for `FOO` is missing and it is displayed as a plain string -- this way we can verify the translation was successful.
 You can also run this step manually by `do $env.ENV_CONVERSIONS.FOO.to_string [a b c]`
 
-If we look back at the [`env`](commands/env.html) command, the `raw` column shows the value translated by `ENV_CONVERSIONS.<name>.to_string` and the `value` column shows the value used in Nushell (the result of `ENV_CONVERSIONS.<name>.from_string` in the case of `FOO`).
+If we look back at the [`env`](/commands/docs/env.html) command, the `raw` column shows the value translated by `ENV_CONVERSIONS.<name>.to_string` and the `value` column shows the value used in Nushell (the result of `ENV_CONVERSIONS.<name>.from_string` in the case of `FOO`).
 If the value is not a string and does not have `to_string` conversion, it is not passed to an external (see the `raw` column of `PROMPT_COMMAND`).
 One exception is `PATH` (`Path` on Windows): by default, it converts the string to a list on startup and from a list to a string when running externals if no manual conversions are specified.
 
 _(Important! The environment conversion string -> value happens **after** the env.nu and config.nu are evaluated. All environment variables in env.nu and config.nu are still strings unless you set them manually to some other values.)_
 
 ## Removing environment variables
 
-You can remove an environment variable only if it was set in the current scope via [`hide-env`](commands/hide_env.html):
+You can remove an environment variable only if it was set in the current scope via [`hide-env`](/commands/docs/hide_env.html):
 
 ```
 > let-env FOO = 'BAR'

book/escaping.md

@@ -1,6 +1,6 @@
 # Escaping to the system
 
-Nu provides a set of commands that you can use across different OSes ("internal" commands), and having this consistency is helpful. Sometimes, though, you want to run an external command that has the same name as an internal Nu command. To run the external `ls` or `date` command, for example, you use the caret (^) command. Escaping with the caret prefix calls the command that's in the user's PATH (e.g. `/bin/ls` instead of Nu's internal [`ls`](commands/ls.md) command).
+Nu provides a set of commands that you can use across different OSes ("internal" commands), and having this consistency is helpful. Sometimes, though, you want to run an external command that has the same name as an internal Nu command. To run the external `ls` or `date` command, for example, you use the caret (^) command. Escaping with the caret prefix calls the command that's in the user's PATH (e.g. `/bin/ls` instead of Nu's internal [`ls`](/commands/docs/ls.md) command).
 
 Nu internal command: