Skip to content

Add inline code fencing in v0.112.1 post #2150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hustcer merged 1 commit into from
Apr 12, 2026
Merged

Add inline code fencing in v0.112.1 post #2150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions blog/2026-04-11-nushell_v0_112_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -469,7 +469,7 @@ Now you see this output in the `--testbin` section of the help.

### Added support for parsing `hh:mm:ss` formatted strings in `into duration` <JumpToc/> <PrBy :pr="17781" user="fdncred" />

Added the ability to parse `h:m:s` with `into datetime` with optional .mmm for millis, .mmmmmm for micros, and .mmmmmmmmm for nanos.
Added the ability to parse `h:m:s` with `into datetime` with optional `.mmm` for millis, `.mmmmmm` for micros, and `.mmmmmmmmm` for nanos.

It has to be in the format of `h:m:s`:

Expand All @@ -494,7 +494,7 @@ When it is, it should just work:
3hr 34min
```

When minutes or seconds >= 60 there are errors:
When minutes or seconds >= `60` there are errors:

```ansi :no-line-numbers
> "3:61:0" | into duration
Expand Down