Forums Bug Reports /read bug, command execution after |,folder&spaces

How to Reproduce:
1) Create a folder in the mirc directory with a name which contain a space ex. "my scripts"
2) Create a text file ex. test.txt in that new directory
3) Write in that file ex: heh | echo That is the bug..
4) In the mirc write //echo $mid($read(my scripts\test.txt,1),1,2)
You should see "That is the bug.."

Tested on Mirc 6.03,6.12

I would be very grateful if Khaled have written mine nick in versions.txt

That's not a bug. If you want the text to not be evaluated you should use the n switch.

Ahh .. Ok .. 10x
But if that is not a bug .. Why he evaluate only the readed text from a folder which contain a space ? If you try to read that from a file from a folder without space it not evaluated ?

AFAIK, it doesn't evaluate commands (like /play does). So, reading a pipe ('|') doesn't mean anything to $read().

/mkdir "c:\t e s t"
/write "c:\t e s t\test.txt" pipes | $me | $active | echo -a bugged?
//echo -a $read(c:\t e s t\test.txt)
/remove "c:\t e s t\test.txt"
/rmdir "c:\t e s t"

Copying and pasting those lines, mIRC echoes:

pipes | cold | Status Window | echo -a bugged?
-
* Removed 'c:\t e s t\test.txt'
-

It works here with "heh | echo That is the bug.." as well.

How about my version ?

/mkdir "c:\t e s t"
/write "c:\t e s t\test.txt" pipes | echo -a bugged? Yup
//echo -a $len($read(c:\t e s t\test.txt))
/remove "c:\t e s t\test.txt"
/rmdir "c:\t e s t"

I get
5
bugged? Yup

Used Mirc [email]6.12@Win98se[/email]

Yeah, now it's reproduced here too. It's bugged when it's used as a parameter of any other identifier (it seems so, even inside $null()), provided that its specified path contains spaces.

Well, that's why you use the n switch
//echo -a $len($read(c:\t e s t\test.txt,n))
27

It's well-known that the n switch should be used there, but the point is, this behaviour is weird and makes no sense at first.. so, Khaled might want to check it.

Edit:
Actually, there is no 'n' solution. The real point is it should be fixed. Because I could want to read a line evaluating its content. Pipes should not be evaluated, however, mIRC is evaluating them in this case.
Or maybe it should actually evaluate them in any case, like $eval() does.

Regardless of its intended behaviour, it's currently a bugged feature.