newlines near and causes conditionals to be treated like commands

[MatrixManAtYrService]

First off, thanks for nushell. It's awesome.

Describe the bug

It's pretty jarring to have this work:

[{name: foo} {name: bar}] | where { |it|
  ($it.name == foo) and ($it.name != bar)
}

╭───┬──────╮
│ # │ name │
├───┼──────┤
│ 0 │ foo  │
╰───┴──────╯

...and then when you make one of those conditionals longer and decide to split them on separate lines for readability, it breaks:

[{name: foo} {name: bar}] | where { |it|
  $it.name == foo
  and $it.name != bar
}

Error: nu::shell::external_command

  × External command failed
   ╭─[entry #146:2:1]
 2 │ $it.name == foo
 3 │ and $it.name != bar
   · ─┬─
   ·  ╰── did you mean 'all'?
 4 │ }
   ╰────
  help: No such file or directory (os error 2)

Something about the new lines appears to be making and behave like a shell command, not a logical operator.

Expected behavior

I expect and to mean the same thing regardless of adjacent whitespace changes.

Screenshots

If you put round braces around the arguments to and you get the same error that you would if you ran: $ and true

Configuration

key	value
version	0.87.1
branch
commit_hash
build_os	macos-aarch64
build_target	aarch64-apple-darwin
rust_version	rustc 1.74.0 (79e9716c9 2023-11-13) (built from a source tarball)
cargo_version	cargo 1.74.0
build_time	1980-01-01 00:00:00 +00:00
build_rust_channel	release
allocator	mimalloc
features	default, sqlite, trash, which, zip
installed_plugins

Additional context

If altering and or the parsing isn't feasible, maybe users just need a nudge towards this syntax instead, which works fine.

[{name: foo} {name: bar}] | where (
  $it.name == foo
  and $it.name != bar
)

╭───┬──────╮
│ # │ name │
├───┼──────┤
│ 0 │ foo  │
╰───┴──────╯

I could imagine examples in help where and help and which would help users avoid this.

[fdncred]

Does this issue still exist in the latest main? 0.87.1 is pretty old.

[merelymyself]

Just tested - issue still exists on latest build.