Expected behavior of `.1sec`? Inconsistent highlighting of float, duration, filesize?
Open
Nobody has claimed this yet.
status:needs-triage
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 79
Description
Bug report form
- I have done a basic search of the issue tracker to find any existing issues that are similar.
- I have checked that my version is at least the latest stable release available via my installation method.
Describe the bug
Essentially 2 related issues here:
- Not sure if it's a bug, but if
.1is a float, I'd expect.1secto be parsed as duration - The following highlighting might be caused by incorrect customization, but we better provide a mechanism to prevent it
Basically I mean 1. in 1.sec should be highlighted as float, otherwise why not highlighting all number shapes in the same way?
How to reproduce
Type commands mentioned above in the REPL.
Expected behavior
More consistent behavior
Configuration
| key | value |
|---|---|
| version | 0.111.0 |
| major | 0 |
| minor | 111 |
| patch | 0 |
| branch | |
| commit_hash | |
| build_os | macos-aarch64 |
| build_target | aarch64-apple-darwin |
| rust_version | rustc 1.93.1 (01f6ddf75 2026-02-11) (Homebrew) |
| cargo_version | cargo 1.93.1 (Homebrew) |
| build_time | 2026-02-28 23:22:43 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, mcp, network, plugin, rustls-tls, sqlite, trash-support |
| installed_plugins | |
| experimental_options | example=false, reorder-cell-paths=true, pipefail=true, enforce-runtime-annotations=false, native-clip=false |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the .1sec and 1.sec examples in the Nushell REPL using the reported 0.111.0 configuration, and inspect the parsing and highlighting entry points involved. Clarify the intended treatment of floats, durations, and filesizes, then add coverage for the agreed behavior and verify the REPL output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100