Double consecutive spaces already are preserved in variables themselves - it's the parsing/tokenizing of the commandline where things go wrong. This is the case for /set as well as any other command (although /set behaves slightly differently at this point) so changing only /set would not solve anything.
As far as I can see it (and I have looked into it a bit, hence the DLL mentioned earlier), the only two things we really need are:
1) a way to allow commands to be parsed without losing the spaces. See my suggestion
here, which is simple to implement and easy to use.
2) a version of $1- as set by mIRC in events and callbacks such as "on INPUT" and $findfile's 'command' parameter, that also leaves all double consecutive spaces in. In fact, I doubt that changing the standard behaviour of $1- this way will affect any existing scripts at all - I can elaborate on this but I don't think I should do that in this thread.
This would allow scripters to get rid of all problems with double consecutive spaces; in cases ranging from simple /msg commands, to theme engines, to MP3 players (double spaces in filenames), etc.
Oh and while I'm at it: adding support for true quoted strings (as also mentioned in another thread) would be such a fundamental change to mIRC's script parser, that I can safely say that it just isn't going to happen. Ever. And IMO, that's only a good thing.
