Parsing validation fails with bareword containing # in block

[sholderbach]

Describe the bug

On the REPL insert, and try to submit via enter.

1..10 | each {echo nixpkgs#unzip }

This will continue to insert a new line as if the block was not closed.

The basic behavior that a string containing a # is not interpreted as a comment (commonly found in the nix context) still works outside the block:

> echo nixpkgs#unzip
nixpkgs#unzip

The original problem was described in: (#6957, #6335, #8137)
The parsing/lexing change to make it possible came with #8151

How to reproduce

1. In repl
2. Insert

1..10 | each {echo nixpkgs#unzip }

3. cursor at the end
4. Press enter

Expected behavior

Should be a valid expression to submit

Screenshots

No response

Configuration

key	value
version	0.84.0
branch
commit_hash
build_os	linux-x86_64
build_target	x86_64-unknown-linux-gnu
rust_version	rustc 1.72.0 (5680fa18f 2023-08-23)
rust_channel	stable-x86_64-unknown-linux-gnu
cargo_version	cargo 1.72.0 (103a7ff2e 2023-08-15)
build_time	2023-09-11 22:00:27 +02:00
build_rust_channel	release
allocator	standard
features	default, sqlite, trash, which, zip
installed_plugins

Additional context

No response

[Eisfunke]

Can confirm. Also, still doesn't work if I try running via nu -c (so that the REPL not allowing me to submit the command doesn't play into it):

$> nu -c "nix run nixpkgs#hello"
Hello, world!

$> nu -c "echo (nix run nixpkgs#hello)"
Error: nu::parser::unexpected_eof

  × Unexpected end of code.
   ╭─[source:1:1]
 1 │ echo (nix run nixpkgs#hello)
   ╰────

(same with your example each {echo nixpkgs#unzip })

So it seems this is not just a problem with the REPL not allowing you to submit the command, the # just seems to still be parsed incorrectly if inside a block.

[amtoine]

ooh i stumbled upon the same exact one when writing this, where i tried nix run nixpkgs#opam inside a do block