Fix tip syntax

Author: 132ikl

blog/2025-07-23-nushell_0_106_0.md

@@ -182,22 +182,24 @@ If you want to opt in and try them out yourself, you can enable them in the foll
   nu --experimental-options=[reorder-cell-paths,..]
   ```
 
-> [!Tip] Live on the edge
-> If you want to have all available experimental options on, rather than specifying them one by one, you can just use `all`!
-
-> [!Note] Enabling experimental options
-> If you use Nushell as your default shell in your terminal emulator, simply add whatever experimental options you'd like in your terminal config.
-
-> On the other hand, if you use Nushell as your login shell, a quick (if not the most elegant) way to set this up is to put this snippet into your config (this example uses `all`):
->
-> ```nushell
-> if $nu.is-login and $env.NU_EXPERIMENTAL_OPTIONS? != "all" {
->     $env.NU_EXPERIMENTAL_OPTIONS = "all"
->     exec $nu.current-exe
-> }
-> ```
->
-> The first time your login shell runs, this snippet will relaunch it with the `NU_EXPERIMENTAL_OPTIONS` environment variable set. This will ensure that any child processes of your login shell will also have the experimental options set.
+::: tip Live on the edge
+If you want to have all available experimental options on, rather than specifying them one by one, you can just use `all`!
+:::
+
+::: note Enabling experimental options
+If you use Nushell as your default shell in your terminal emulator, simply add whatever experimental options you'd like in your terminal config.
+
+On the other hand, if you use Nushell as your login shell, a quick (if not the most elegant) way to set this up is to put this snippet into your config (this example uses `all`):
+
+```nushell
+if $nu.is-login and $env.NU_EXPERIMENTAL_OPTIONS? != "all" {
+    $env.NU_EXPERIMENTAL_OPTIONS = "all"
+    exec $nu.current-exe
+}
+```
+
+The first time your login shell runs, this snippet will relaunch it with the `NU_EXPERIMENTAL_OPTIONS` environment variable set. This will ensure that any child processes of your login shell will also have the experimental options set.
+:::
 
 #### Our first experimental option: `reorder-cell-paths`
 
@@ -352,59 +354,60 @@ There will of course be long deprecation period to avoid breaking existing code.
 
 Implemented by [@Bahex] in [#16007].
 
-> [!Tip]
-> Nushell currently doesn't have a great way to disable deprecation warnings for code that might not be yours. If you have issues with integrations which are not updated with this and don't want to see the deprecation warnings, you can add a small wrapper around `get` to squelch the warnings as a workaround.
->
-> **Please note that this will also disable the warnings for your own scripts!** Use this with caution.
->
-> Here's a small example demonstrating the concept:
->
-> ```nushell
-> alias get-builtin = get
-> def get [--optional (-o), --ignore-errors (-i), --sensitive (-s), cell_path: cell-path, ...rest: cell-path] {
->   get-builtin --optional=($optional or $ignore_errors) $cell_path ...$rest
->
-> ```
->
-> **To actually use this**, here is a more fully featured version with documentation and examples. You can put this in your `env.nu` to silence the warnings:
->
-> <details>
-> <summary>Click here to expand code</summary>
->
-> ```nushell
-> alias get-builtin = get
->
-> # Extract data using a cell path.
-> #
-> # This is equivalent to using the cell path access syntax: `$env.OS` is the same as `$env | get OS`.
-> #
-> # If multiple cell paths are given, this will produce a list of values.
-> @example "Get an item from a list" { [0 1 2] | get 1 } --result 1
-> @example "Get a column from a table" { [{A: A0}] | get A } --result [A0]
-> @example "Get a cell from a table" { [{A: A0}] | get 0.A } --result A0
-> @example "Extract the name of the 3rd record in a list (same as `ls | $in.name.2`)" { ls | get name.2 }
-> @example "Extract the name of the 3rd record in a list" { ls | get 2.name }
-> @example "Getting Path/PATH in a case insensitive way" { $env | get paTH! }
-> @example "Getting Path in a case sensitive way, won't work for `PATH`" { $env | get Path }
-> def get [
->   --optional (-o) # make all cell path members optional (returns null for missing values),
->   --ignore-errors (-i) # ignore missing data (make all cell path members optional) (deprecated),
->   --sensitive (-s) # get path in a case sensitive manner (deprecated),
->   cell_path: cell-path # The cell path to the data.
->   ...rest: cell-path # Additional cell paths.
-> ]: [
->   list<any> -> any,
->   table -> any,
->   record -> any,
->   nothing -> nothing
-> ] {
->   get-builtin --optional=($optional or $ignore_errors) --sensitive=$sensitive $cell_path ...$rest
-> }
-> ```
->
-> </details>
->
-> _This workaround was inspired by [@JoaquinTrinanes]'s [similar workaround](https://github.com/nix-community/home-manager/pull/7490). Thanks for the inspiration!_
+::: tip
+Nushell currently doesn't have a great way to disable deprecation warnings for code that might not be yours. If you have issues with integrations which are not updated with this and don't want to see the deprecation warnings, you can add a small wrapper around `get` to squelch the warnings as a workaround.
+
+**Please note that this will also disable the warnings for your own scripts!** Use this with caution.
+
+Here's a small example demonstrating the concept:
+
+```nushell
+alias get-builtin = get
+def get [--optional (-o), --ignore-errors (-i), --sensitive (-s), cell_path: cell-path, ...rest: cell-path] {
+  get-builtin --optional=($optional or $ignore_errors) $cell_path ...$rest
+
+```
+
+**To actually use this**, here is a more fully featured version with documentation and examples. You can put this in your `env.nu` to silence the warnings:
+
+<details>
+<summary>Click here to expand code</summary>
+
+```nushell
+alias get-builtin = get
+
+# Extract data using a cell path.
+#
+# This is equivalent to using the cell path access syntax: `$env.OS` is the same as `$env | get OS`.
+#
+# If multiple cell paths are given, this will produce a list of values.
+@example "Get an item from a list" { [0 1 2] | get 1 } --result 1
+@example "Get a column from a table" { [{A: A0}] | get A } --result [A0]
+@example "Get a cell from a table" { [{A: A0}] | get 0.A } --result A0
+@example "Extract the name of the 3rd record in a list (same as `ls | $in.name.2`)" { ls | get name.2 }
+@example "Extract the name of the 3rd record in a list" { ls | get 2.name }
+@example "Getting Path/PATH in a case insensitive way" { $env | get paTH! }
+@example "Getting Path in a case sensitive way, won't work for `PATH`" { $env | get Path }
+def get [
+  --optional (-o) # make all cell path members optional (returns null for missing values),
+  --ignore-errors (-i) # ignore missing data (make all cell path members optional) (deprecated),
+  --sensitive (-s) # get path in a case sensitive manner (deprecated),
+  cell_path: cell-path # The cell path to the data.
+  ...rest: cell-path # Additional cell paths.
+]: [
+  list<any> -> any,
+  table -> any,
+  record -> any,
+  nothing -> nothing
+] {
+  get-builtin --optional=($optional or $ignore_errors) --sensitive=$sensitive $cell_path ...$rest
+}
+```
+
+</details>
+
+_This workaround was inspired by [@JoaquinTrinanes]'s [similar workaround](https://github.com/nix-community/home-manager/pull/7490). Thanks for the inspiration!_
+:::
 
 <!-- ## Removals -->