Forums Feature Suggestions unparsed parameters alias

Now, this has been posted about countless times, but what I am suggesting is a work around for it, which I am sure would be easy for Khaled to implement. If you have NO ON TEXT events, and someone sends some text to a channel with spaces in it, they display correctly. If you have an ON TEXT event, they do not. This is because of the parsing etc.. If mIRC can echo the text from the server correctly without being scripted, then it should be able to do the same scripted.

$stext Displays raw text from server unparsed.

Simple as that.

This has been suggested many times, although the name most people suggested was $rawtext

Of course, I was about to use $rawtext as well. It has been suggested many times, but it needs to be added.

Perhaps if the $1- parameter in all events/aliases could also be dumped to a binvar; &1-, then the user can work with the raw data... binarily.

Next, you would need to have commands like /echo and /msg support &binvars, and everyone should be happy.

- Raccoon

That's even a better idea Racoon...

Well (in theory) /msg can't support binary data. IRC is a text based protocol. If the text contains a $cr a $lf or a $null, the IRC server is going to ignore all text after that. Actually not ignore, you'll get a "Unknown command <word after that char>" error.

At the moment /msg behaves like raw PRIVMSG $1 : +$ $2-
For example:
//msg $me hi $crlf privmsg $me :ho
Messages yourself 2 times.

I don't see the problem if you could send binary data instead...

The problem with that is it'll be a bit longer.

codemastr, it would be up to the user to make sure the data he sends through /msg via &binvar is appropriate. This should be obvious. You can send Good Data and Bad Data with standard %vars, as is (empty, too long, cr, lf, etc)... you will be able to do the same with &binvars too (null, too long, etc).

The point is, with &binvars you can preserve the freshness of the message and all its space-padded goodness, and alter or display this data as you please.

The only difference between "binary data" and "plain text" as far as mIRC is concerned, are 3 control characters that cannot be displayed as text (or formatting). Null, CR, LF. The other 253 characters can be displayed and handled just fine.

- Raccoon

zac, Binary data is no 'longer' than plain text. We're not talking unicoded text (which would be useful for international users), so the length is exactly the same. Unless of corse you have padded-spaces, then it'll be that much longer.

- Raccoon