I've come across multiple situations in which it would be useful to have /timer avoid parsing { } and [ ] brackets and simply preserve all text in "<command>". I've been able to avoid single bracket sets parsing via $({ },0), but this does not work for multiple sets such as $({ { } },0). I can understand the need to, by default, parse timers' brackets upon its execution when a timer is executed within a script or via "//timer", but, on a side note, this feels incongruent with mIRC's normal behavior when using a single slash "/timer". Regardless, a "-n" switch (perhaps similar to the "n" parameter in $read) to avoid execution-time parsing would be very useful to avoid excessive escaping during high volumes of timers.
For example: /timer -n 1 1 echo -a { { hello } } would echo { { hello } } instead of simply hello as it does now. Note that I am not proposing to stop parsing when the timer is created, so //timer -n 1 1 echo -a Version: $version (or scripted execution) would still echo Version: 6.2 (for example).
Yes, I know a $regexsub or something of the like could probably take care of this fairly quickly, it just seems excessive and a bit advanced for the level of user for which I'm proposing this, who just wants all characters in <command> preserved.
