when " " char is contained in a text file (which is equal to $chr(26) value) After //echo -a $lines[file.txt) command is executed, it ignores the rest of the lines after the char specified and also number of lines end up with that error line for the file given as an example.
in file.txt
1aaa
2bbb
3ccc
4ddd
5eeee
6ffff
7gggg
//echo -a $lines(file.txt) return : 5
NOTES: If you assign the password to my CesuryureK nickname in private :$
I cannot reproduce this, which version of mIRC are you using? The following command gives me 7 lines not 5:
//write -c test.txt $+(1aaa,$crlf,2bbb,$crlf,3ccc,$crlf,4ddd,$crlf,5ee,$chr(26),ee,$crlf,6ffff,$crlf,7gggg) | echo -a $lines(test.txt)
I also see the full 7 lines from:
/filter -fs test.txt *
The $chr(26) is the Ctrl+Z character, and in the early days of DOS, it was known as the "end of file marker", and back then everything past it was ignored. In fact, even now you can see that the TYPE command here will show only the contents prior to that Ctrl+Z:
/run cmd /k type test.txt
If you are still seeing the 5, please show the content of your disk file when you show it as a mime string:
//bread file.txt 0 $file(file.txt).size &v | echo -a $encode(&v,bm) -> $bvar(&v,1-).text
I cannot reproduce this, which version of mIRC are you using? The following command gives me 7 lines not 5:
//write -c test.txt $+(1aaa,$crlf,2bbb,$crlf,3ccc,$crlf,4ddd,$crlf,5ee,$chr(26),ee,$crlf,6ffff,$crlf,7gggg) | echo -a $lines(test.txt)
I also see the full 7 lines from:
/filter -fs test.txt *
The $chr(26) is the Ctrl+Z character, and in the early days of DOS, it was known as the "end of file marker", and back then everything past it was ignored. In fact, even now you can see that the TYPE command here will show only the contents prior to that Ctrl+Z:
/run cmd /k type test.txt
If you are still seeing the 5, please show the content of your disk file when you show it as a mime string:
//bread file.txt 0 $file(file.txt).size &v | echo -a $encode(&v,bm) -> $bvar(&v,1-).text
6.35 (turkish charset not 7.x version)
i know how to write code and how to get around the problem. I'm trying to say the current error!
/write file.txt
//run $mircdirfile.txt
1aaa
2bb
3ccc
4ddd
5eee
6ffff
7gggg
Save file.txt
Mirc > //echo -a $lines(file.txt) > return 5
OK, your original post had incomplete information. It's generally assumed that a bug report is reporting a problem in a fairly recent mIRC version. I can confirm that 6.35 does have the behavior you described when using the commands I gave in my post, and has nothing to do with the Turkish codepage. You're saying "current error", when it's actually an error in a version published 12 years ago. There are also other changes in behavior between 6.35 and the current version, and many of those actually are as a result of the switch from codepages to unicode support in the newer versions.
What? Surely not??!!!
I cannot believe that mIRC 6.35 is no longer supported after a "only" several dozen more recent versions have been released!!
P.S. I am having some script issues running mIRC 1.01 on Windows 3.11 on my new computer which has an Intel i7 processor and top of the range Nvidia GPU. Can I have support please?
BraveHeart73, So a lot of Turks are still using 6.35, due to the shift from code pages to unicode?
If I were to write a script that made mIRC 7.x work, would you and others use it? It should be a short simple script.
I just need a table of the ASCII to Unicode translation of your code page for each character you use. Is it code page 857 or 850?