Quote:
Thank you.

From reading the report in the bugtracker it might be important to mention that the faulty printing of the error on v0 is not related to the dir command in any way. It does print this faulty message for several AROS shell command i tried such as also list.

It could be the dir ram: example to be more the culprit of the dir command itself ?

Quote:

It's worse
dir "ram:" "
prints the content of the current directory.

I'll open a ticket on the bug tracker.

Quote:

Surely mismatched quotes shouldn't be ignored (if that's still what were talking about).

No problem Mazze, i'm not in a hurry

I leave the topic for now then, until status becomes more clear.

Since it's a minor issue (in the grand scheme of things) i thought perhaps it's not so important (and given your request for a bit more streamlining in the bug-forum).

thank you for the input

Wait, maybe we can backport the Shell to ABIv0.

Quote:

Although the silent treatment could be expected behaviour for AROS (i honestly can't tell), do i still need to expect classic behaviour ?
(WB 40.42: "argument line invalid or too long")

If the silent behaviour is expected, can i then assume there is no need for addressing it for v0 ?

iow can i change the topic to solved or won't fix already ?

It works under ABIv1 (no error message, the " is silently ignored)

Just some additional information

when doing:

dir____|


it shows (more or less) the correct error:

____r____|: argument line invalid or too long

Ah, always nice to see a debug log.
it can tell so much more, although i have no idea what error 100 means in this context :S

btw: there are more commands giving the same result. Maybe those conditions what are displayed by debuglog could be used to tell it's a "argument line invalid or too long" ?

Forgive my ignorance on the subject if it is completly wrong.

BTW: using a single quote also brings some interresting sideeffects
- "Dir '" (without double qoutes), does more or less as expected, but list (space space space singlequote) does something wierd (object not found), so it seems that is not directly related to shell but an per command feature ?

There must be more of thouse 'hidden' features

thx again o1i,

RED: hmz, interresting when people post at exactly the same time

Indeed that stuff looks scary nice you were able to confirm what i more or less suspected, a faulty error print/formatting routine. I do hope that's all to it....

Seems like just the wrong error message is printed, it calls

PrintFault(result, filtered.CS_Buffer);

with a not valid buffer. Should just be:

PutStr("argument line invalid or too long\n");

But I won't mess around with the shell code, this stuff looks scary ..