colorize some examples

Author: Bahex

blog/2025-10-14-nushell_v0_108_0.md

@@ -889,16 +889,18 @@ If you are manually building Nushell without default features (`cargo build --no
 ### Improved error messages for binary literals
 Previously, a generic shell error is thrown for invalid binary strings. Now, an improve error message is thrown for invalid binary, hexadecimal, and octal strings.
 ```nushell
-> 0b[121]
-# => Error: nu::parser::invalid_binary_string
-# => 
-# => × Invalid binary string.
-# =>   ╭─[entry #1:1:1]
-# => 1 │ 0b[121]
-# =>   · ───┬───
-# =>   ·    ╰── invalid binary string
-# =>   ╰────
-# =>  help: binary strings may contain only 0 or 1.
+0b[121]
+```
+```ansi:no-line-numbers
+Error: nu::parser::invalid_binary_string
+
+  × Invalid binary string.
+   ╭─[entry #3:1:1]
+ 1 │ 0b[121]
+   · ───┬───
+   ·    ╰── invalid binary string
+   ╰────
+  help: binary strings may contain only 0 or 1.
 ```
 
 ### Polars 50.1 upgrade
@@ -927,31 +929,32 @@ toolkit run pr <number>
 
 ### Additional changes
 
-* The `which` command now lists all commands (internal and external) when no application parameter is passed to it ([#16551](https://github.com/nushell/nushell/pull/16551))
+* The `which` command now lists all commands (internal and external) when no argument is passed to it ([#16551](https://github.com/nushell/nushell/pull/16551))
+
 ## Bug fixes
 
 ### Discard `path add` input
-Previously `std path add` could fail if it was fed `any` input. Example:
-
-```console
-❯ ls | each {} | path add
-Error: nu::shell::incompatible_parameters
+Previously `path add` (from `std/util`) could fail if it was fed `any` input.
+```ansi:no-line-numbers
+[96m> [22;1;36muse[22;39m [32mstd/util[39m [32m'path add'
+[96m> [22;1;36mls[22;39m [22;1;35m|[22;39m [22;1;36meach[22;39m [22;1;32m{}[22;39m [22;1;35m|[22;39m [22;1;36mpath add
+[22;39mError: [31mnu::shell::incompatible_parameters
 
-  × Incompatible parameters.
-    ╭─[std/util/mod.nu:18:17]
- 17 │ ]: [nothing -> nothing, nothing -> list<path>] {
- 18 │     let span = (metadata $paths).span
-    ·                 ────┬─── ───┬──
-    ·                     │       ╰── but a positional metadata expression was also given
-    ·                     ╰── pipeline input was provided
- 19 │     let paths = $paths | flatten
-    ╰────
+[39m  [31m×[39m Incompatible parameters.
+    ╭─[[22;1;36;4mstd/util/mod.nu:18:17[22;39;24m]
+ [22;2m17[22m │ ]: [nothing -> nothing, nothing -> list<path>] {
+ [22;2m18[22m │     let span = (metadata $paths).span
+    · [22;1;35m                ────┬───[33m ───┬──
+[22;39m    ·                     [22;1;35m│[22;39m       [22;1;33m╰── but a positional metadata expression was also given
+[22;39m    ·                     [22;1;35m╰── pipeline input was provided
+[22;39m [22;2m19[22m │     let paths = $paths | flatten
+    ╰────[0m
 ```
 
-Now any input to `std path add` will be discarded. It's still possible to pass it with `$in`:
+Now any input to `path add` will be discarded. It's still possible to pass it with `$in`:
 
 ```nushell
-[a b c] | each {|p| $env.HOME | path join $p } | std path add $in
+[a b c] | each {|p| $env.HOME | path join $p } | path add $in
 ```
 
 ### Aliases are now expanded before being sent to external completers
@@ -1001,14 +1004,6 @@ get_type # list<any> -> list<record<baz: int>>
 
 Previously this error wasn't caught during compilation, and manifested as a runtime error when the execution reached the invalid `break`/`continue` call.
 
-::: center
-
-Hello
-
-Hi
-
-:::
-
 ```ansi:no-line-numbers title="Before"
 > let fn = { break }
 > do $fn