nushell: nushell crashed in Windows Terminal when running the `help` command

Describe the bug When running the help command in nushell, I see the following output, followed by a crash:

C:\Users\Lucre> help
Welcome to Nushell.

Here are some tips to help you get started.
  * help commands - list all available commands
  * help <command name> - display help about a particular command

Nushell works on the idea of a "pipeline". Pipelines are commands connected with the '|' character.
Each stage in the pipeline works together to load, parse, and display information to you.

[Examples]

List the files in the current directory, sorted by size:
    ls | sort-by size

Get information about the current system:
    sys | get host

Get the processes on your system actively using CPU:
    ps | where cpu > 0

You can also learn more at https://www.nushell.sh/book/
Error: Io(Os { code: 87, kind: InvalidInput, message: "The parameter is incorrect." })

This error seems to only occur in Windows Terminal, not in the older powershell.exe or cmd.exe. Additionally, this error only seems to occur with help, with no arguments; there is no such issue when running ls, ps, or help commands.

Whatever the problem is, it seems to have something to do with echoing non-table content; I get the same crash behavior when I run echo hello, but not when I run echo, echo hello world, or ^echo hello.

To Reproduce Steps to reproduce the behavior:

  1. Run help or echo hello in Windows Terminal

Expected behavior The command should complete without the shell crashing

Screenshots image

Configuration (please complete the following information):

  • OS (e.g. Windows): Windows 10, Version 2004, Build 19041.450
  • Terminal: Windows Terminal 1.2.2381.0
  • Nu version (you can use the version command to find out): 0.18.1

Add any other context about the problem here.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (10 by maintainers)

Most upvoted comments

I’d say fairly confident. While it’s possible it’s something else, we’ve seen this error come from rustyline a number of times in the past.