From 8896ba80a41645bca1199110851ed6725238ed3d Mon Sep 17 00:00:00 2001 From: Darren Schroeder <343840+fdncred@users.noreply.github.com> Date: Sat, 31 May 2025 08:04:46 -0500 Subject: [PATCH] make sure new nul chars don't print in `char --list` (#15858) # Description This PR fixes and oversight. When we added `nul`, `null_byte`, and `zero_byte` we forgot to make them non-printable for `char --list`. That's what this PR fixes. # User-Facing Changes # Tests + Formatting # After Submitting --- crates/nu-command/src/strings/char_.rs | 3 +++ 1 file changed, 3 insertions(+) diff --git a/crates/nu-command/src/strings/char_.rs b/crates/nu-command/src/strings/char_.rs index bcc35a45c9..d3061e08fd 100644 --- a/crates/nu-command/src/strings/char_.rs +++ b/crates/nu-command/src/strings/char_.rs @@ -164,6 +164,9 @@ static NO_OUTPUT_CHARS: LazyLock> = LazyLock::new(|| { [ // If the character is in the this set, we don't output it to prevent // the broken of `char --list` command table format and alignment. + "nul", + "null_byte", + "zero_byte", "newline", "enter", "nl",