use ansi escape codes for command output

Author: cptpiepmatz

blog/2025-09-02-nushell_0_107_0.md

@@ -67,27 +67,31 @@ Previously, `find` would always split multi-line input strings, making it imposs
 
 Before:
 
-```nu
-"hello\nworld" | find -mr 'lo\swo'
-# => no output
+```ansi
+> "hello\nworld" | find -mr 'lo\swo'
+╭────────────╮
+│ empty list │
+╰────────────╯
 ```
 
 After:
 
-```nu
-"hello\nworld" | find -mr 'lo\swo'
-# => hello
-# => world
+```ansi
+[38;5;14m> [32m"hello\nworld"[39m [1m[35m|[22m[39m [1m[36mfind[22m[39m [1m[34m-mr[22m[39m [32m'lo\swo'[39m
+hel[41mlo
+wo[49mrl[0m
 ```
 
 ### `random dice` moved to `std`
 
 The `random dice` command has been rewritten in Nushell and moved to the standard library. The `random dice` built-in is still available with a deprecation error, but will be removed in 0.108. The new command can be used as follows:
 
-```nushell
-use std/random
-
-random dice
+```ansi
+> use std/random
+> random dice
+╭───┬───╮
+│ 0 │ 6 │
+╰───┴───╯
 ```
 
 It's behavior, parameters, and defaults are the same.
@@ -97,16 +101,21 @@ It's behavior, parameters, and defaults are the same.
 When `null` is passed to the `each` command, it now returns `null` instead of passing `null` to the closure.
 For example, before this change:
 
-```nu
-→ null | each { "something" }
-something
+```ansi
+> null | each { "something" } | describe
+string
+> null | each { "something" }
+something
+>
 ```
 
 But after this change:
 
-```nu
-→ null | each { "something" }
-null
+```ansi
+> null | each { "something" } | describe
+nothing
+> null | each { "something" }
+>
 ```
 
 ### Execution Order of Hooks Changed: `env_change` _before_ `pre_prompt`
@@ -134,12 +143,12 @@ open -r tests/fixtures/formats/jt.xml
 
 Before this change, this would return:
 
-```
-╭───┬─────────╮
-│ # │ false() │
+```ansi
+[37m╭───┬─────────╮
+│[39m [1m[32m#[22m[39m [37m│[39m [1m[32mfalse()[22m[39m [37m│
 ├───┼─────────┤
-│ 0 │ false   │
-╰───┴─────────╯
+│[39m [1m[32m0[22m[39m [37m│[39m [96mfalse[39m   [37m│
+╰───┴─────────╯[0m
 ```
 
 Now, this will just return `false`.
@@ -178,23 +187,23 @@ open -r tests/fixtures/formats/jt.xml
 
 While the most popular architectures use little endian, many people are used to reading binary numbers as little endian. However, until now, if you were in a little endian system, you would get:
 
-```nushell
-~> 258 | format bits
-00000010 00000001
+```ansi
+[38;5;14m> [1m[35m258[22m[39m [1m[35m|[22m[39m [1m[36mformat bits[22m[39m
+00000010 00000001[0m
 ```
 
 If you copied and pasted that as a number, you would get a surprising result:
 
-```nushell
-~> 0b00000010_00000001
-513
+```ansi
+[38;5;14m> [1m[35m0b00000010_00000001[22m[39m
+513[0m
 ```
 
 Now, `format bits` always formats in big endian:
 
-```nushell
-~> 258 | format bits
-00000001 00000010
+```ansi
+[38;5;14m> [1m[35m258[22m[39m [1m[35m|[22m[39m [1m[36mformat bits[22m[39m
+00000001 00000010[0m
 ```
 
 ### Add active column to `overlay list`
@@ -275,60 +284,76 @@ The `stor create/insert/open` and `query db` commands now support JSON and JSONB
 
 Here's an example of storing a simple table inside a `stor` database, and retrieving it as structured data with `query db`:
 
-```nushell
+```ansi
 # create a table named my_table with a JSON column named data
-stor create -t my_table -c {data: json}
+> stor create -t my_table -c {data: json}
+╭──────────┬────────────────╮
+│ my_table │ [list 0 items] │
+╰──────────┴────────────────╯
 
 # inset a row into the data column containing a table
-{data: [1 2 3]} | stor insert -t my_table
+> {data: [1 2 3]} | stor insert -t my_table
+╭──────────┬───────────────────╮
+│          │ ╭───┬───────────╮ │
+│ my_table │ │ # │   data    │ │
+│          │ ├───┼───────────┤ │
+│          │ │ 0 │ ╭───┬───╮ │ │
+│          │ │   │ │ 0 │ 1 │ │ │
+│          │ │   │ │ 1 │ 2 │ │ │
+│          │ │   │ │ 2 │ 3 │ │ │
+│          │ │   │ ╰───┴───╯ │ │
+│          │ ╰───┴───────────╯ │
+╰──────────┴───────────────────╯
 
 # retrieve the data column from the table as structured data
-stor open | query db "select data from my_table"
-# => ╭───┬───────────╮
-# => │ # │   data    │
-# => ├───┼───────────┤
-# => │ 0 │ ╭───┬───╮ │
-# => │   │ │ 0 │ 1 │ │
-# => │   │ │ 1 │ 2 │ │
-# => │   │ │ 2 │ 3 │ │
-# => │   │ ╰───┴───╯ │
-# => ╰───┴───────────╯
+[38;5;14m> [1m[36mstor open[22m[39m [1m[35m|[22m[39m [1m[36mquery db[22m[39m [32m"select data from my_table"[39m
+╭───┬───────────╮
+│ [1m[32m#[22m[39m │   [1m[32mdata[22m[39m    │
+├───┼───────────┤
+│ [1m[32m0[22m[39m │ ╭───┬───╮ │
+│   │ │ [1m[32m0[22m[39m │ 1 │ │
+│   │ │ [1m[32m1[22m[39m │ 2 │ │
+│   │ │ [1m[32m2[22m[39m │ 3 │ │
+│   │ ╰───┴───╯ │
+╰───┴───────────╯[0m
 ```
 
 ### New `random choice` command in `std-rfc`
 
 The `random choice` command has been added as a new candidate for our standard library. This command can randomly sample a number of elements from a list:
 
-```nushell
-use std-rfc/random
-[1 2 3 4 5] | random choice 2
-# => ╭───┬───╮
-# => │ 0 │ 3 │
-# => │ 1 │ 2 │
-# => ╰───┴───╯
+```ansi
+[38;5;14m> [1m[36muse[22m[39m [32mstd-rfc/random[38;5;14m
+> [1m[36m[[35m1[36m [35m2[36m [35m3[36m [35m4[36m [35m5[36m][22m[39m [1m[35m|[22m[39m [1m[36mrandom choice[22m[39m [1m[35m2[22m[39m
+╭───┬───╮
+│ [1m[32m0[22m[39m │ 1 │
+│ [1m[32m1[22m[39m │ 3 │
+╰───┴───╯[0m
 ```
 
 ### Add `str align` to `std-rfc/str`
 
 The `std-rfc/str` module has new command in this release, `str align`. This command will look for a substring (such as a delimiter), and add padding so that it is in the same column in all lines. It can also take a range to only align any number of lines.
 
-```nushell
-[ "one = 1", "two = 2", "three = 3", "four = 4", "five = 5" ] | str align '='
-# => one   = 1
-# => two   = 2
-# => three = 3
-# => four  = 4
-# => five  = 5
+```ansi
+> use std-rfc/str
+> [ "one = 1", "two = 2", "three = 3", "four = 4", "five = 5" ] | str align '='
+one   = 1
+two   = 2
+three = 3
+four  = 4
+five  = 5
 ```
 
 ### Spread `null` into collections or arguments
 
 `null` values can be used with the spread operator (`...`), behaving as if they were empty lists or records (whichever is appropriate for its place)
 
-```nushell
-[ 1 2 ...(null) ] == [ 1 2 ]
-
-{ a:1 b:2 ...(null) } == { a:1 b:2 }
+```ansi
+> [ 1 2 ...(null) ] == [ 1 2 ]
+true
+> { a:1 b:2 ...(null) } == { a:1 b:2 }
+true
 ```
 
 ### `get`, `select`, `reject` can `--ignore-case` of cell-path
@@ -371,13 +396,13 @@ If you're using any of the `--output-*` switches, and want `string_value` column
 
 Previously, converting values to `binary` with `into binary` could only do so in the native endianness of your platform. Using native endianness is still the default, but with the `--endian` flag, you get to choose:
 
-```nushell
-258 | into binary --endian little
-# => Length: 8 (0x8) bytes | printable whitespace ascii_other non_ascii
-# => 00000000:   02 01 00 00  00 00 00 00
-258 | into binary --endian big
-# => Length: 8 (0x8) bytes | printable whitespace ascii_other non_ascii
-# => 00000000:   00 00 00 00  00 00 01 02
+```ansi
+[38;5;14m> [1m[35m258[22m[39m [1m[35m|[22m[39m [1m[36minto binary[22m[39m [1m[34m--endian[22m[39m [32mlittle[39m
+Length: 8 (0x8) bytes | [1m[36mprintable [32mwhitespace [35mascii_other [33mnon_ascii[22m[36m
+00000000[39m:   [1m[35m02[22m[39m [1m[35m01[22m[39m [38;5;242m00[39m [38;5;242m00[39m  [38;5;242m00[39m [38;5;242m00[39m [38;5;242m00[39m [38;5;242m00[39m                             [1m[35m••[22m[38;5;242m000000[38;5;14m
+> [1m[35m258[22m[39m [1m[35m|[22m[39m [1m[36minto binary[22m[39m [1m[34m--endian[22m[39m [32mbig[39m
+Length: 8 (0x8) bytes | [1m[36mprintable [32mwhitespace [35mascii_other [33mnon_ascii[22m[36m
+00000000[39m:   [38;5;242m00[39m [38;5;242m00[39m [38;5;242m00[39m [38;5;242m00[39m  [38;5;242m00[39m [38;5;242m00[39m [1m[35m01[22m[39m [1m[35m02[22m[39m                             [38;5;242m000000[1m[35m••[0m
 ```
 
 Note that this only affects `int`, `float`, `filesize`, `bool` and `duration` (i.e. it does not affect `string`s, `date`s and `binary`). Likewise, only the individual elements in `table`s and `record`s are affected (not the `table` or `record` itself)
@@ -402,12 +427,12 @@ Note that this only affects `int`, `float`, `filesize`, `bool` and `duration` (i
 
 The `http` subcommands can now maintain a list of redirects when using the `--full` flag. This will be stored in a new `urls` column:
 
-```nushell
-http get --full http://nushell.sh | get urls
-# => ╭───┬────────────────────────╮
-# => │ 0 │ http://nushell.sh/     │
-# => │ 1 │ http://www.nushell.sh/ │
-# => ╰───┴────────────────────────╯
+```ansi
+[38;5;14m> [1m[36mhttp get[22m[39m [1m[34m--full[22m[39m [32mhttp://nushell.sh[39m [1m[35m|[22m[39m [1m[36mget[22m[39m [32murls[39m
+╭───┬────────────────────────╮
+│ [1m[32m0[22m[39m │ http://nushell.sh/     │
+│ [1m[32m1[22m[39m │ http://www.nushell.sh/ │
+╰───┴────────────────────────╯[0m
 ```
 
 > TODO(release-notes): make sure the callout below is in the correct format for the blog
@@ -481,41 +506,46 @@ http get --full --allow-errors http://localhost:1234
 
 Previously, the help text for a missing flag would list all of them, which could get verbose on a single line:
 
-```nushell
-~> ls --full-path
-Error: nu::parser::unknown_flag
-
-  × The `ls` command doesn't have flag `full-path`.
-   ╭─[entry #8:1:4]
- 1 │ ls --full-path
-   ·    ─────┬─────
-   ·         ╰── unknown flag
-   ╰────
-  help: Available flags: --help(-h), --all(-a), --long(-l), --short-names(-s), --full-paths(-f), --du(-d), --directory(-D), --mime-type(-m), --threads(-t). Use
-        `--help` for more information.
+```ansi
+[38;5;14m> [1m[36mls[22m[39m [1m[34m--full-path[22m[39m
+Error: [31mnu::parser::unknown_flag
+[39m
+  [31m×[39m The `ls` command doesn't have flag `full-path`.
+   ╭─[[1m[4m[36mentry #26:1:4[22m[24m[39m]
+ [2m1[22m │ ls --full-path
+   · [1m[35m   ─────┬─────[22m[39m
+   ·         [1m[35m╰── unknown flag[22m[39m
+   ╰────[36m
+  help: [39mAvailable flags: --help(-h), --all(-a), --long(-l), --short-names(-s), --full-paths(-f), --du(-d),
+        --directory(-D), --mime-type(-m), --threads(-t). Use `--help` for more information.[0m
 ```
 
 The new error message only suggests the closest flag:
 
-```nushell
-> ls --full-path
-Error: nu::parser::unknown_flag
-
-  × The `ls` command doesn't have flag `full-path`.
-   ╭─[entry #23:1:4]
- 1 │ ls --full-path
-   ·    ─────┬─────
-   ·         ╰── unknown flag
-   ╰────
-  help: Did you mean: `--full-paths`?
+```ansi
+[38;5;14m> [1m[36mls[22m[39m [1m[34m--full-path[22m[39m
+Error: [31mnu::parser::unknown_flag
+[39m
+  [31m×[39m The `ls` command doesn't have flag `full-path`.
+   ╭─[[1m[4m[36mentry #45:1:4[22m[24m[39m]
+ [2m1[22m │ ls --full-path
+   · [1m[35m   ─────┬─────[22m[39m
+   ·         [1m[35m╰── unknown flag[22m[39m
+   ╰────[36m
+  help: [39mDid you mean: `--full-paths`?[0m
 ```
 
 ### Improved default color theme
 
 We changed the default theme to use the ANSI default color (`39m`) instead of white (`37m`).  
 This finally makes the default theme usable in the context of light terminal color settings. On dark terminal palettes this change should have no impact.
 
-<img width="1351" height="507" alt="Comparison of white vs default color on Solarized Light theme" src="https://github.com/user-attachments/assets/db80fe07-0cea-4a4b-ba14-e6a31f29cfe1" />
+Comparison of white vs default color on Solarized Light theme, before and after:
+
+<p align="center">
+  <img src="https://gist.githubusercontent.com/Bahex/08c6b780df1685ea3fa2c472e6d9b7d5/raw/705b102ccdef4faef48f0f1c2a9a5723858b1ccb/theme-before.svg" width="50%" />
+  <img src="https://gist.githubusercontent.com/Bahex/08c6b780df1685ea3fa2c472e6d9b7d5/raw/705b102ccdef4faef48f0f1c2a9a5723858b1ccb/theme-after.svg" width="50%" />
+</p>
 
 ### Reset content type for commands returning partial input
 
@@ -626,34 +656,32 @@ internal-alias; external-alias; unresolvable-alias
 
 Previously `detect columns` created records (rows) with duplicate key names under some circumstances. The resulting table behaved inconsistently with different commands:
 
-```nushell
-let data = "meooooow cat\nkitty kitty woof"
-$data | detect columns
-# => ╭───┬──────────┬───────╮
-# => │ # │ meooooow │  cat  │
-# => ├───┼──────────┼───────┤
-# => │ 0 │ kitty    │ kitty │
-# => ╰───┴──────────┴───────╯
-
-$data | detect columns | get 0.cat
-# => woof
+```ansi
+> let data = "meooooow cat\nkitty kitty woof"
+> $data | detect columns
+╭───┬──────────┬───────╮
+│ # │ meooooow │  cat  │
+├───┼──────────┼───────┤
+│ 0 │ kitty    │ kitty │
+╰───┴──────────┴───────╯
+> $data | detect columns | get 0.cat
+woof
 ```
 
 Now, this will result in an error suggesting using `detect columns --guess` or `parse`:
 
-```nushell
-let data = "meooooow cat\nkitty kitty woof"
-$data | detect columns
-# => Error: nu::shell::failed_to_detect_columns
-# =>
-# =>   × Failed to detect columns
-# =>    ╭─[entry #2:3:1]
-# =>  2 │
-# =>  3 │ $data | detect columns
-# =>    · ──┬──   ───────┬──────
-# =>    ·   │            ╰── tried to detect columns here
-# =>    ·   ╰── value coming from here
-# =>    ╰────
+```ansi
+> let data = "meooooow cat\nkitty kitty woof"
+> $data | detect columns
+Error: nu::shell::failed_to_detect_columns
+
+  × Failed to detect columns
+   ╭─[entry #48:1:1]
+ 1 │ $data | detect columns
+   · ──┬──   ───────┬──────
+   ·   │            ╰── tried to detect columns here
+   ·   ╰── value coming from here
+   ╰────
 ```
 
 ### Improve errors for subcommands without a corresponding parent command