You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2025-09-02-nushell_0_107_0.md
+26-15Lines changed: 26 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,14 +52,14 @@ The `find` command is now case-sensitive by default in all modes. Previously, yo
52
52
53
53
This change makes the different modes of `find` more consistent. It also makes `find` more consistent with other parts of Nushell, such as `where`'s `=~` operator and the recent [case-sensitive cell-paths change](https://www.nushell.sh/blog/2025-06-10-nushell_0_105_0.html#case-sensitive-cell-paths-or-not-toc).
54
54
55
-
> TODO(release-notes): make sure this callout renders correctly on the blog
55
+
::: tip
56
+
If you want `find` to still be case-insensitive after this release, which might be desirable for interactive usage, you can add an alias to your config:
56
57
57
-
> [!TIP]
58
-
> If you want `find` to still be case-insensitive after this release, which might be desirable for interactive usage, you can add an alias to your config:
59
-
>
60
-
> ```nu
61
-
> alias find = find -i
62
-
> ```
58
+
```nu
59
+
alias find = find -i
60
+
```
61
+
62
+
:::
63
63
64
64
### New behavior for `find --multiline`
65
65
@@ -201,12 +201,10 @@ Now, `format bits` always formats in big endian:
201
201
202
202
`overlay list` now returns table instead of list of overlays. Before, only active overlays were included in `overlay list`. Now, hidden overlays will be included as well, and there is a column indicating whether a given overlay is hidden or not.
203
203
204
-
> TODO(release-notes): make sure this call out is formatted correctly for the blog
205
-
206
-
> [!TIP]
207
-
> The ordering of `overlay list` is still preserved. If you run `overlay list | last`, you will still get the most recently activated overlay.
208
-
>
209
-
> For migrating to the new behavior, you can update any usages of `overlay list | last` to `overlay list | last | get name`.
204
+
::: tip
205
+
The ordering of `overlay list` is still preserved. If you run `overlay list | last`, you will still get the most recently activated overlay.
206
+
For migrating to the new behavior, you can update any usages of `overlay list | last` to `overlay list | last | get name`.
207
+
:::
210
208
211
209
## Additions
212
210
@@ -225,6 +223,9 @@ With the new [watch --debounce option](#new-watch-duration-option-toc), the `--d
225
223
226
224
`nu --testbin` has a new flag `-h` to show available \<bins\>
227
225
226
+
<details>
227
+
<p>
228
+
228
229
```
229
230
> nu --testbin -h
230
231
Usage: nu --testbin <bin>
@@ -247,6 +248,9 @@ repeat_bytes -> A version of repeater that can output binary data, even null byt
247
248
repeater -> Repeat a string or char N times(e.g: nu --testbin repeater a 5)
248
249
```
249
250
251
+
</p>
252
+
</details>
253
+
250
254
### New keybinding: `vichangemode`
251
255
252
256
You can now set bindings which change the Vi mode.
@@ -267,7 +271,7 @@ The available modifiers and keycodes, remain limited to single character binding
267
271
268
272
### JSON column support for `stor` and `query db`
269
273
270
-
The 'stor create/insert/open' and 'query db' commands now support JSON and JSONB columns. This lets you store more kinds of structured data directly inside of an SQLite database without an explicit `to`/`from` step.
274
+
The `stor create/insert/open` and `query db` commands now support JSON and JSONB columns. This lets you store more kinds of structured data directly inside of an SQLite database without an explicit `to`/`from` step.
271
275
272
276
Here's an example of storing a simple table inside a `stor` database, and retrieving it as structured data with `query db`:
273
277
@@ -559,7 +563,14 @@ Here's a before/after comparison:
559
563
560
564
`help` command used to trim the outputs of examples, which could result in inconsistent white space:
561
565
562
-
> Following snippets are generated with this config `$env.config.table = {mode: light, padding: {left: 1}, header_on_separator: false}`
566
+
::: info
567
+
Following snippets are generated with this config:
0 commit comments