Debug tells us:

Allocated new buffer a4909890
Found end of line
commandline: dir "

[Shell] checkLine() Calling convertLine(), line = dir "

[Shell] BackTicks handling done... cookingCS.CS_Buffer = 'dir "'
Str: dir "
Found possible command
Command found!
Command = dir
Str: "
error=100 moreleft=1 interactive=1 background=0

Thanks o1i,

Indeed it is even funnier. In my example it literally showed s2 (with lots of spaces around it).

Now that i tried your examples, the message seems to vary

Is it perhaps a print formatting routine getting some randomly peeked memory ?

At least it does print something of the command you entered (when not using too much spaces), but not always.

Interresting issue...

Since i don't have a sf account -> it would be nice if someone could pick this up or file a bugreport when the issue is not known yet.

Thanks again for the confirmation o1i.

It's even funnier:

> dir_"
_ir_":_Error_100

> dir__"
__r_":_Error_100

> dir___"
____":_Error_100

I was testing some stuff the other day and i ran into this:

Reproduce:
- open shell
- type dir_____" + enter
(underscores are spaces, amount does not matter as long as it's 1 or more. It's the qoute that throws it off)

Error:
- above command results in: __________ s2__________": error 100

Expected behaviour:
- as on classic (WB 40.42): "argument line invalid or too long"

Tested on:
- every abiv0 i could possibly find atm

possible culprit/solution
- i have no idea

looking/searching for confirmation.

thanks in advance.